Add mandatory regulator for all users of pwm-backlight.
Get series with b4
b4 am 1363763588.30752.7.camel@gitboxVersions newest first
- v4 Latest1 of 9 patches 0 repliesNew
1 of 9 patches is in this archive. The cover letter announces 9.
Patches in v4 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 7/9 | ARM: vt8500: Provide regulator to pwm-backlight | +0 | 0 replies |
Reviews trailers per patch
The patch has a Reviewed-by or Acked-by.
| Patch | Tony Prisk |
|---|---|
| 7/9 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH V4 0/9] Add mandatory regulator for all users of pwm-backlight.
Quoted 11 lines · Alex Courbot
Quoted 9 lines · Shawn Guo
Quoted 3 lines · Andrew Chew
Many backlights are enabled via GPIO. We can generalize the GPIO to a fixed regulator.
I think we should push the series of "Runtime Interpreted Power Sequences" moving forward, which should be useful this case and many other cases as well.
Quoted 8 lines
That's still the medium-term plan. But doing this correctly requires some improvements to be done in the GPIO subsystem, which I am pushing at the moment.
Eventually power sequences should handle this kind of scenario, but by the meantime it cannot hurt to get the job done.
Alex.
I don't mind this patch personally, so take this query as more of a 'generalization' than a problem with this patch:
This patch changes the binding for an already used device (by addition of a required property), which isn't so bad BUT, as Alex pointed out, the binding will probably end up being changed again once power sequencing is sorted out.
I realise it's still early days and things need to be tried-and-tested first, but wasn't the point of the bindings that they should be finalized (as best as possible anyway) the first time, so we don't have to worry about incompatibilities between bindings and drivers?
Regards
Tony P