From: Jerome Brunet <jbrunet@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>, linus.walleij@linaro.org
Cc: linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] pinctrl: meson-gxl: Add Ethernet PHY LEDS pins
Date: Wed, 24 May 2017 10:57:01 +0200 [thread overview]
Message-ID: <1495616221.14589.12.camel@baylibre.com> (raw)
In-Reply-To: <1495614042-2676-6-git-send-email-narmstrong@baylibre.com>
On Wed, 2017-05-24 at 10:20 +0200, Neil Armstrong wrote:
> The Amlogic Meson GXL SoCs embeds an 10/100 Ethernet PHY, this patchs enables
> the Link and Activity LEDs signals.
Reviewed-by: Jerome Brunet <jbrunet@baylibre.com>
>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> drivers/pinctrl/meson/pinctrl-meson-gxl.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxl.c
> b/drivers/pinctrl/meson/pinctrl-meson-gxl.c
> index 7d81287..78a9af5 100644
> --- a/drivers/pinctrl/meson/pinctrl-meson-gxl.c
> +++ b/drivers/pinctrl/meson/pinctrl-meson-gxl.c
> @@ -239,6 +239,9 @@
>
> static const unsigned int spdif_out_h_pins[] = { PIN(GPIOH_4, EE_OFF)
> };
>
> +static const unsigned int eth_link_led_pins[] = { PIN(GPIOZ_14,
> EE_OFF) };
> +static const unsigned int eth_act_led_pins[] = { PIN(GPIOZ_15, EE_OFF)
> };
> +
> static const struct pinctrl_pin_desc meson_gxl_aobus_pins[] = {
> MESON_PIN(GPIOAO_0, 0),
> MESON_PIN(GPIOAO_1, 0),
> @@ -437,6 +440,8 @@
> GROUP(i2s_out_ch23_z, 3, 26),
> GROUP(i2s_out_ch45_z, 3, 25),
> GROUP(i2s_out_ch67_z, 3, 24),
> + GROUP(eth_link_led, 4, 25),
> + GROUP(eth_act_led, 4, 24),
>
> /* Bank H */
> GROUP(hdmi_hpd, 6, 31),
> @@ -665,6 +670,10 @@
> "spdif_out_h",
> };
>
> +static const char * const eth_led_groups[] = {
> + "eth_link_led", "eth_act_led",
> +};
> +
> static const char * const gpio_aobus_groups[] = {
> "GPIOAO_0", "GPIOAO_1", "GPIOAO_2", "GPIOAO_3", "GPIOAO_4",
> "GPIOAO_5", "GPIOAO_6", "GPIOAO_7", "GPIOAO_8", "GPIOAO_9",
> @@ -736,6 +745,7 @@
> FUNCTION(hdmi_i2c),
> FUNCTION(i2s_out),
> FUNCTION(spdif_out),
> + FUNCTION(eth_led),
> };
>
> static struct meson_pmx_func meson_gxl_aobus_functions[] = {
next prev parent reply other threads:[~2017-05-24 8:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 8:20 [PATCH 0/5] pinctrl: meson: new pins and fixes round 2 Neil Armstrong
2017-05-24 8:20 ` [PATCH 1/5] pinctrl: meson-gxl: Fix typo in AO I2S pins Neil Armstrong
2017-05-24 8:41 ` Jerome Brunet
2017-05-29 8:57 ` Linus Walleij
2017-05-24 8:20 ` [PATCH 2/5] pinctrl: meson-gxl: Fix typo in AO SPDIF pins Neil Armstrong
2017-05-24 8:42 ` Jerome Brunet
2017-05-29 8:58 ` Linus Walleij
2017-05-24 8:20 ` [PATCH 3/5] pinctrl: meson-gxbb: Add CEC pins Neil Armstrong
2017-05-24 8:53 ` Jerome Brunet
2017-05-29 8:59 ` Linus Walleij
2017-05-24 8:20 ` [PATCH 4/5] pinctrl: meson-gxl: " Neil Armstrong
2017-05-24 8:54 ` Jerome Brunet
2017-05-29 9:00 ` Linus Walleij
2017-05-24 8:20 ` [PATCH 5/5] pinctrl: meson-gxl: Add Ethernet PHY LEDS pins Neil Armstrong
2017-05-24 8:57 ` Jerome Brunet [this message]
2017-05-29 9:01 ` Linus Walleij
2017-05-29 9:17 ` Neil Armstrong
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=1495616221.14589.12.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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 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).