netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: fugang.duan@nxp.com
Cc: andrew@lunn.ch, martin.fuzzey@flowbird.group,
	davem@davemloft.net, netdev@vger.kernel.org, robh+dt@kernel.org,
	shawnguo@kernel.org, devicetree@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH net v2 1/4] net: ethernet: fec: move GPR register offset and bit into DT
Date: Mon, 25 May 2020 12:48:49 +0200	[thread overview]
Message-ID: <20200525104849.GQ11869@pengutronix.de> (raw)
In-Reply-To: <1590390569-4394-2-git-send-email-fugang.duan@nxp.com>

On Mon, May 25, 2020 at 03:09:26PM +0800, fugang.duan@nxp.com wrote:
> From: Fugang Duan <fugang.duan@nxp.com>
> 
> The commit da722186f654 (net: fec: set GPR bit on suspend by DT
> configuration) set the GPR reigster offset and bit in driver for
> wake on lan feature.
> 
> But it introduces two issues here:
> - one SOC has two instances, they have different bit
> - different SOCs may have different offset and bit
> 
> So to support wake-on-lan feature on other i.MX platforms, it should
> configure the GPR reigster offset and bit from DT.
> 
> So the patch is to improve the commit da722186f654 (net: fec: set GPR
> bit on suspend by DT configuration) to support multiple ethernet
> instances on i.MX series.
> 
> v2:
>  * switch back to store the quirks bitmask in driver_data
> 
> Signed-off-by: Fugang Duan <fugang.duan@nxp.com>
> ---
>  drivers/net/ethernet/freescale/fec_main.c | 103 ++++++++++--------------------
>  1 file changed, 34 insertions(+), 69 deletions(-)
> 
> diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
> index 2e20914..4f55d30 100644
> --- a/drivers/net/ethernet/freescale/fec_main.c
> +++ b/drivers/net/ethernet/freescale/fec_main.c
> @@ -86,56 +86,6 @@ static void fec_enet_itr_coal_init(struct net_device *ndev);
>  #define FEC_ENET_OPD_V	0xFFF0
>  #define FEC_MDIO_PM_TIMEOUT  100 /* ms */
>  
> -struct fec_devinfo {
> -	u32 quirks;
> -	u8 stop_gpr_reg;
> -	u8 stop_gpr_bit;
> -};

Honestly I like the approach of having a struct fec_devinfo for
abstracting differences between different hardware variants. It gives
you more freedom to describe the differences. Converting this back to a
single bitfield is a step backward, even when currently struct
fec_devinfo only contains a single value.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2020-05-25 10:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  7:09 [PATCH net v2 0/4] net: ethernet: fec: move GPR reigster offset and bit into DT fugang.duan
2020-05-25  7:09 ` [PATCH net v2 1/4] net: ethernet: fec: move GPR register " fugang.duan
2020-05-25 10:48   ` Sascha Hauer [this message]
2020-05-25 15:38     ` [EXT] " Andy Duan
2020-05-25  7:09 ` [PATCH net v2 2/4] dt-bindings: fec: update the gpr property fugang.duan
2020-05-25  7:09 ` [PATCH net v2 3/4] ARM: dts: imx: add ethernet stop mode property fugang.duan
2020-05-25 13:51   ` Andrew Lunn
2020-05-25 15:39     ` [EXT] " Andy Duan
2020-05-25  7:09 ` [PATCH net v2 4/4] ARM: dts: imx6qdl-sabresd: enable fec wake-on-lan fugang.duan
2020-05-25 13:51   ` Andrew Lunn
2020-05-25 15:40     ` [EXT] " Andy Duan
2020-05-25 13:54 ` [PATCH net v2 0/4] net: ethernet: fec: move GPR reigster offset and bit into DT Andrew Lunn
2020-05-25 15:41   ` [EXT] " Andy Duan

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=20200525104849.GQ11869@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=fugang.duan@nxp.com \
    --cc=kuba@kernel.org \
    --cc=martin.fuzzey@flowbird.group \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.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).