On Mon, Oct 27, 2014 at 10:16:17AM -0700, Guenter Roeck wrote: > On Mon, Oct 27, 2014 at 11:03:24AM -0500, Felipe Balbi wrote: > > Adding Johan, who's working on RTC power off for AM335x devices > > > Hi Felipe, > > is that the rtc-omap driver ?
yes it is. > I am tracking linux-next for related changes. As new power-off handlers are > introduced, I prepare patches for those as well. I currently have patches for > the following two drivers in the queue: > drivers/regulator/act8865-regulator.c > drivers/rtc/rtc-omap.c > > I plan to send review requests for those patches in a week or so (I think > there is still some change pending to the power-off function in the rtc-omap > driver, and I want to wait for it). yeah, Johan's working on that. > My current plan is to send a pull request for the series directly to Linus > when the next commit window opens; this is what a number of maintainers > suggested I should do. This pull request would exclude the last patch, > so pm_power_off would still be there. Next steps would then be to submit > another set of patches to update the newly introduced power-off handlers > and then to finally remove pm_power_off; this would probably happen after > the commit window closes. > > At least that is the plan unless someone has a better idea .... sounds like a good idea to me :-) > There may be some variants; for example, it might make sense to create an > immutable branch with the key patches (1-3 and 8) to enable others to use > the new functions immediately. That would require Acks from affected > maintainers for patch 1, though, so I can not do that yet. alright, I think an immutable branch people can merge would be appreciated nevertheless, but I'd certainly defer that to arch and soc maintainers. cheers -- balbi
signature.asc
Description: Digital signature