[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190508094132.GB13389@t480s.localdomain>
Date: Wed, 8 May 2019 09:41:32 -0400
From: Vivien Didelot <vivien.didelot@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Rasmus Villemoes <rasmus.villemoes@...vas.dk>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>
Subject: Re: [RFC PATCH 1/5] net: dsa: mv88e6xxx: introduce support for two
chips using direct smi addressing
Hi Rasmus,
On Wed, 8 May 2019 13:47:15 +0200, Andrew Lunn <andrew@...n.ch> wrote:
> > >
> > > This works, but i think i prefer adding mv88e6xxx_smi_dual_chip_write,
> > > mv88e6xxx_smi_dual_chip_read, and create a
> > > mv88e6xxx_smi_single_chip_ops.
> >
> > Now that Vivien's "net: dsa: mv88e6xxx: refine SMI support" is in
> > master, do you still prefer introducing a third bus_ops structure
> > (mv88e6xxx_smi_dual_direct_ops ?), or would the approach of adding
> > chip->sw_addr in the smi_direct_{read/write} functions be ok (which
> > would then require changing the indirect callers to pass 0 instead of
> > chip->swaddr).
>
> I would still prefer a new bus_ops.
Even though those are direct read and write operations, having 3
mv88e6xxx_bus_ops structures will make it clear that there are 3 ways
for accessible the internal switch registers through SMI, depending
on the Marvell chip model. So I would prefer a third ops as well.
Thanks,
Vivien
Powered by blists - more mailing lists