From: b29396@freescale.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] pinctrl: pinctrl-imx: add support for set bits for general purpose registers
Date: Tue, 17 Jul 2012 11:04:12 +0800 [thread overview]
Message-ID: <20120717030411.GG19699@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <201207161340.18528.arnd@arndb.de>
On Mon, Jul 16, 2012 at 09:40:17PM +0800, Arnd Bergmann wrote:
> On Monday 16 July 2012, Richard Zhao wrote:
> > > If you really wants a "funnel driver" doing all these diverse things,
> > > I'd put it in drivers/mfd.
> >
> > It's like driver drivers/mfd/anatop-mfd.c. They both store misc bits.
> > We may need a generic driver to simply provide register accessor.
>
> We already have the "regmap" framework that deals with sets of registers
> on spi, i2c or memory mapped buses. One thing I've thought about
Thanks for the hints.
Will look into it.
> before is to create some kind of very simple "system controller"
> framework based on regmap that lets you register a single global
> "struct regmap" pointer from an SoC specific driver, and have drivers
> call a function into that framework to get a reference to that
> regmap.
>
That would be a good idea to make people easy use.
Regards
Dong Aisheng
WARNING: multiple messages have this Message-ID (diff)
From: Dong Aisheng <b29396-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Zhao Richard-B20223
<B20223-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
"s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
<s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org"
<linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>,
"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Liu Hui-R64343 <r64343-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
"kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
<kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Mike Turquette <mturquette-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH v2 1/2] pinctrl: pinctrl-imx: add support for set bits for general purpose registers
Date: Tue, 17 Jul 2012 11:04:12 +0800 [thread overview]
Message-ID: <20120717030411.GG19699@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <201207161340.18528.arnd-r2nGTMty4D4@public.gmane.org>
On Mon, Jul 16, 2012 at 09:40:17PM +0800, Arnd Bergmann wrote:
> On Monday 16 July 2012, Richard Zhao wrote:
> > > If you really wants a "funnel driver" doing all these diverse things,
> > > I'd put it in drivers/mfd.
> >
> > It's like driver drivers/mfd/anatop-mfd.c. They both store misc bits.
> > We may need a generic driver to simply provide register accessor.
>
> We already have the "regmap" framework that deals with sets of registers
> on spi, i2c or memory mapped buses. One thing I've thought about
Thanks for the hints.
Will look into it.
> before is to create some kind of very simple "system controller"
> framework based on regmap that lets you register a single global
> "struct regmap" pointer from an SoC specific driver, and have drivers
> call a function into that framework to get a reference to that
> regmap.
>
That would be a good idea to make people easy use.
Regards
Dong Aisheng
next prev parent reply other threads:[~2012-07-17 3:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 9:07 [PATCH v2 1/2] pinctrl: pinctrl-imx: add support for set bits for general purpose registers Dong Aisheng
2012-07-12 9:07 ` Dong Aisheng
2012-07-12 9:08 ` [PATCH v2 2/2] pinctrl: pinctrl-imx6q: add missed mux function for USBOTG_ID Dong Aisheng
2012-07-12 9:08 ` Dong Aisheng
2012-07-12 9:31 ` [PATCH v2 1/2] pinctrl: pinctrl-imx: add support for set bits for general purpose registers Richard Zhao
2012-07-12 9:31 ` Richard Zhao
2012-07-12 9:48 ` Hui Wang
2012-07-12 9:48 ` Hui Wang
2012-07-12 10:24 ` Richard Zhao
2012-07-12 10:24 ` Richard Zhao
2012-07-12 11:04 ` Dong Aisheng
2012-07-12 11:04 ` Dong Aisheng
2012-07-14 20:43 ` Linus Walleij
2012-07-14 20:43 ` Linus Walleij
2012-07-16 8:17 ` Richard Zhao
2012-07-16 8:17 ` Richard Zhao
2012-07-16 13:40 ` Arnd Bergmann
2012-07-16 13:40 ` Arnd Bergmann
2012-07-16 22:15 ` Linus Walleij
2012-07-16 22:15 ` Linus Walleij
2012-07-17 3:04 ` Dong Aisheng [this message]
2012-07-17 3:04 ` Dong Aisheng
2012-07-17 3:02 ` Dong Aisheng
2012-07-17 3:02 ` Dong Aisheng
2012-07-17 18:15 ` Linus Walleij
2012-07-17 18:15 ` Linus Walleij
2012-07-17 18:24 ` Mark Brown
2012-07-17 18:24 ` 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=20120717030411.GG19699@shlinux2.ap.freescale.net \
--to=b29396@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.