linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: aisheng.dong@freescale.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] pinctrl: add pinctrl-mxs support
Date: Tue, 24 Apr 2012 11:40:11 +0800	[thread overview]
Message-ID: <20120424034010.GA32166@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <20120423144623.GU26306@S2101-09.ap.freescale.net>

On Mon, Apr 23, 2012 at 10:46:26PM +0800, Shawn Guo wrote:
> On Mon, Apr 23, 2012 at 03:47:03PM +0800, Dong Aisheng wrote:
> > On Mon, Apr 23, 2012 at 12:32:58AM +0800, Shawn Guo wrote:
> > > On Sun, Apr 22, 2012 at 12:47:13AM +0800, Dong Aisheng wrote:
> > > > On Thu, Apr 19, 2012 at 04:12:05PM +0800, Shawn Guo wrote:
> > > > > Add pinctrl support for Freescale MXS SoCs, i.MX23 and i.MX28.
> > > > > The driver supports device tree probe only.
> > > > > 
> > > > > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > > > > ---
> > > > First, it seems i.MX23 and i.MX28 have the same situation as
> > > > other IMX families like i.MX6Q that they're all pin based
> > > > SoCs. Thus i think the correct thing to do now may be to
> > > > enhance pinctrl-imx core driver to support them all rather
> > > > than write a much similar one only for i.MX23 and i.MX28,
> > > > right?
> > > > 
> > > I would think there will be SoCs from other vendors sharing the same
> > > situation.  My view on this is to have them in and then look for the
> > > common pattern among these drivers and come up with some generic
> > > helper functions.
> > > 
> > We may get align with all FSL families first.
> > At least the binding part could be the same.
> > The most difference between MXS and IMX is different register layout.
> > For example, pinconf_set/get may be different.
> > One rough idea in my mind is that one callback in pinctrl-imx may
> > handle it.
> > 
> You haven't convinced me that the imx binding you came up with your
> v2 series plays well for mxs.
> 
Then please feel free to comment on the pinctrl-imx binding if you've
different option for mxs.
But i did not receive you comment...

I think we'd better have a face to face discussion when you come to office.
At least one unified binding for all FSL SoCs is our goal, isn't it?

BTW one idea in my mind is that we indeed may want pinctrl subsystem support
config a group of pins based on pin config which i rasied in my v2 patch.
I'm going to send a patch and discuss with Linus and Stephen more.
If that works, we really do not have to do as you did for mxs
for all FSL SoCs.

Regards
Dong Aisheng

  parent reply	other threads:[~2012-04-24  3:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19  8:12 [PATCH 1/2] pinctrl: add pinctrl-mxs support Shawn Guo
2012-04-19  8:40 ` Shawn Guo
2012-04-20 17:02 ` Stephen Warren
2012-04-21  1:51   ` Shawn Guo
2012-04-23 18:47     ` Stephen Warren
2012-04-23 23:12       ` Shawn Guo
2012-04-21 16:47 ` Dong Aisheng
2012-04-22 16:32   ` Shawn Guo
2012-04-23  7:47     ` Dong Aisheng
2012-04-23 14:46       ` Shawn Guo
2012-04-23 19:01         ` Stephen Warren
2012-04-23 23:25           ` Shawn Guo
2012-04-24 13:01           ` Linus Walleij
2012-04-24  3:40         ` Dong Aisheng [this message]
2012-04-24  4:05           ` Shawn Guo
2012-04-24 13:07             ` Linus Walleij
2012-04-24 13:26               ` Shawn Guo
2012-04-24 14:25                 ` Dong Aisheng
2012-04-26  8:41                   ` Linus Walleij
2012-04-26 11:22                     ` Dong Aisheng

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=20120424034010.GA32166@shlinux2.ap.freescale.net \
    --to=aisheng.dong@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 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).