All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	linux-omap@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] pinctrl: Add generic pinctrl-simple driver that supports omap2+ padconf
Date: Tue, 15 May 2012 13:07:55 -0700	[thread overview]
Message-ID: <20120515200754.GD17852@atomide.com> (raw)
In-Reply-To: <4FB1513A.4070002@wwwdotorg.org>

* Stephen Warren <swarren@wwwdotorg.org> [120514 11:42]:
> On 05/12/2012 05:49 PM, Linus Walleij wrote:
> > On Thu, May 10, 2012 at 7:05 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
> > 
> >> Also, were you intending pinctrl-simple to actually be the GPIO
> >> controller itself? That'd be another case that one might consider fairly
> >> simple, but then extends to being gpio-simple as well as pinctrl-simple...
> > 
> > We have some pinctrl drivers implementing gpiolib too already,
> > and it's unavoidable I think, as some recent discussion about
> > matcing struct gpio_chip and pinctrl GPIO ranges shows.
> 
> I strongly believe we should only do this when the exact same HW module
> is both pinctrl and GPIO.
> 
> When there are separate HW modules, we should have separate drivers. The
> fact that the two drivers need to co-ordinate with each-other isn't a
> good argument to make them one driver.
> 
> And irrespective of how the drivers are structured, if there are two HW
> modules, we really need two separate nodes in DT to describe them, since
> the SW architecture (1 vs. 2 drivers) shouldn't influence the DT
> representation unduly.

Yes.
 
> > Maybe "-simple" isn't such a good name for this thing. Noone thinks
> > any kind of pin control is simple in any sense of the word anyway :-D
> > 
> > Tony, would pinctrl-dt-only.c be a better name perhaps?
> 
> That might be OK for the filename, but it doesn't seem like a useful
> change for the DT compatible value.

Yeah let's see if we can come up with some better name.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: Add generic pinctrl-simple driver that supports omap2+ padconf
Date: Tue, 15 May 2012 13:07:55 -0700	[thread overview]
Message-ID: <20120515200754.GD17852@atomide.com> (raw)
In-Reply-To: <4FB1513A.4070002@wwwdotorg.org>

* Stephen Warren <swarren@wwwdotorg.org> [120514 11:42]:
> On 05/12/2012 05:49 PM, Linus Walleij wrote:
> > On Thu, May 10, 2012 at 7:05 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
> > 
> >> Also, were you intending pinctrl-simple to actually be the GPIO
> >> controller itself? That'd be another case that one might consider fairly
> >> simple, but then extends to being gpio-simple as well as pinctrl-simple...
> > 
> > We have some pinctrl drivers implementing gpiolib too already,
> > and it's unavoidable I think, as some recent discussion about
> > matcing struct gpio_chip and pinctrl GPIO ranges shows.
> 
> I strongly believe we should only do this when the exact same HW module
> is both pinctrl and GPIO.
> 
> When there are separate HW modules, we should have separate drivers. The
> fact that the two drivers need to co-ordinate with each-other isn't a
> good argument to make them one driver.
> 
> And irrespective of how the drivers are structured, if there are two HW
> modules, we really need two separate nodes in DT to describe them, since
> the SW architecture (1 vs. 2 drivers) shouldn't influence the DT
> representation unduly.

Yes.
 
> > Maybe "-simple" isn't such a good name for this thing. Noone thinks
> > any kind of pin control is simple in any sense of the word anyway :-D
> > 
> > Tony, would pinctrl-dt-only.c be a better name perhaps?
> 
> That might be OK for the filename, but it doesn't seem like a useful
> change for the DT compatible value.

Yeah let's see if we can come up with some better name.

Regards,

Tony

  reply	other threads:[~2012-05-15 20:07 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 17:24 [PATCH] pinctrl: Add generic pinctrl-simple driver that supports omap2+ padconf Tony Lindgren
2012-05-02 17:24 ` Tony Lindgren
2012-05-03  6:51 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-03  6:51   ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-03 15:27   ` Tony Lindgren
2012-05-03 15:27     ` Tony Lindgren
2012-05-03 22:34     ` Stephen Warren
2012-05-03 22:34       ` Stephen Warren
2012-05-04  4:43       ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04  4:43         ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 15:03         ` Tony Lindgren
2012-05-04 15:03           ` Tony Lindgren
2012-05-04 15:32           ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 15:32             ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 15:32             ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 16:34             ` Tony Lindgren
2012-05-04 16:34               ` Tony Lindgren
2012-05-04 16:38               ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 16:38                 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 18:55               ` Stephen Warren
2012-05-04 18:55                 ` Stephen Warren
2012-05-04 22:08                 ` Tony Lindgren
2012-05-04 22:08                   ` Tony Lindgren
2012-05-09 20:19                   ` Stephen Warren
2012-05-09 20:19                     ` Stephen Warren
2012-05-09 20:49                     ` Tony Lindgren
2012-05-09 20:49                       ` Tony Lindgren
2012-05-10 17:05                       ` Stephen Warren
2012-05-10 17:05                         ` Stephen Warren
2012-05-10 17:27                         ` Tony Lindgren
2012-05-10 17:27                           ` Tony Lindgren
2012-05-11 19:17                           ` Stephen Warren
2012-05-11 19:17                             ` Stephen Warren
2012-05-11 19:51                             ` Tony Lindgren
2012-05-11 19:51                               ` Tony Lindgren
2012-05-11 21:04                               ` Stephen Warren
2012-05-11 21:04                                 ` Stephen Warren
2012-05-11 21:18                                 ` Tony Lindgren
2012-05-11 21:18                                   ` Tony Lindgren
2012-05-12 23:49                         ` Linus Walleij
2012-05-12 23:49                           ` Linus Walleij
2012-05-12 23:49                           ` Linus Walleij
2012-05-14 18:38                           ` Stephen Warren
2012-05-14 18:38                             ` Stephen Warren
2012-05-15 20:07                             ` Tony Lindgren [this message]
2012-05-15 20:07                               ` Tony Lindgren
2012-05-16  7:14                             ` Linus Walleij
2012-05-16  7:14                               ` Linus Walleij
2012-05-16 15:53                               ` Stephen Warren
2012-05-16 15:53                                 ` Stephen Warren
2012-05-05  2:04                 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-05  2:04                   ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-09 20:24                   ` Stephen Warren
2012-05-09 20:24                     ` Stephen Warren
2012-05-09  9:09           ` Linus Walleij
2012-05-09  9:09             ` Linus Walleij
2012-05-09 20:50             ` Tony Lindgren
2012-05-09 20:50               ` Tony Lindgren
2012-05-04 19:23 ` Stephen Warren
2012-05-04 19:23   ` Stephen Warren
2012-05-04 21:57   ` Tony Lindgren
2012-05-04 21:57     ` Tony Lindgren
2012-05-09 20:16     ` Stephen Warren
2012-05-09 20:16       ` Stephen Warren
2012-05-09 21:08       ` Tony Lindgren
2012-05-09 21:08         ` Tony Lindgren

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=20120515200754.GD17852@atomide.com \
    --to=tony@atomide.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.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.