From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
Mike Rapoport <mike@compulab.co.il>,
linux-kernel@vger.kernel.org, sameo@linux.intel.com,
linux-i2c@vger.kernel.org,
Linus Walleij <linus.walleij@stericsson.com>
Subject: Re: [PATCH 1/1] MFD: Add U300 AB3100 core support v2
Date: Tue, 19 May 2009 19:40:59 +0100 [thread overview]
Message-ID: <20090519184059.GB4476@sirena.org.uk> (raw)
In-Reply-To: <5d5443650905191026w22b0ff95j992e09923f55dd0a@mail.gmail.com>
On Tue, May 19, 2009 at 10:56:16PM +0530, Trilok Soni wrote:
> I don't know but why people are not encouraging to use mfd_xxx apis
> here? Lot's of drivers are available under drivers/mfd, but only
> couple of them are using real mfd_xxx apis? Is there anything missing
> in those apis?
The mfd_ APIs only really help with memory mapped platform devices but a
lot of MFD devices are controlled using I2C and SPI interfaces instead.
On registration they need to at least do something extra to allow the
client devices to access the I2C or SPI control structure, or the client
drivers have to do something like fish around using their parent
pointer.
It's not so much that there's something wrong with the MFD APIs as
issues with splitting up I2C and SPI devices for access in a generic
manner. With things mapped through struct resource the MFD API is able
to provide some help.
prev parent reply other threads:[~2009-05-19 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 20:40 [PATCH 1/1] MFD: Add U300 AB3100 core support v2 Linus Walleij
[not found] ` <63386a3d0905181340y42ad1868k6b2978e586abc18d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-19 10:50 ` Ben Dooks
2009-05-19 14:35 ` Mike Rapoport
[not found] ` <4A12C3B5.2050100-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2009-05-19 16:23 ` Linus Walleij
[not found] ` <63386a3d0905190923t36d301c5hf245c06db00b6127-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-19 17:26 ` Trilok Soni
2009-05-19 18:40 ` 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=20090519184059.GB4476@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=sameo@linux.intel.com \
--cc=soni.trilok@gmail.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).