[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220516224801.1656752-1-chris.packham@alliedtelesis.co.nz>
Date: Tue, 17 May 2022 10:47:59 +1200
From: Chris Packham <chris.packham@...iedtelesis.co.nz>
To: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, andrew@...n.ch,
gregory.clement@...tlin.com, sebastian.hesselbarth@...il.com,
kabel@...nel.org
Cc: netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Chris Packham <chris.packham@...iedtelesis.co.nz>
Subject: [PATCH 0/2] armada-3720-turris-mox and orion-mdio
This is a follow up to the change that converted the orion-mdio dt-binding from
txt to DT schema format. At the time I thought the binding needed
'unevaluatedProperties: false' because the core mdio.yaml binding didn't handle
the DSA switches. In reality it was simply the invalid reg property causing the
downstream nodes to be unevaluated. Fixing the reg nodes means we can set
'unevaluatedProperties: true'
Marek,
I don't know if you had a change for the reg properties in flight. I didn't see
anything on lore/lkml so sorry if this crosses with something you've done.
Chris Packham (2):
arm64: dts: armada-3720-turris-mox: Correct reg property for mdio
devices
dt-bindings: net: marvell,orion-mdio: Set unevaluatedProperties to
false
.../devicetree/bindings/net/marvell,orion-mdio.yaml | 2 +-
.../boot/dts/marvell/armada-3720-turris-mox.dts | 12 ++++++------
2 files changed, 7 insertions(+), 7 deletions(-)
--
2.36.1
Powered by blists - more mailing lists