From: Alex Marginean <alexm.osslist@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] net: mdio-uclass: name MDIO according to device-name property if preset
Date: Tue, 23 Jul 2019 09:51:18 +0300 [thread overview]
Message-ID: <d02fc202-4ff6-5a8a-924e-bc38926ef84f@gmail.com> (raw)
In-Reply-To: <CAEUhbmVqCo=PLtVJ3V7DFy1B+G+Oxn4ojypiK7sftdqvbeqnig@mail.gmail.com>
On 7/23/2019 9:38 AM, Bin Meng wrote:
> On Wed, Jul 17, 2019 at 11:11 PM Alex Marginean
> <alexandru.marginean@nxp.com> wrote:
>>
>> Use the optional property device-name to name the MDIO bus. This works
>> around limitations with using the DT node name on devices such as
>> Armada-8040, which integrates two cp100 cores, both featuring MDIOs at the
>> same relative offsets and with the same DT node names.
>> The concept was originally proposed by Marvell as a custom property called
>> mdio-name specific to Marvell driver. This patch uses the more generic
>
> I was wondering whether such optional custom property name is accepted
> by the Linux devicetree committee or yet? The general goal is to use
> exact the same DT as kernel uses, at least for ARM, and that is what I
> learned from this ML.
I didn't ask, my guess is they would not. The property is not actually
describing HW, plus Linux wouldn't need this name anyway. As far as I
know MDIOs in Linux are not addressable directly using user-space tools
and for the purpose of probing devices and matching ethernet/PHY/MDIO
this property is not useful. U-Boot on the other hand has the mdio cmd
which requires unique names and also benefits from friendly names for
MDIO buses.
There are other potential solutions for the unique name problem, like
creating something out of the full DT path of the device, or resolve
absolute base address and use that. These aren't as easy to use though.
Alex
>
>> property device-name and moves this into MDIO class code so other can use
>> it as well.
>>
>> Signed-off-by: Alex Marginean <alexm.osslist@gmail.com>
>> ---
>> net/mdio-uclass.c | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>
> Anyway, the codes LGTM. So
>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
>
> Regards,
> Bin
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
>
next prev parent reply other threads:[~2019-07-23 6:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 15:10 [U-Boot] [PATCH 0/4] Marvell MDIO driver and new MDIO name property Alex Marginean
2019-07-17 15:10 ` [U-Boot] [PATCH 1/4] net: mdio-uclass: name MDIO according to device-name property if preset Alex Marginean
2019-07-23 0:21 ` Joe Hershberger
2019-07-23 6:38 ` Bin Meng
2019-07-23 6:51 ` Alex Marginean [this message]
2019-07-23 7:03 ` Bin Meng
2019-07-17 15:10 ` [U-Boot] [PATCH 2/4] doc: bindings: add mdio.txt describing generic MDIO properties Alex Marginean
2019-07-23 0:30 ` Joe Hershberger
2019-07-23 6:39 ` Bin Meng
2019-07-17 15:10 ` [U-Boot] [PATCH 3/4] drivers: net: add marvell MDIO driver Alex Marginean
2019-07-23 0:27 ` Joe Hershberger
2019-07-17 15:10 ` [U-Boot] [PATCH 4/4] arm: dts: Set custom names for cp110 master/slave MDIO buses Alex Marginean
2019-07-23 0:29 ` Joe Hershberger
2019-07-23 15:17 ` Nevo Hed
2019-07-23 17:03 ` Nevo Hed
2019-07-23 17:22 ` Nevo Hed
2019-07-24 13:05 ` Alex Marginean
2019-07-24 18:57 ` Joe Hershberger
2019-07-17 19:09 ` [U-Boot] [PATCH 0/4] Marvell MDIO driver and new MDIO name property Alex Marginean
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=d02fc202-4ff6-5a8a-924e-bc38926ef84f@gmail.com \
--to=alexm.osslist@gmail.com \
--cc=u-boot@lists.denx.de \
/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