Messages in this thread | | | Date | Mon, 4 Jul 2011 23:19:03 -0700 | From | Mark Brown <> | Subject | Re: [PATCH 3/3] MFD: MAX8997: IRQ definition moved to public header. |
| |
On Tue, Jul 05, 2011 at 02:57:54PM +0900, MyungJoo Ham wrote: > On Tue, Jul 5, 2011 at 2:16 AM, Mark Brown
> > My understanding was that one of the goals of the power_supply subsystem > > was to support this sort of interaction? This (and your subsequent > > paragraphs) all sounds entirely sensible but it should be being dealt > > with at a higher level with the various charger drivers delivering > > events into a subsystem or board driver which coordinates them all. It > > seems like the driver should be doing the work of dealing with the > > actual interrupts.
> Yes, I also think that it is supposed to read and update attributes of > chargers. However, I don't see any ways to interconnect chargers and > related devices with power_supply subsystem.
Nor do I, but this is just software so we should be able to make it do what's needed here.
> If we let a user process interconnect the chargers and related > devices, we need to allow userland to access (both read and write)
I didn't say anything about userspace, and I wouldn't expect userspace to do anything except policy here. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |