[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YnxYtE9dGn6BwF/8@lunn.ch>
Date: Thu, 12 May 2022 02:45:40 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Cc: "robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"will@...nel.org" <will@...nel.org>,
"gregory.clement@...tlin.com" <gregory.clement@...tlin.com>,
"sebastian.hesselbarth@...il.com" <sebastian.hesselbarth@...il.com>,
"kostap@...vell.com" <kostap@...vell.com>,
"robert.marko@...tura.hr" <robert.marko@...tura.hr>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v6 1/3] dt-bindings: marvell: Document the AC5/AC5X
compatibles
> Yes there are registers that you can read to identify the specific chip.
>
> It still might be useful to have a expected vs actual check as those ID
> values are determined by pin strapping resistors.
That i don't get? Can i turn a
* 98DX2538: 24x1G + 2x10G + 2x10G Stack
into a
* 98DX2535: 24x1G + 4x1G Stack
by strapping its pin differently?
> It could also be used
> to validate the dts (e.g. port 20 would be invalid on a 98DX3501). But
> those are considerations for further down the track.
Yes, that would be up to the switchdev driver to validate the DT based
on the ID register.
Andrew
Powered by blists - more mailing lists