LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: linux-phy@lists.infradead.org, Mikhail Rudenko <mike.rudenko@gmail.com>
Cc: linux-media@vger.kernel.org,
Mikhail Rudenko <mike.rudenko@gmail.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/5] phy: phy-rockchip-dphy-rx0: refactor for tx1rx1 addition
Date: Mon, 30 Aug 2021 22:45:03 +0200 [thread overview]
Message-ID: <6474995.6kXVAnRFRJ@diego> (raw)
In-Reply-To: <20210830180758.251390-2-mike.rudenko@gmail.com>
Hi Mikhail,
Am Montag, 30. August 2021, 20:07:50 CEST schrieb Mikhail Rudenko:
> In order to accommodate for rk3399 tx1rx1 addition, make
> enable/disable function calls indirect via function pointers in
> rk_dphy_drv_data. Also rename rk_dphy_write and rk_dphy_enable to
> avoid naming clashes.
You're a bit too late to the party :-( .
The tx1rx1 dphy is living _inside_ the 2nd DSI controller and is
configured through it.
So having the same peripheral in the dts with different compatibles
does break the devicetree-describes-hardware-not-Linux-implementation-details
paradigm.
Therefore my approach was to handle the switch between tx and rx modes
inside the dsi driver. This got merged for 5.15 as well, see [0] [1].
So sadly this series is somewhat obsolete, but you should find the
building blocks for camera support in linux-next already.
Regards
Heiko
[0] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=71f68fe7f12182ed968cfbbd1ef018721e4dee30
[1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=68e0277204c733dff19073686e2ac48239b06fbc
>
> Signed-off-by: Mikhail Rudenko <mike.rudenko@gmail.com>
> ---
> drivers/phy/rockchip/phy-rockchip-dphy-rx0.c | 38 +++++++++++++-------
> 1 file changed, 25 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/phy/rockchip/phy-rockchip-dphy-rx0.c b/drivers/phy/rockchip/phy-rockchip-dphy-rx0.c
> index 4df9476ef2a9..72145cdfb036 100644
> --- a/drivers/phy/rockchip/phy-rockchip-dphy-rx0.c
> +++ b/drivers/phy/rockchip/phy-rockchip-dphy-rx0.c
> @@ -138,12 +138,17 @@ static const struct dphy_reg rk3399_grf_dphy_regs[] = {
> [GRF_DPHY_RX0_TESTDOUT] = PHY_REG(RK3399_GRF_SOC_STATUS1, 8, 0),
> };
>
> +struct rk_dphy;
> +
> struct rk_dphy_drv_data {
> const char * const *clks;
> unsigned int num_clks;
> const struct hsfreq_range *hsfreq_ranges;
> unsigned int num_hsfreq_ranges;
> const struct dphy_reg *regs;
> +
> + void (*enable)(struct rk_dphy *priv);
> + void (*disable)(struct rk_dphy *priv);
> };
>
> struct rk_dphy {
> @@ -170,7 +175,7 @@ static inline void rk_dphy_write_grf(struct rk_dphy *priv,
> regmap_write(priv->grf, reg->offset, val);
> }
>
> -static void rk_dphy_write(struct rk_dphy *priv, u8 test_code, u8 test_data)
> +static void rk_dphy_write_mipi_rx(struct rk_dphy *priv, u8 test_code, u8 test_data)
> {
> rk_dphy_write_grf(priv, GRF_DPHY_RX0_TESTDIN, test_code);
> rk_dphy_write_grf(priv, GRF_DPHY_RX0_TESTEN, 1);
> @@ -186,7 +191,7 @@ static void rk_dphy_write(struct rk_dphy *priv, u8 test_code, u8 test_data)
> rk_dphy_write_grf(priv, GRF_DPHY_RX0_TESTCLK, 1);
> }
>
> -static void rk_dphy_enable(struct rk_dphy *priv)
> +static void rk_dphy_enable_rx(struct rk_dphy *priv)
> {
> rk_dphy_write_grf(priv, GRF_DPHY_RX0_FORCERXMODE, 0);
> rk_dphy_write_grf(priv, GRF_DPHY_RX0_FORCETXSTOPMODE, 0);
> @@ -206,22 +211,27 @@ static void rk_dphy_enable(struct rk_dphy *priv)
> usleep_range(100, 150);
>
> /* set clock lane */
> - /* HS hsfreq_range & lane 0 settle bypass */
> - rk_dphy_write(priv, CLOCK_LANE_HS_RX_CONTROL, 0);
> + /* HS hsfreq_range & lane 0 settle bypass */
> + rk_dphy_write_mipi_rx(priv, CLOCK_LANE_HS_RX_CONTROL, 0);
> /* HS RX Control of lane0 */
> - rk_dphy_write(priv, LANE0_HS_RX_CONTROL, priv->hsfreq << 1);
> + rk_dphy_write_mipi_rx(priv, LANE0_HS_RX_CONTROL, priv->hsfreq << 1);
> /* HS RX Control of lane1 */
> - rk_dphy_write(priv, LANE1_HS_RX_CONTROL, priv->hsfreq << 1);
> + rk_dphy_write_mipi_rx(priv, LANE1_HS_RX_CONTROL, priv->hsfreq << 1);
> /* HS RX Control of lane2 */
> - rk_dphy_write(priv, LANE2_HS_RX_CONTROL, priv->hsfreq << 1);
> + rk_dphy_write_mipi_rx(priv, LANE2_HS_RX_CONTROL, priv->hsfreq << 1);
> /* HS RX Control of lane3 */
> - rk_dphy_write(priv, LANE3_HS_RX_CONTROL, priv->hsfreq << 1);
> + rk_dphy_write_mipi_rx(priv, LANE3_HS_RX_CONTROL, priv->hsfreq << 1);
> /* HS RX Data Lanes Settle State Time Control */
> - rk_dphy_write(priv, LANES_THS_SETTLE_CONTROL,
> - THS_SETTLE_COUNTER_THRESHOLD);
> + rk_dphy_write_mipi_rx(priv, LANES_THS_SETTLE_CONTROL,
> + THS_SETTLE_COUNTER_THRESHOLD);
>
> /* Normal operation */
> - rk_dphy_write(priv, 0x0, 0);
> + rk_dphy_write_mipi_rx(priv, 0x0, 0);
> +}
> +
> +static void rk_dphy_disable_rx(struct rk_dphy *priv)
> +{
> + rk_dphy_write_grf(priv, GRF_DPHY_RX0_ENABLE, 0);
> }
>
> static int rk_dphy_configure(struct phy *phy, union phy_configure_opts *opts)
> @@ -266,7 +276,7 @@ static int rk_dphy_power_on(struct phy *phy)
> if (ret)
> return ret;
>
> - rk_dphy_enable(priv);
> + priv->drv_data->enable(priv);
>
> return 0;
> }
> @@ -275,7 +285,7 @@ static int rk_dphy_power_off(struct phy *phy)
> {
> struct rk_dphy *priv = phy_get_drvdata(phy);
>
> - rk_dphy_write_grf(priv, GRF_DPHY_RX0_ENABLE, 0);
> + priv->drv_data->disable(priv);
> clk_bulk_disable(priv->drv_data->num_clks, priv->clks);
> return 0;
> }
> @@ -310,6 +320,8 @@ static const struct rk_dphy_drv_data rk3399_mipidphy_drv_data = {
> .hsfreq_ranges = rk3399_mipidphy_hsfreq_ranges,
> .num_hsfreq_ranges = ARRAY_SIZE(rk3399_mipidphy_hsfreq_ranges),
> .regs = rk3399_grf_dphy_regs,
> + .enable = rk_dphy_enable_rx,
> + .disable = rk_dphy_disable_rx,
> };
>
> static const struct of_device_id rk_dphy_dt_ids[] = {
>
next prev parent reply other threads:[~2021-08-30 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 18:07 [PATCH v1 0/5] phy: phy-rockchip-dphy-rx0: add support for tx1rx1 rx mode Mikhail Rudenko
2021-08-30 18:07 ` [PATCH v1 1/5] phy: phy-rockchip-dphy-rx0: refactor for tx1rx1 addition Mikhail Rudenko
2021-08-30 20:45 ` Heiko Stübner [this message]
2021-08-31 0:41 ` Ezequiel Garcia
2021-08-30 18:07 ` [PATCH v1 2/5] phy: phy-rockchip-dphy-rx0: add support for tx1rx1 in receive mode Mikhail Rudenko
2021-08-30 18:07 ` [PATCH v1 3/5] phy: rename phy-rockchip-dphy-rx0 to phy-rockchip-dphy-rx Mikhail Rudenko
2021-08-30 18:07 ` [PATCH v1 4/5] dt-bindings: phy: phy-rockchip-dphy-rx0: add support for tx1rx1 phy Mikhail Rudenko
2021-08-30 21:00 ` Johan Jonker
2021-08-30 22:06 ` Johan Jonker
2021-08-31 0:03 ` Rob Herring
2021-08-30 18:07 ` [PATCH v1 5/5] arm64: dts: rockchip: add mipi-dphy-tx1rx1 for rk3399 Mikhail Rudenko
2021-08-30 21:12 ` Johan Jonker
2021-08-30 21:50 ` Johan Jonker
2021-08-31 12:58 ` [PATCH v1 0/5] phy: phy-rockchip-dphy-rx0: add support for tx1rx1 rx mode Mikhail Rudenko
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=6474995.6kXVAnRFRJ@diego \
--to=heiko@sntech.de \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mike.rudenko@gmail.com \
--cc=vkoul@kernel.org \
--subject='Re: [PATCH v1 1/5] phy: phy-rockchip-dphy-rx0: refactor for tx1rx1 addition' \
/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
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).