From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] pinctrl: add ethernet pin groups to r8a7740
Date: Fri, 25 Jan 2013 10:15:48 +0000 [thread overview]
Message-ID: <2776240.reRXLDdyXo@avalon> (raw)
In-Reply-To: <1359043653-11374-2-git-send-email-g.liakhovetski@gmx.de>
Hi Guennadi,
Thanks for the patch.
On Thursday 24 January 2013 17:07:31 Guennadi Liakhovetski wrote:
> r8a7740 SoCs have an integrated gigabit ethernet MAC. This patch adds two
> pin groups: base for 100mbps and additional pins for the gigabit mode.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> ---
> drivers/pinctrl/sh-pfc/pfc-r8a7740.c | 31 +++++++++++++++++++++++++++++++
> 1 files changed, 31 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a7740.c
> b/drivers/pinctrl/sh-pfc/pfc-r8a7740.c index 4c92af8..d7f69dd 100644
> --- a/drivers/pinctrl/sh-pfc/pfc-r8a7740.c
> +++ b/drivers/pinctrl/sh-pfc/pfc-r8a7740.c
> @@ -2052,6 +2052,29 @@ static const unsigned int mmc0_ctrl_1_mux[] = {
> MMC1_CMD_PORT104_MARK, MMC1_CLK_PORT103_MARK,
> };
>
> +static const unsigned int eth_base_pins[] = {
> + 203, 204, 205, 206, 207,
> + 183, 184,
> + 185, 186, 187, 188,
> + 171, 170, 169, 168,
> + 161, 163, 164, 174,
> +};
> +static const unsigned int eth_base_mux[] = {
> + ET_TX_ER_MARK, ET_RX_ER_MARK, ET_CRS_MARK, ET_MDC_MARK, ET_MDIO_MARK,
> + ET_TX_EN_MARK, ET_TX_CLK_MARK,
> + ET_ERXD0_MARK, ET_ERXD1_MARK, ET_ERXD2_MARK, ET_ERXD3_MARK,
> + ET_ETXD0_MARK, ET_ETXD1_MARK, ET_ETXD2_MARK, ET_ETXD3_MARK,
> + ET_RX_DV_MARK, ET_COL_MARK, ET_PHY_INT_MARK, ET_RX_CLK_MARK,
> +};
> +static const unsigned int eth_gbit_pins[] = {
> + 189, 190, 191, 192,
> + 167, 166, 173, 172,
> +};
> +static const unsigned int eth_gbit_mux[] = {
> + ET_ERXD4_MARK, ET_ERXD5_MARK, ET_ERXD6_MARK, ET_ERXD7_MARK,
> + ET_ETXD4_MARK, ET_ETXD5_MARK, ET_ETXD6_MARK, ET_ETXD7_MARK,
> +};
> +
> static const struct sh_pfc_pin_group pinmux_groups[] = {
> SH_PFC_PIN_GROUP(lcd0_data8),
> SH_PFC_PIN_GROUP(lcd0_data9),
> @@ -2100,6 +2123,8 @@ static const struct sh_pfc_pin_group pinmux_groups[] > { SH_PFC_PIN_GROUP(mmc0_data4_1),
> SH_PFC_PIN_GROUP(mmc0_data8_1),
> SH_PFC_PIN_GROUP(mmc0_ctrl_1),
> + SH_PFC_PIN_GROUP(eth_base),
> + SH_PFC_PIN_GROUP(eth_gbit),
> };
>
> static const char * const lcd0_groups[] = {
> @@ -2167,6 +2192,11 @@ static const char * const mmc0_groups[] = {
> "mmc0_ctrl_1",
> };
>
> +static const char * const eth_groups[] = {
> + "eth_base",
> + "eth_gbit",
> +};
> +
What about calling the groups mdio (for management), mii, gmii and rmii ? You
can duplicate common pins in mii and gmii.
The WOL, GTK_CLK and LINK pins are missing BTW.
> static const struct sh_pfc_function pinmux_functions[] = {
> SH_PFC_FUNCTION(lcd0),
> SH_PFC_FUNCTION(lcd1),
> @@ -2174,6 +2204,7 @@ static const struct sh_pfc_function pinmux_functions[]
> = { SH_PFC_FUNCTION(sdhi1),
> SH_PFC_FUNCTION(sdhi2),
> SH_PFC_FUNCTION(mmc0),
> + SH_PFC_FUNCTION(eth),
> };
>
> #define PINMUX_FN_BASE ARRAY_SIZE(pinmux_pins)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-01-25 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 16:07 [PATCH 0/3] ARM: shmobile: sh-eth pins in DT for armadillo800eva Guennadi Liakhovetski
2013-01-24 16:07 ` [PATCH 1/3] pinctrl: add ethernet pin groups to r8a7740 Guennadi Liakhovetski
2013-01-25 10:15 ` Laurent Pinchart [this message]
2013-01-24 16:07 ` [PATCH/RFC 2/3] ethernet: add a PHY reset GPIO DT binding to sh_eth Guennadi Liakhovetski
2013-01-25 10:21 ` Laurent Pinchart
2013-01-25 10:34 ` Guennadi Liakhovetski
2013-01-25 18:21 ` Jason Gunthorpe
2013-07-08 10:49 ` Guennadi Liakhovetski
2013-01-26 1:04 ` Laurent Pinchart
2013-01-24 16:07 ` [PATCH 3/3] ARM: shmobile: move pin configuration on armadillo800eva-reference to DT Guennadi Liakhovetski
2013-01-25 4:37 ` [PATCH 0/3] ARM: shmobile: sh-eth pins in DT for armadillo800eva Simon Horman
2013-01-25 8:09 ` Guennadi Liakhovetski
2013-01-25 9:05 ` Simon Horman
2013-01-25 9:57 ` Laurent Pinchart
2013-01-28 1:02 ` Simon Horman
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=2776240.reRXLDdyXo@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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).