On Tue, Nov 4, 2008 at 18:55, David Brownell wrote: > On Tuesday 04 November 2008, Bill Gatliff wrote: >> So, what's the next step? How do I advocate for getting >> this API into mainline? > > The number of backing implementations seemed a bit low ... > just one. And that's switching Atmel's dedicated PWM, but > not the other PWM driver in the tree (for PXA); so it's > not terrifically accessible. > > My rule of thumb is that it's not worth considering a > framework as being general enough until it's got three > fairly different backing implementations. Two is enough > to consider merging, especially with complicated drivers. every Blackfin processor so far has had dedicated PWM hardware in it, so a backend driver for that arch would show up ... > Plus the number of framework users is an issue. The > PWM led driver is a good demo for two basic features, > and it's useful: brightness (duty cycle beyond visual > perception) and blink rate (duty cycle easily seen with > the eye). But it's still only really one API customer, > even given that new LED trigger... there is an lcd driver or two in the tree (probably Blackfin specific) that uses the PWM hardware as an output to drive the hsync/vsync signals. and while LIRC is still out-of-tree for mainline, i wrote a driver using the PWM hardware as an input ... but there wasnt anything else Blackfin specific in said driver other than the PWM stuff ... i'm guessing you'd prefer to see those implemented before moving to mainline though ? -mike -- 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
