From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Jangam <Ashish.Jangam@kpitcummins.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"sameo@openedhand.com" <sameo@openedhand.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dajun <dajun.chen@diasemi.com>,
"linaro-dev@lists.linaro.org" <linaro-dev@lists.linaro.org>
Subject: Re: [PATCH 01/11] MFD: DA9052 MFD core module v8
Date: Fri, 2 Dec 2011 14:03:04 +0000 [thread overview]
Message-ID: <20111202140304.GT8245@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <C3AE124F08223B42BC95AEB82F0F6CED1F9CFD03@KCHJEXMB01.kpit.com>
On Fri, Dec 02, 2011 at 01:57:49PM +0000, Ashish Jangam wrote:
> > On Fri, Nov 18, 2011 at 02:49:54PM +0530, Ashish Jangam wrote:
> > > + da9052_i2c->bustype = BUS_I2C;
> > bustype should be redundant now, it certianly doesn't seem to be
> > referred to in this patch.
> This is required in the TSI driver.
You can just query the bus_type of the struct device if you really need
this.
> > > + * Interrupt controller support for Dilaog DA9052 PMICs.
> > This looks very much like it could be replaced with regmap-irq. The
> > code would be slightly less efficient due to the support for sparse
> > interrupt registers but it'd be less code.
> regmap-irq has a opaque struct regmap_irq_chip_data which has a member
> irq_base and this is required for non-primary irqs registration
> and also the clean-up function regmap_del_irq_chip() requires it.
> So as of now I will keep the current irq implementation as it is.
I'm not sure how this is relevant to my above comment? The struct is of
course opaque since it is only used by the implementation.
next prev parent reply other threads:[~2011-12-02 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 9:19 [PATCH 01/11] MFD: DA9052 MFD core module v8 Ashish Jangam
2011-11-24 12:05 ` Mark Brown
2011-12-02 13:57 ` Ashish Jangam
2011-12-02 14:03 ` Mark Brown [this message]
2011-12-04 11:50 ` Ashish Jangam
2011-12-04 15:59 ` Mark Brown
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=20111202140304.GT8245@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Ashish.Jangam@kpitcummins.com \
--cc=arnd@arndb.de \
--cc=dajun.chen@diasemi.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@openedhand.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