On Mon, Nov 23, 2009 at 10:44:25AM -0700, Grant Likely wrote: > Right, pin-mux is a different problem. But there are also devices > that implement both PWM and GPIO functionality in the same IP block. That's not the general case, though - most of the SoCs seem to have PWM as a separate IP block. In the general case PWM and GPIO have nothing to do with each other. > I think pin muxing, and pin controller drivers are different problem > domains and should be handled separately. ... > Sorry. when I said pin management I meant how Linux keeps track of pin > controllers. Not pin mux. I should use different terminology perhaps > to reduce confusion. I have to confess I'm a bit lost as to what you mean by a "pin controller" as opposed to "pin mux" interface. For a substantial proportion of ARMs they're going to be one and the same. Judging from some of the other messages in the thread I suspect you're thinking of a much closer mapping between PWM and GPIO pins - many SoCs do have distinct PWM controllers that aren't terribly tied to a GPIO pin. For them the whole concept of requesting a "pin" or having the PWM controller be tied to a particular pin is going to be at best confusing, you really do want to request the PWM controller itself and let the pin mux setup figure out where that emerges from the SoC. -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
