public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] pinctrl/nomadik: add STn8815 ASIC support
Date: Fri, 08 Jun 2012 10:39:22 -0600	[thread overview]
Message-ID: <4FD22ABA.6010607@wwwdotorg.org> (raw)
In-Reply-To: <1339146426-20697-1-git-send-email-linus.walleij@linaro.org>

On 06/08/2012 03:07 AM, Linus Walleij wrote:
> This adds support for the STN8815 ASIC for the Nomadik pin
> controller.

> diff --git a/drivers/pinctrl/pinctrl-nomadik.c b/drivers/pinctrl/pinctrl-nomadik.c

> @@ -1717,6 +1717,8 @@ static int __devinit nmk_pinctrl_probe(struct platform_device *pdev)
>  			of_match_device(nmk_pinctrl_match, &pdev->dev)->data;
>  
>  	/* Poke in other ASIC variants here */
> +	if (version == PINCTRL_NMK_STN8815)
> +		nmk_pinctrl_stn8815_init(&npct->soc);
>  	if (version == PINCTRL_NMK_DB8500)
>  		nmk_pinctrl_db8500_init(&npct->soc);

One comment that came up in other reviews is that we shouldn't have a
single driver that switches on the SoC type it's running on and then
dispatches to different ${soc}_init() functions, but rather should have
multiple separate drivers, where each probe calls some utility function
with the appropriate SoC parameterization structures/tables.

IIRC, it was SPEAr, and I appear to have already converted Tegra to that
scheme.

Should we do the same conversion for nomadik too?

Aside from that, the series looks fine.

  reply	other threads:[~2012-06-08 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08  9:07 [PATCH 1/2] pinctrl/nomadik: add STn8815 ASIC support Linus Walleij
2012-06-08 16:39 ` Stephen Warren [this message]
2012-06-12 11:28   ` Linus Walleij
2012-06-12 16:17     ` Stephen Warren
  -- strict thread matches above, loose matches on Subject: below --
2012-08-09 22:43 Linus Walleij
2012-08-10 23:15 ` Stephen Warren

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=4FD22ABA.6010607@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.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