From: Marek Behun <marek.behun@nic.cz>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Gregory CLEMENT <gregory.clement@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH RFC] ARM64: dts: marvell: Add DTS file for Turris Mox
Date: Thu, 13 Dec 2018 05:08:29 +0100 [thread overview]
Message-ID: <20181213050829.6d942510@nic.cz> (raw)
In-Reply-To: <20181204203706.GA25038@bogus>
Hi Rob
On Tue, 4 Dec 2018 14:37:06 -0600
Rob Herring <robh@kernel.org> wrote:
> > +
> > + switch1@2 {
>
> Ideally, we shouldn't have this switch0, switch1, etc.
I can rename peridot switches (switch0@10, switch1@11, switch2@12 to
swtich@10, switch@11, switch@12), but I cannot rename Topaz to
switch@2. Topaz always has MDIO address 2, because there can be only
one, but it can be connected either directly or after the first or
second peridot. Therefore I have three different nodes, each describing
different connection to the previous switch/cpu.
How should I rename it?
Marek
WARNING: multiple messages have this Message-ID (diff)
From: Marek Behun <marek.behun@nic.cz>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
Gregory CLEMENT <gregory.clement@bootlin.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH RFC] ARM64: dts: marvell: Add DTS file for Turris Mox
Date: Thu, 13 Dec 2018 05:08:29 +0100 [thread overview]
Message-ID: <20181213050829.6d942510@nic.cz> (raw)
In-Reply-To: <20181204203706.GA25038@bogus>
Hi Rob
On Tue, 4 Dec 2018 14:37:06 -0600
Rob Herring <robh@kernel.org> wrote:
> > +
> > + switch1@2 {
>
> Ideally, we shouldn't have this switch0, switch1, etc.
I can rename peridot switches (switch0@10, switch1@11, switch2@12 to
swtich@10, switch@11, switch@12), but I cannot rename Topaz to
switch@2. Topaz always has MDIO address 2, because there can be only
one, but it can be connected either directly or after the first or
second peridot. Therefore I have three different nodes, each describing
different connection to the previous switch/cpu.
How should I rename it?
Marek
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-13 4:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 13:44 [PATCH RFC] ARM64: dts: marvell: Add DTS file for Turris Mox Marek Behún
2018-11-13 13:44 ` Marek Behún
2018-12-04 20:37 ` Rob Herring
2018-12-04 20:37 ` Rob Herring
2018-12-13 4:08 ` Marek Behun [this message]
2018-12-13 4:08 ` Marek Behun
2019-01-18 14:35 ` Gregory CLEMENT
2019-01-18 14:35 ` Gregory CLEMENT
2019-01-21 13:12 ` Marek Behún
2019-01-21 13:12 ` Marek Behún
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=20181213050829.6d942510@nic.cz \
--to=marek.behun@nic.cz \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.