From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: MyungJoo Ham <myungjoo.ham@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Donggeun Kim <dg77.kim@samsung.com>
Subject: Re: [PATCH 3/3] MFD: MAX8997: IRQ definition moved to public header.
Date: Tue, 5 Jul 2011 12:53:45 -0700 [thread overview]
Message-ID: <20110705195344.GC8642@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJ0PZbSrB9Cc-2h0xGot6kYUGR-uu0f7GVq43c_fSEd5oTMEog@mail.gmail.com>
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.
prev parent reply other threads:[~2011-07-05 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 1:31 [PATCH 1/3] MFD: MAX8997: IRQ Handling Bugfix MyungJoo Ham
2011-06-30 1:31 ` [PATCH 2/3] MFD: MAX8997: Support Wake-up from Suspend MyungJoo Ham
2011-06-30 1:31 ` [PATCH 3/3] MFD: MAX8997: IRQ definition moved to public header MyungJoo Ham
2011-06-30 5:28 ` Mark Brown
2011-06-30 5:56 ` MyungJoo Ham
2011-06-30 5:57 ` Mark Brown
2011-06-30 8:00 ` MyungJoo Ham
2011-06-30 15:56 ` Mark Brown
2011-07-01 0:43 ` MyungJoo Ham
2011-07-04 17:16 ` Mark Brown
2011-07-05 5:57 ` MyungJoo Ham
2011-07-05 6:19 ` Mark Brown
2011-07-05 6:49 ` MyungJoo Ham
2011-07-05 19:53 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110705195344.GC8642@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dg77.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=myungjoo.ham@gmail.com \
--cc=sameo@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox