linux-kernel - Re: [PATCH 3/3] MFD: MAX8997: IRQ definition moved to public header.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110705195344.GC8642@opensource.wolfsonmicro.com>
Date:	Tue, 5 Jul 2011 12:53:45 -0700
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	MyungJoo Ham <myungjoo.ham@...il.com>
Cc:	linux-kernel@...r.kernel.org, Samuel Ortiz <sameo@...ux.intel.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	Donggeun Kim <dg77.kim@...sung.com>
Subject: Re: [PATCH 3/3] MFD: MAX8997: IRQ definition moved to public header.

On Tue, Jul 05, 2011 at 03:49:39PM +0900, MyungJoo Ham wrote:

> Anyway, I've been trying to implement some virtual device driver or
> psuedo framework in kernel to interconnect charger related devices,
> "charger manager". This code mentioned is to support that "charger
> manager". It is sort of at a higher level of charger related devices,
> taking device names of them as a platform data. The platform data
> taking the IRQ numbers is the one for that "charger manager".

Right, so what I'm saying is that the interface between the two blocks
should be changed so that the manager code isn't talking directly to the
interrupt but is talking to something higher level.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/