All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Harvey <tharvey@gateworks.com>
To: "Marek Behún" <marek.behun@nic.cz>
Cc: Joe Hershberger <joe.hershberger@ni.com>,
	Ramon Fried <rfried.dev@gmail.com>,
	 Vladimir Oltean <vladimir.oltean@nxp.com>,
	u-boot <u-boot@lists.denx.de>,  Stefano Babic <sbabic@denx.de>,
	Fabio Estevam <festevam@gmail.com>,
	 "NXP i . MX U-Boot Team" <uboot-imx@nxp.com>
Subject: Re: [PATCH 5/6] net: add MV88E61xx DSA driver
Date: Wed, 30 Mar 2022 08:46:06 -0700	[thread overview]
Message-ID: <CAJ+vNU10g+eqkXqNYiBKa8siAxHgKE80bbKPgn0ezfTPU-Bhow@mail.gmail.com> (raw)
In-Reply-To: <20220330012223.71ea3812@thinkpad>

On Tue, Mar 29, 2022 at 4:22 PM Marek Behún <marek.behun@nic.cz> wrote:
>
> On Tue, 29 Mar 2022 15:52:39 -0700
> Tim Harvey <tharvey@gateworks.com> wrote:
>
> > Add a DSA driver for the MV88E61xx compatible GbE Ethernet switches.
> >
> > Signed-off-by: Tim Harvey <tharvey@gateworks.com>
>

Marek,

Thanks for looking at this.

> Is this final version that should be accepted?

This is the first submission of the new driver.

>
> The drivers seems to support not only 61xx, but 6xxx (6096, 6250, 6352,
> ...).

It should also support all the same devices that the non dsa driver it
was derived from (drivers/net/phy/mv88e61xx.c) but I only have a board
with 88E6176 to test with.

It is not completely clear to me what devices are supported in the
original driver per Kconfig but from looking over the code I would say
the following appear to be supported:
mv88e6096
mv88e6097
mv88e6020
mv88e6070
mv88e6071
mv88e6172
mv88e6176
mv88e6220
mv88e6240
mv88e6250
mv88e6352

>
> Also there are some commented lines, for example
>
> > +//   u16 port_stat_link_mask;/* Bitmask for port link status bits */
> > +//   u16 port_stat_dup_mask; /* Bitmask for port duplex status bits */
> > +//   u8 port_stat_speed_width;/* Width of speed status bitfield */
>
> What is their purpose?
>

oops... that was a mistake. I'm surprised checkpatch didn't catch
those. Those were in the non-dsa driver and not used here so will be
removed.

> Why is mv88e61xx_dsa_xmit() no-op?

For DSA dsa-uclass calls the switch master eth device send function
after calling the dsa_ops->xmit function so that a dsa driver can add
any header/footer if needed. The function is required but in my case I
don't care about header/footer tagging or vlan as only 1 port is
active at a time in U-Boot so I just return success.

Best Regards,

Tim

  reply	other threads:[~2022-03-30 15:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 22:52 [PATCH 0/6] Add MV88E61xx DSA driver and use on gwventana Tim Harvey
2022-03-29 22:52 ` [PATCH 1/6] net: mdio-uclass: scan for dm mdio children on post-bind Tim Harvey
2022-04-01 19:40   ` Ramon Fried
2022-03-29 22:52 ` [PATCH 2/6] net: dsa: move cpu port probe to dsa_post_probe Tim Harvey
2022-04-01 19:40   ` Ramon Fried
2022-03-29 22:52 ` [PATCH 3/6] net: mdio-uclass: add wrappers for read/write/reset operations Tim Harvey
2022-03-29 22:52 ` [PATCH 4/6] net: fec: add support for DM_MDIO Tim Harvey
2022-03-31 17:01   ` Vladimir Oltean
2022-03-31 17:48     ` Tim Harvey
2022-03-31 19:36       ` Vladimir Oltean
2022-04-01 17:53         ` Tim Harvey
2022-04-01 19:14           ` Vladimir Oltean
2022-03-29 22:52 ` [PATCH 5/6] net: add MV88E61xx DSA driver Tim Harvey
2022-03-29 23:22   ` Marek Behún
2022-03-30 15:46     ` Tim Harvey [this message]
2022-03-31 10:30       ` Marek Behún
2022-04-01 20:24         ` Tim Harvey
2022-04-02 23:17           ` Vladimir Oltean
2022-04-07 20:33             ` Tim Harvey
2022-04-07 21:31               ` Vladimir Oltean
2022-04-07 23:03                 ` Tim Harvey
2022-04-08  0:26                   ` Marek Behún
2022-04-12 14:13   ` Vladimir Oltean
2022-04-14 21:30     ` Tim Harvey
2022-03-29 22:52 ` [PATCH 6/6] board: gw_ventana: enable MV88E61XX DSA support Tim Harvey
2022-03-30 16:01 ` [PATCH 0/6] Add MV88E61xx DSA driver and use on gwventana Tim Harvey
2022-03-31 20:47   ` Chris Packham

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=CAJ+vNU10g+eqkXqNYiBKa8siAxHgKE80bbKPgn0ezfTPU-Bhow@mail.gmail.com \
    --to=tharvey@gateworks.com \
    --cc=festevam@gmail.com \
    --cc=joe.hershberger@ni.com \
    --cc=marek.behun@nic.cz \
    --cc=rfried.dev@gmail.com \
    --cc=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.com \
    --cc=vladimir.oltean@nxp.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.