From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Kevin Hilman <khilman@baylibre.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH net-next v2 3/3] net: phy: meson-gxl: add g12a support
Date: Fri, 29 Mar 2019 20:22:56 +0100 [thread overview]
Message-ID: <0b7df4e8-8db2-a028-bd1d-6d77cac67110@gmail.com> (raw)
In-Reply-To: <20190329141512.29867-4-jbrunet@baylibre.com>
On 29.03.2019 15:15, Jerome Brunet wrote:
> The g12a SoC family uses the type of internal PHY that was used on the
> gxl family. The quirks of gxl family, like the LPA register corruption,
> appear to have been resolved on this new SoC generation.
>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
> drivers/net/phy/meson-gxl.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/net/phy/meson-gxl.c b/drivers/net/phy/meson-gxl.c
> index 0eec2913c289..49cad0f4c79b 100644
> --- a/drivers/net/phy/meson-gxl.c
> +++ b/drivers/net/phy/meson-gxl.c
> @@ -237,11 +237,25 @@ static struct phy_driver meson_gxl_phy[] = {
> .config_intr = meson_gxl_config_intr,
> .suspend = genphy_suspend,
> .resume = genphy_resume,
> + }, {
> + .phy_id = 0x01803301,
> + .phy_id_mask = 0xffffffff,
Here you could use the PHY_ID_MATCH_EXACT() macro, see realtek PHY
driver for an example.
> + .name = "Meson G12A Internal PHY",
> + .features = PHY_BASIC_FEATURES,
> + .flags = PHY_IS_INTERNAL,
> + .soft_reset = genphy_soft_reset,
> + .aneg_done = genphy_aneg_done,
> + .read_status = genphy_read_status,
genphy_aneg_done() and genphy_read_status() are used automatically
as fallback if no callback is defined. You can omit these two lines.
> + .ack_interrupt = meson_gxl_ack_interrupt,
> + .config_intr = meson_gxl_config_intr,
> + .suspend = genphy_suspend,
> + .resume = genphy_resume,
> },
> };
>
> static struct mdio_device_id __maybe_unused meson_gxl_tbl[] = {
> { 0x01814400, 0xfffffff0 },
> + { 0x01803301, 0xffffffff },
Also a candidate for PHY_ID_MATCH_EXACT. In the line before
PHY_ID_MATCH_MODEL could be used.
> { }
> };
>
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-03-29 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 14:15 [PATCH net-next v2 0/3] net: phy: add Amlogic g12a support Jerome Brunet
2019-03-29 14:15 ` [PATCH net-next v2 1/3] dt-bindings: net: phy: add g12a mdio mux documentation Jerome Brunet
2019-03-29 14:15 ` [PATCH net-next v2 2/3] net: phy: add amlogic g12a mdio mux support Jerome Brunet
2019-03-29 22:49 ` Stephen Boyd
2019-03-29 14:15 ` [PATCH net-next v2 3/3] net: phy: meson-gxl: add g12a support Jerome Brunet
2019-03-29 19:22 ` Heiner Kallweit [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=0b7df4e8-8db2-a028-bd1d-6d77cac67110@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).