From: patchwork-bot+netdevbpf@kernel.org
To: Tommaso Merciai <tommaso.merciai@amarulasolutions.com>
Cc: michael@amarulasolutions.com,
alberto.bianchi@amarulasolutions.com,
linux-amarula@amarulasolutions.com, linuxfancy@googlegroups.com,
andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] net: phy: DP83822: enable rgmii mode if phy_interface_is_rgmii
Date: Sun, 22 May 2022 20:50:12 +0000 [thread overview]
Message-ID: <165325261265.21066.3922504901469719799.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220520235846.1919954-1-tommaso.merciai@amarulasolutions.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sat, 21 May 2022 01:58:46 +0200 you wrote:
> RGMII mode can be enable from dp83822 straps, and also writing bit 9
> of register 0x17 - RMII and Status Register (RCSR).
> When phy_interface_is_rgmii rgmii mode must be enabled, same for
> contrary, this prevents malconfigurations of hw straps
>
> References:
> - https://www.ti.com/lit/gpn/dp83822i p66
>
> [...]
Here is the summary with links:
- [v3] net: phy: DP83822: enable rgmii mode if phy_interface_is_rgmii
https://git.kernel.org/netdev/net-next/c/621427fbdada
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-22 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 23:58 [PATCH v3] net: phy: DP83822: enable rgmii mode if phy_interface_is_rgmii Tommaso Merciai
2022-05-21 18:39 ` Andrew Lunn
2022-05-23 6:57 ` Tommaso Merciai
2022-05-23 12:16 ` Andrew Lunn
2022-05-23 16:41 ` Tommaso Merciai
2022-05-22 20:50 ` patchwork-bot+netdevbpf [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=165325261265.21066.3922504901469719799.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alberto.bianchi@amarulasolutions.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxfancy@googlegroups.com \
--cc=michael@amarulasolutions.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tommaso.merciai@amarulasolutions.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