From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: "Marek Behún" <marek.behun@nic.cz>, arm@kernel.org
Cc: Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v2 mvebu-dt64 0/3] Add Turris Mox device-tree
Date: Fri, 30 Aug 2019 22:20:18 +0200 [thread overview]
Message-ID: <874l1yxv5p.fsf@FE-laptop> (raw)
In-Reply-To: <20190828151243.23542-1-marek.behun@nic.cz>
Hi Marek,
> Hello, this is the second version of patches adding Turris Mox dts.
> I have addressed Andrew's comments about led label, reset button
> function and sfp i2c bus speed. The other issues I have explained
> in reply to Andrew. Here is a copy of those:
>
>> > The node is called i2c0, but here you have i2c1_pins?
>
>> That is how this is defined in armada-37xx.dtsi. First i2c has
>> phandle pointer called i2c0, second i2c1. But the pinctrl drivers uses
>> i2c1 and i2c2. All device trees need to be changed for this. This can
>> be done later in a separate commit for all device trees using
>> armada-37xx.dtsi
>
>> > > > +&pcie_reset_pins {
>> > > > + function = "gpio";
>> > > > +};
>> >
>> > Should there be something to indicate which GPIO?
>
>> No. The thing here is that the function here should remain "pcie"
>> ideally. When that pin is configured in pcie mode, modifying specific
>> pcie register should control the pin. But for some reason on our SOC
>> it does not. I suspect it does not work for Miquel Raynal either,
>> since he sent patches for aardvark that use reset-gpio as well (see
>> https://lkml.org/lkml/2018/12/12/242 ).
>> So we configure it in gpio mode and than in the pcie node we have
>> reset-gpios = <&gpiosb 3 GPIO_ACTIVE_LOW>;
>
>> > Does u-boot also modify this, if switch2 does not exist? I don't
>> > know if it actually matters, but if the switch does not exist, but
>> > the routing entry exists, this switch might still send it frames and
>> > use up some of your bandwidth?
>
>> That port has status = "disabled" by default. U-Boot enables that node
>> if second switch is present. U-Boot removes all disabled nodes before
>> boot. Even if it did not, kernel ignores disabled nodes here.
>
> Marek
>
> Marek Behún (3):
> arm64: dts: marvell: armada-37xx: add SPI CS1 pinctrl
> dt-bindings: marvell: document Turris Mox compatible
> arm64: dts: marvell: add DTS for Turris Mox
The 3 patches are applied on mvebu/dt64
Thanks,
Gregory
>
> .../bindings/arm/marvell/armada-37xx.txt | 8 +
> arch/arm64/boot/dts/marvell/Makefile | 1 +
> .../dts/marvell/armada-3720-turris-mox.dts | 840 ++++++++++++++++++
> arch/arm64/boot/dts/marvell/armada-37xx.dtsi | 5 +
> 4 files changed, 854 insertions(+)
> create mode 100644 arch/arm64/boot/dts/marvell/armada-3720-turris-mox.dts
>
> --
> 2.21.0
>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2019-08-30 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 15:12 [PATCH v2 mvebu-dt64 0/3] Add Turris Mox device-tree Marek Behún
2019-08-28 15:12 ` [PATCH v2 mvebu-dt64 1/3] arm64: dts: marvell: armada-37xx: add SPI CS1 pinctrl Marek Behún
2019-08-28 15:12 ` [PATCH v2 mvebu-dt64 2/3] dt-bindings: marvell: document Turris Mox compatible Marek Behún
2019-08-28 15:12 ` [PATCH v2 mvebu-dt64 3/3] arm64: dts: marvell: add DTS for Turris Mox Marek Behún
2019-08-29 1:09 ` Andrew Lunn
2019-08-30 20:20 ` Gregory CLEMENT [this message]
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=874l1yxv5p.fsf@FE-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=robh@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox