From: Andrew Lunn <andrew@lunn.ch>
To: Divya Koppera <Divya.Koppera@microchip.com>
Cc: 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,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next] net: phy: micrel: Adding SQI support for lan8814 phy
Date: Thu, 25 Aug 2022 23:53:45 +0200 [thread overview]
Message-ID: <YwfvaSFejdtPtZgK@lunn.ch> (raw)
In-Reply-To: <20220825080549.9444-1-Divya.Koppera@microchip.com>
> +#define LAN8814_DCQ_CTRL 0xe6
> +#define LAN8814_DCQ_CTRL_READ_CAPTURE_ BIT(15)
> +#define LAN8814_DCQ_CTRL_CHANNEL_MASK GENMASK(1, 0)
> +#define LAN8814_DCQ_SQI 0xe4
> +#define LAN8814_DCQ_SQI_MAX 7
> +#define LAN8814_DCQ_SQI_VAL_MASK GENMASK(3, 1)
> +
> static int lanphy_read_page_reg(struct phy_device *phydev, int page, u32 addr)
> {
> int data;
> @@ -2927,6 +2934,32 @@ static int lan8814_probe(struct phy_device *phydev)
> return 0;
> }
>
> +static int lan8814_get_sqi(struct phy_device *phydev)
> +{
> + int rc, val;
> +
> + val = lanphy_read_page_reg(phydev, 1, LAN8814_DCQ_CTRL);
> + if (val < 0)
> + return val;
I just took a quick look at the datasheet. It says:
All registers references in this section are in MMD Device Address 1
So you should be using phy_read_mmd(phydev, MDIO_MMD_PMAPMD, xxx) to
read/write these registers. The datasheet i have however is missing
the register map, so i've no idea if it is still 0xe6.
Andrew
next prev parent reply other threads:[~2022-08-25 21:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 8:05 [PATCH net-next] net: phy: micrel: Adding SQI support for lan8814 phy Divya Koppera
2022-08-25 13:19 ` Andrew Lunn
2022-08-26 3:46 ` Divya.Koppera
2022-08-25 21:53 ` Andrew Lunn [this message]
2022-08-26 3:50 ` Divya.Koppera
2022-08-26 19:42 ` Andrew Lunn
2022-08-29 5:23 ` Divya.Koppera
2022-08-26 8:42 ` Michael Walle
2022-08-26 9:11 ` Divya.Koppera
2022-08-26 9:26 ` Michael Walle
2022-08-26 9:54 ` Oleksij Rempel
2022-08-26 10:43 ` Oleksij Rempel
2022-08-26 19:51 ` Andrew Lunn
2022-08-29 5:50 ` Divya.Koppera
2022-08-29 12:30 ` Andrew Lunn
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=YwfvaSFejdtPtZgK@lunn.ch \
--to=andrew@lunn.ch \
--cc=Divya.Koppera@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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