From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Heiko Stuebner <heiko@sntech.de>, vkoul@kernel.org, kishon@kernel.org
Cc: linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
quentin.schulz@cherry.de,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH 1/2] phy: phy-rockchip-samsung-hdptx: annotate regmap register-callback
Date: Fri, 6 Dec 2024 13:18:56 +0200 [thread overview]
Message-ID: <e6172204-2f3f-4a9c-892c-be85d19ad031@collabora.com> (raw)
In-Reply-To: <20241206103401.1780416-2-heiko@sntech.de>
On 12/6/24 12:34 PM, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@cherry.de>
>
> The variant of the driver in the vendor-tree contained those handy
> comments in the regmap register callback. Having the different ranges
> describe what they are looks helpful.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@cherry.de>
> ---
> drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c b/drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c
> index 4ced1479e2dc..c5c64c209e96 100644
> --- a/drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c
> +++ b/drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c
> @@ -766,13 +766,13 @@ static struct tx_drv_ctrl tx_drv_ctrl_hbr2[4][4] = {
> static bool rk_hdptx_phy_is_rw_reg(struct device *dev, unsigned int reg)
> {
> switch (reg) {
> - case 0x0000 ... 0x029c:
> - case 0x0400 ... 0x04a4:
> - case 0x0800 ... 0x08a4:
> - case 0x0c00 ... 0x0cb4:
> - case 0x1000 ... 0x10b4:
> - case 0x1400 ... 0x14b4:
> - case 0x1800 ... 0x18b4:
> + case 0x0000 ... 0x029c: /* CMN Register */
> + case 0x0400 ... 0x04a4: /* Sideband Register */
> + case 0x0800 ... 0x08a4: /* Lane Top Register */
> + case 0x0c00 ... 0x0cb4: /* Lane 0 Register */
> + case 0x1000 ... 0x10b4: /* Lane 1 Register */
> + case 0x1400 ... 0x14b4: /* Lane 2 Register */
> + case 0x1800 ... 0x18b4: /* Lane 3 Register */
> return true;
> }
>
Nice finding! The HDMI variant of the driver which I used as an
implementation reference (i.e. phy-rockchip-samsung-hdptx-hdmi.c)
doesn't provide these comments.
Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-12-06 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 10:33 [PATCH 0/2] phy: phy-rockchip-samsung-hdptx: don't use of-alias Heiko Stuebner
2024-12-06 10:34 ` [PATCH 1/2] phy: phy-rockchip-samsung-hdptx: annotate regmap register-callback Heiko Stuebner
2024-12-06 11:18 ` Cristian Ciocaltea [this message]
2024-12-06 17:36 ` Heiko Stübner
2024-12-06 17:54 ` Cristian Ciocaltea
2024-12-06 10:34 ` [PATCH 2/2] phy: phy-rockchip-samsung-hdptx: Don't use dt aliases to determine phy-id Heiko Stuebner
2024-12-06 11:26 ` Cristian Ciocaltea
2024-12-06 13:53 ` Heiko Stübner
2024-12-06 16:59 ` [PATCH 0/2] phy: phy-rockchip-samsung-hdptx: don't use of-alias Sebastian Reichel
2025-02-09 21:18 ` Heiko Stübner
2025-02-10 17:21 ` Vinod Koul
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=e6172204-2f3f-4a9c-892c-be85d19ad031@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
--cc=vkoul@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