From: Lee Jones <lee.jones@linaro.org>
To: "Shevchenko, Andriy" <andriy.shevchenko@intel.com>
Cc: "pure.logic@nexus-software.ie" <pure.logic@nexus-software.ie>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chen, Alvin" <alvin.chen@intel.com>,
"Tan, Raymond" <raymond.tan@intel.com>
Subject: Re: [PATCH 1/1] mfd: intel_quark_i2c_gpio: Add Intel Quark X1000 I2C-GPIO MFD Driver
Date: Tue, 4 Nov 2014 09:22:46 +0000 [thread overview]
Message-ID: <20141104092246.GN17577@x1> (raw)
In-Reply-To: <1415092249.472.5.camel@intel.com>
On Tue, 04 Nov 2014, Shevchenko, Andriy wrote:
> On Mon, 2014-11-03 at 09:43 +0000, Bryan O'Donoghue wrote:
> > On 03/11/14 07:39, Raymond Tan wrote:
> > > In Quark X1000, there's a single PCI device that provides both
> > > an I2C controller and a GPIO controller. This MFD driver will
> > > split the 2 devices for their respective drivers.
> > >
> > > This patch is based on Josef Ahmad's initial work for Quark enabling.
> >
> > Hi Raymond.
> >
> > I see support for interrupts on GPIO input has been dropped. In fact it
> > doesn't appear you have any IRQ support here at all.
> >
> > Could you detail the reasons why ?
>
> In general the MFD drivers are just dispatchers which split an original
> compound device by its slices.
+1
That's a really nice way of putting it.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-11-04 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 7:39 [PATCH 0/1] mfd: intel_quark_i2c_gpio: Add Intel Quark X1000 I2C-GPIO MFD Driver Raymond Tan
2014-11-03 7:39 ` [PATCH 1/1] " Raymond Tan
2014-11-03 9:11 ` Andy Shevchenko
2014-11-03 13:09 ` Lee Jones
2014-11-11 12:57 ` Tan, Raymond
2014-11-03 9:43 ` Bryan O'Donoghue
2014-11-04 9:10 ` Shevchenko, Andriy
2014-11-04 9:22 ` Lee Jones [this message]
2014-11-03 10:35 ` Bryan O'Donoghue
2014-11-04 0:46 ` Chen, Alvin
2014-11-04 0:51 ` Chen, Alvin
2014-11-04 10:54 ` Bryan O'Donoghue
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=20141104092246.GN17577@x1 \
--to=lee.jones@linaro.org \
--cc=alvin.chen@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pure.logic@nexus-software.ie \
--cc=raymond.tan@intel.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;
as well as URLs for NNTP newsgroup(s).