From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 2/2] pinctrl: meson: meson8b: rename the NAND DQS pin definitions
Date: Mon, 03 Apr 2017 09:08:45 -0700 [thread overview]
Message-ID: <m28tnha2ya.fsf@baylibre.com> (raw)
In-Reply-To: <20170401135922.1288-3-martin.blumenstingl@googlemail.com> (Martin Blumenstingl's message of "Sat, 1 Apr 2017 15:59:22 +0200")
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> The NAND DQS pins are currently named nand_dqs_0 and nand_dqs_1.
> However, they both seem to have the same function, just exposed on
> different pins (unlike the ethernet TX pins for example, where there's
> eth_txd0..3 - all of these can be active at the same time as they are
> different data lines).
> Rename the NAND DQS pins to nand_dqs_15 and nand_dqs_18 to reflect that
> it's the same functionality just exposed on different pins (BOOT_15 and
> BOOT_18).
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Since we don't yet have any users of these pins, LGTM.
Acked-by: Kevin Hilman <khilman@baylibre.com>
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, linux-gpio@vger.kernel.org,
carlo@caione.org, linus.walleij@linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] pinctrl: meson: meson8b: rename the NAND DQS pin definitions
Date: Mon, 03 Apr 2017 09:08:45 -0700 [thread overview]
Message-ID: <m28tnha2ya.fsf@baylibre.com> (raw)
In-Reply-To: <20170401135922.1288-3-martin.blumenstingl@googlemail.com> (Martin Blumenstingl's message of "Sat, 1 Apr 2017 15:59:22 +0200")
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> The NAND DQS pins are currently named nand_dqs_0 and nand_dqs_1.
> However, they both seem to have the same function, just exposed on
> different pins (unlike the ethernet TX pins for example, where there's
> eth_txd0..3 - all of these can be active at the same time as they are
> different data lines).
> Rename the NAND DQS pins to nand_dqs_15 and nand_dqs_18 to reflect that
> it's the same functionality just exposed on different pins (BOOT_15 and
> BOOT_18).
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Since we don't yet have any users of these pins, LGTM.
Acked-by: Kevin Hilman <khilman@baylibre.com>
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] pinctrl: meson: meson8b: rename the NAND DQS pin definitions
Date: Mon, 03 Apr 2017 09:08:45 -0700 [thread overview]
Message-ID: <m28tnha2ya.fsf@baylibre.com> (raw)
In-Reply-To: <20170401135922.1288-3-martin.blumenstingl@googlemail.com> (Martin Blumenstingl's message of "Sat, 1 Apr 2017 15:59:22 +0200")
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> The NAND DQS pins are currently named nand_dqs_0 and nand_dqs_1.
> However, they both seem to have the same function, just exposed on
> different pins (unlike the ethernet TX pins for example, where there's
> eth_txd0..3 - all of these can be active at the same time as they are
> different data lines).
> Rename the NAND DQS pins to nand_dqs_15 and nand_dqs_18 to reflect that
> it's the same functionality just exposed on different pins (BOOT_15 and
> BOOT_18).
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Since we don't yet have any users of these pins, LGTM.
Acked-by: Kevin Hilman <khilman@baylibre.com>
next prev parent reply other threads:[~2017-04-03 16:08 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
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 [this message]
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=m28tnha2ya.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@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 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.