From: Florian Fainelli <f.fainelli@gmail.com>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: paul.geurts@prodrive-technologies.com, jonas.gorski@gmail.com,
andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] net: dsa: b53: mdio: add support for BCM53134
Date: Thu, 23 Mar 2023 09:57:30 -0700 [thread overview]
Message-ID: <37d626f7-d38d-69b4-d57c-73ddd47163a5@gmail.com> (raw)
In-Reply-To: <CAKR-sGdhVTH__KT2bu3NM56QoJgiM0JuKXGabW5uLRg8NMwGmA@mail.gmail.com>
On 3/23/23 09:49, Álvaro Fernández Rojas wrote:
> El jue, 23 mar 2023 a las 17:43, Florian Fainelli
> (<f.fainelli@gmail.com>) escribió:
>>
>> On 3/23/23 05:18, Álvaro Fernández Rojas wrote:
>>> From: Paul Geurts <paul.geurts@prodrive-technologies.com>
>>>
>>> Add support for the BCM53134 Ethernet switch in the existing b53 dsa driver.
>>> BCM53134 is very similar to the BCM58XX series.
>>>
>>> Signed-off-by: Paul Geurts <paul.geurts@prodrive-technologies.com>
>>> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
>>> ---
>>> drivers/net/dsa/b53/b53_common.c | 53 +++++++++++++++++++++++++++++++-
>>> drivers/net/dsa/b53/b53_mdio.c | 5 ++-
>>> drivers/net/dsa/b53/b53_priv.h | 9 +++++-
>>> 3 files changed, 64 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/net/dsa/b53/b53_common.c b/drivers/net/dsa/b53/b53_common.c
>>> index 1f9b251a5452..aaa0813e6f59 100644
>>> --- a/drivers/net/dsa/b53/b53_common.c
>>> +++ b/drivers/net/dsa/b53/b53_common.c
>>> @@ -1282,6 +1282,42 @@ static void b53_adjust_link(struct dsa_switch *ds, int port,
>>> if (is63xx(dev) && port >= B53_63XX_RGMII0)
>>> b53_adjust_63xx_rgmii(ds, port, phydev->interface);
>>>
>>> + if (is53134(dev) && phy_interface_is_rgmii(phydev)) {
>>
>> Why is not this in the same code block as the one for the is531x5()
>> device like this:
>
> This is what I asked on the cover letter:
>> I also added a separate RGMII handling block for is53134() since according to
>> Paul, BCM53134 doesn't support RGMII_CTRL_TIMING_SEL as opposed to is531x5().
>
> Should I add it to the same block and avoid adding
> RGMII_CTRL_TIMING_SEL if is53134() or is it compatible with
> RGMII_CTRL_TIMING_SEL?
RGMII_CTRL_TIMING_SEL is not defined for the 53125 or 53128, and for
53115, the register 0x60 is not even defined in the datasheet.
RGMII_CTRL_TIMING_SEL is defined for the 53134 however and would control
how the two other bits behave with respect to RGMII timing. My guess is
that if we removed it entirely we would not be breaking anything, and we
could just support all of the 531x5() and 53134 families within the same
block.
Jonas, do you remember why setting RGMII_CTRL_TIMING_SEL might have been
necessary?
--
Florian
next prev parent reply other threads:[~2023-03-23 16:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 12:18 [PATCH 0/2] " Álvaro Fernández Rojas
2023-03-23 12:18 ` [PATCH 1/2] dt-bindings: net: dsa: b53: add BCM53134 support Álvaro Fernández Rojas
2023-03-23 16:34 ` Florian Fainelli
2023-03-25 11:15 ` Krzysztof Kozlowski
2023-03-23 12:18 ` [PATCH 2/2] net: dsa: b53: mdio: add support for BCM53134 Álvaro Fernández Rojas
2023-03-23 16:43 ` Florian Fainelli
2023-03-23 16:49 ` Álvaro Fernández Rojas
2023-03-23 16:57 ` Florian Fainelli [this message]
2023-03-23 20:10 ` Paul Geurts
2023-03-23 21:02 ` Florian Fainelli
2023-03-23 22:13 ` Álvaro Fernández Rojas
2023-03-24 8:29 ` Paul Geurts
2023-03-24 8:43 ` Álvaro Fernández Rojas
2023-03-23 22:12 ` Álvaro Fernández Rojas
2023-03-23 19:58 ` [PATCH 0/2] " Paul Geurts
2023-03-23 22:10 ` Álvaro Fernández Rojas
2023-03-24 8:41 ` [PATCH v2 " Álvaro Fernández Rojas
2023-03-24 8:41 ` [PATCH v2 1/2] dt-bindings: net: dsa: b53: add BCM53134 support Álvaro Fernández Rojas
2023-03-25 11:15 ` Krzysztof Kozlowski
2023-03-24 8:41 ` [PATCH v2 2/2] net: dsa: b53: mdio: add support for BCM53134 Álvaro Fernández Rojas
2023-03-24 22:07 ` Florian Fainelli
2023-03-24 22:05 ` [PATCH v2 0/2] " Jakub Kicinski
2023-03-27 7:40 ` patchwork-bot+netdevbpf
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=37d626f7-d38d-69b4-d57c-73ddd47163a5@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jonas.gorski@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=paul.geurts@prodrive-technologies.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®