[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221114100643.14ec2dc6@wsk>
Date: Mon, 14 Nov 2022 10:06:43 +0100
From: Lukasz Majewski <lukma@...x.de>
To: Andrew Lunn <andrew@...n.ch>
Cc: Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org
Subject: Re: [PATCH 7/9] net: dsa: mv88e6071: Define max frame size (2048
bytes)
Hi Andrew,
> On Thu, Nov 10, 2022 at 04:42:36PM +0100, Lukasz Majewski wrote:
> > Hi Andrew,
> >
> > > On Tue, Nov 08, 2022 at 09:23:28AM +0100, Lukasz Majewski wrote:
> > > > Accroding to the documentation - the mv88e6071 can support
> > > > frame size up to 2048 bytes.
> > >
> > > Since the mv88e6020 is in the same family, it probably is the
> > > same?
> >
> > Yes it is 2048 B
> >
> > > And what about the mv88e66220?
> >
> > You mean mv88e6220 ?
>
> Upps, sorry, yes.
>
> >
> > IIRC they are from the same family of ICs, so my guess :-) is that
> > they also have the same value.
>
> My point being, you created a new _ops structure when i don't think it
> is needed.
This was mostly my precaution to not introduce regression for other
supported ICs.
However, this shall not be the problem as long as the max supported
frame size is set for each of it. Then calling set_max_frame_size()
callback will always provide correct value.
>
> Andrew
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@...x.de
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists