All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Carlo Caione <carlo@caione.org>,
	"open list:ARM/Amlogic Meson..."
	<linux-amlogic@lists.infradead.org>,
	Kevin Hilman <khilman@baylibre.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] pinctrl: meson: meson8b: fix the NAND DQS pins
Date: Fri, 7 Apr 2017 09:29:53 +0200	[thread overview]
Message-ID: <CACRpkdbc9BqTAo-KbqVdeJ5ZS1K5ikepdvz_-ScjcX_sDvioPA@mail.gmail.com> (raw)
In-Reply-To: <20170401135922.1288-2-martin.blumenstingl@googlemail.com>

On Sat, Apr 1, 2017 at 3:59 PM, Martin Blumenstingl
<martin.blumenstingl@googlemail.com> wrote:

> The nand_groups table uses different names for the NAND DQS pins than
> the GROUP() definition in meson8b_cbus_groups (nand_dqs_0 vs nand_dqs0).
> This prevents using the NAND DQS pins in the devicetree.
>
> Fix this by ensuring that the GROUP() definition and the
> meson8b_cbus_groups use the same name for these pins.
>
> Fixes: 0fefcb6876d0 ("pinctrl: Add support for Meson8b")
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>

Patch applied with Kevin's ACK.

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] pinctrl: meson: meson8b: fix the NAND DQS pins
Date: Fri, 7 Apr 2017 09:29:53 +0200	[thread overview]
Message-ID: <CACRpkdbc9BqTAo-KbqVdeJ5ZS1K5ikepdvz_-ScjcX_sDvioPA@mail.gmail.com> (raw)
In-Reply-To: <20170401135922.1288-2-martin.blumenstingl@googlemail.com>

On Sat, Apr 1, 2017 at 3:59 PM, Martin Blumenstingl
<martin.blumenstingl@googlemail.com> wrote:

> The nand_groups table uses different names for the NAND DQS pins than
> the GROUP() definition in meson8b_cbus_groups (nand_dqs_0 vs nand_dqs0).
> This prevents using the NAND DQS pins in the devicetree.
>
> Fix this by ensuring that the GROUP() definition and the
> meson8b_cbus_groups use the same name for these pins.
>
> Fixes: 0fefcb6876d0 ("pinctrl: Add support for Meson8b")
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>

Patch applied with Kevin's ACK.

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 1/2] pinctrl: meson: meson8b: fix the NAND DQS pins
Date: Fri, 7 Apr 2017 09:29:53 +0200	[thread overview]
Message-ID: <CACRpkdbc9BqTAo-KbqVdeJ5ZS1K5ikepdvz_-ScjcX_sDvioPA@mail.gmail.com> (raw)
In-Reply-To: <20170401135922.1288-2-martin.blumenstingl@googlemail.com>

On Sat, Apr 1, 2017 at 3:59 PM, Martin Blumenstingl
<martin.blumenstingl@googlemail.com> wrote:

> The nand_groups table uses different names for the NAND DQS pins than
> the GROUP() definition in meson8b_cbus_groups (nand_dqs_0 vs nand_dqs0).
> This prevents using the NAND DQS pins in the devicetree.
>
> Fix this by ensuring that the GROUP() definition and the
> meson8b_cbus_groups use the same name for these pins.
>
> Fixes: 0fefcb6876d0 ("pinctrl: Add support for Meson8b")
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>

Patch applied with Kevin's ACK.

Yours,
Linus Walleij

  parent reply	other threads:[~2017-04-07  7:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-25 18:43 [PATCH 0/1] pinctrl-meson8b: fix the NAND DQS pin definitions Martin Blumenstingl
2017-03-25 18:43 ` Martin Blumenstingl
2017-03-25 18:43 ` Martin Blumenstingl
2017-03-25 18:43 ` [PATCH 1/1] pinctrl: meson: meson8b: fix the NAND DQS pins Martin Blumenstingl
2017-03-25 18:43   ` Martin Blumenstingl
2017-03-25 18:43   ` Martin Blumenstingl
2017-03-28 15:09   ` Kevin Hilman
2017-03-28 15:09     ` Kevin Hilman
2017-03-28 15:09     ` Kevin Hilman
2017-03-28 21:26     ` Martin Blumenstingl
2017-03-28 21:26       ` Martin Blumenstingl
2017-03-28 21:26       ` Martin Blumenstingl
2017-04-01 13:59 ` [PATCH v2 0/2] pinctrl-meson8b: fix the NAND DQS pin definitions Martin Blumenstingl
2017-04-01 13:59   ` Martin Blumenstingl
2017-04-01 13:59   ` Martin Blumenstingl
2017-04-01 13:59   ` [PATCH v2 1/2] pinctrl: meson: meson8b: fix the NAND DQS pins Martin Blumenstingl
2017-04-01 13:59     ` Martin Blumenstingl
2017-04-01 13:59     ` Martin Blumenstingl
2017-04-03 16:07     ` Kevin Hilman
2017-04-03 16:07       ` Kevin Hilman
2017-04-03 16:07       ` Kevin Hilman
2017-04-07  7:29     ` Linus Walleij [this message]
2017-04-07  7:29       ` Linus Walleij
2017-04-07  7:29       ` Linus Walleij
2017-04-01 13:59   ` [PATCH v2 2/2] pinctrl: meson: meson8b: rename the NAND DQS pin definitions Martin Blumenstingl
2017-04-01 13:59     ` Martin Blumenstingl
2017-04-01 13:59     ` Martin Blumenstingl
2017-04-03 16:08     ` Kevin Hilman
2017-04-03 16:08       ` Kevin Hilman
2017-04-03 16:08       ` Kevin Hilman
2017-04-07  7:31     ` Linus Walleij
2017-04-07  7:31       ` Linus Walleij
2017-04-07  7:31       ` Linus Walleij

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=CACRpkdbc9BqTAo-KbqVdeJ5ZS1K5ikepdvz_-ScjcX_sDvioPA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=carlo@caione.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    /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.