From: Linus Walleij <linus.walleij@linaro.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Anand Gore" <anand.gore@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/8] ARM: dts: bcm6846: Add MDIO control block
Date: Fri, 11 Oct 2024 08:55:46 +0200 [thread overview]
Message-ID: <CACRpkdawVVt8_2jRfJebUHBMLPCUaj76gieM=FqBbEL2yxwsbQ@mail.gmail.com> (raw)
In-Reply-To: <b542b2e8-115c-4234-a464-e73aa6bece5c@broadcom.com>
On Fri, Oct 11, 2024 at 12:11 AM Florian Fainelli
<florian.fainelli@broadcom.com> wrote:
> On 10/10/24 15:07, Linus Walleij wrote:
> > This adds the MDIO block found in the BCM6846. The vendor tree
> > calls it "mdio5" so we assume the right compatible for this
> > particular version is "brcm,genet-mdio-v5".
>
> That the same IP block be present on systems using GENET and BCMBCA
> routers, absolutely, but it is not really the same. The one present on
> BCM6846 has an extra pair of registers adjacent to it:
>
> LVL_IRQ_CLEAR
> LVL_IRQ_MASK
>
> There are other differences like bit 13 defining a "free running" MDIO
> clock, that has never been present in any of the GENET or ASP variants
> of mdio-bcm-unimac.
>
> Therefore an updated compatible string would be in order IMHO, thanks!
OK I fix!
Is it the same block on all the BCMBCA variants so I should call it
"brcm,bcmbca-mdio" or is it bcm6846-specific so I should call it
"brcm,bcm6846-mdio"?
Yours,
Linus Walleij
next prev parent reply other threads:[~2024-10-11 6:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 22:06 [PATCH 0/8] ARM: dts: Add some BCM6846 device tree Linus Walleij
2024-10-10 22:06 ` [PATCH 1/8] ARM: dts: bcm6846: Add iproc rng Linus Walleij
2024-10-10 22:07 ` [PATCH 2/8] ARM: dts: bcm6846: Enable watchdog Linus Walleij
2024-10-10 22:07 ` [PATCH 3/8] ARM: dts: bcm6846: Add GPIO blocks Linus Walleij
2024-10-10 22:07 ` [PATCH 4/8] ARM: dts: bcm6846: Add MDIO control block Linus Walleij
2024-10-10 22:11 ` Florian Fainelli
2024-10-11 6:55 ` Linus Walleij [this message]
2024-10-10 22:07 ` [PATCH 5/8] ARM: dts: bcm6846: Add LED controller Linus Walleij
2024-10-10 22:07 ` [PATCH 6/8] dt-bindings: vendor-prefixes: Add Genexis Linus Walleij
2024-10-11 14:28 ` Rob Herring (Arm)
2024-10-10 22:07 ` [PATCH 7/8] dt-bindings: arm: bcmbca: Add Genexis XG6846B Linus Walleij
2024-10-11 14:29 ` Rob Herring (Arm)
2024-10-10 22:07 ` [PATCH 8/8] ARM: dts: broadcom: Add Genexis XG6846B DTS file Linus Walleij
2024-10-14 14:05 ` [PATCH 0/8] ARM: dts: Add some BCM6846 device tree Rob Herring (Arm)
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='CACRpkdawVVt8_2jRfJebUHBMLPCUaj76gieM=FqBbEL2yxwsbQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=william.zhang@broadcom.com \
/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;
as well as URLs for NNTP newsgroup(s).