linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: imx25-karo-tx25: Fix pincontrol definition
Date: Tue, 24 Mar 2015 20:50:46 +0100	[thread overview]
Message-ID: <20150324195046.GU5664@pengutronix.de> (raw)
In-Reply-To: <1427206147-19365-2-git-send-email-mpa@pengutronix.de>

Hello,

[Cc += Lothar Wa?mann]

On Tue, Mar 24, 2015 at 03:09:07PM +0100, Markus Pargmann wrote:
> The iomux group nodes have to be in a pinmux category as described in
> the devicetree binding documentation example. The current definitions
> are not parsed by imx25-pinctrl.
I remember having noticed that problem, too, some time ago, but forgot
to fix/report it.

> Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> ---
>  arch/arm/boot/dts/imx25-karo-tx25.dts | 84 +++++++++++++++++++----------------
>  1 file changed, 45 insertions(+), 39 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/imx25-karo-tx25.dts b/arch/arm/boot/dts/imx25-karo-tx25.dts
> index 9b31faa96377..11344fb27727 100644
> --- a/arch/arm/boot/dts/imx25-karo-tx25.dts
> +++ b/arch/arm/boot/dts/imx25-karo-tx25.dts
> @@ -42,49 +42,55 @@
>  };
>  
>  &iomuxc {
> -	pinctrl_uart1: uart1grp {
> -		fsl,pins = <
> -			MX25_PAD_UART1_TXD__UART1_TXD 0x80000000
> -			MX25_PAD_UART1_RXD__UART1_RXD 0x80000000
> -			MX25_PAD_UART1_CTS__UART1_CTS 0x80000000
> -			MX25_PAD_UART1_RTS__UART1_RTS 0x80000000
> -		>;
> +	uart1 {
Some other machines (e.g. imx51-babbage) use a big group named after the
machine for all pin groups. Would it be nice to have a uniform rule
here?

I think this grouping is a relict from the time when we considered to
list the groups in the imx$num.dtsi? I would prefer to "fix" the driver
to work with the way imx25-karo-tx25 presents the pinmuxing because I
don't see the motivation for this extra grouping. (So let us define the
current method of imx25-karo-tx25 as the good one to follow if you ask
me.)

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2015-03-24 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 14:09 [PATCH 1/2] ARM: dts: imx25: Add #pwm-cells to pwm4 Markus Pargmann
2015-03-24 14:09 ` [PATCH 2/2] ARM: dts: imx25-karo-tx25: Fix pincontrol definition Markus Pargmann
2015-03-24 19:50   ` Uwe Kleine-König [this message]
2015-03-25 11:02     ` Markus Pargmann
2015-03-25 11:09       ` Uwe Kleine-König
2015-03-29 21:26         ` Markus Pargmann

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=20150324195046.GU5664@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --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).