mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Riesch <michael.riesch@collabora.com>
To: Jason Yang <jason98166@gmail.com>, Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Guochun Huang <hero.huang@rock-chips.com>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: Sebastian Reichel <sebastian.reichel@collabora.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 5/8] phy: rockchip-samsung-dcphy: Add a second PHY for the receiver
Date: Wed, 28 Oct 2026 00:35:00 +0100	[thread overview]
Message-ID: <fd9aa80b-79d7-4acb-8398-3c22f74c7aea@collabora.com> (raw)
In-Reply-To: <20261016-dcphy-rx-v1-v5-5-e63b49eabe2d@gmail.com>

Hi Jason,

On 10/16/26 10:56, Jason Yang wrote:
> Give the receiver a struct phy of its own, with its own phy_ops and its
> own samsung_mipi_phy for the state the two do not share.
> 
> of_xlate() takes the direction from the second cell and falls back to
> the transmitter for a single-cell provider, so existing device trees
> keep working. It now rejects an unknown value in either cell, and a mix
> of D-PHY and C-PHY consumers, which the TRM does not support [1].
> 
> The receiver's callbacks return -EOPNOTSUPP until its bring-up is added
> in the next change.

Can you merge this patch with the subsequent one? IMHO it does not help
to first introduce some skeleton with -EOPNOTSUPP only to add support
for it in the very next patch...

Thanks and best regards,
Michael

> 
> [1] RK3588 TRM: section 22.1 (overview)
> 
> Assisted-by: LLM
> Signed-off-by: Jason Yang <jason98166@gmail.com>
> ---
>  drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c | 69 +++++++++++++++++++++--
>  1 file changed, 63 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c b/drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c
> index e4293c8d2b29..316d4c4d49c1 100644
> --- a/drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c
> +++ b/drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c
> @@ -296,6 +296,8 @@ struct samsung_mipi_dcphy {
>  	struct reset_control *apb_rst;
>  	struct reset_control *grf_apb_rst;
>  	struct samsung_mipi_phy tx;
> +	struct samsung_mipi_phy rx;
> +	/* PHY mode, PHY_TYPE_DPHY or PHY_TYPE_CPHY. */
>  	u8 type;
>  
>  	const struct samsung_mipi_dcphy_plat_data *pdata;
> @@ -1511,6 +1513,22 @@ static int samsung_mipi_dcphy_exit(struct phy *phy)
>  	return 0;
>  }
>  
> +static int samsung_mipi_dcphy_rx_configure(struct phy *phy,
> +					   union phy_configure_opts *opts)
> +{
> +	return -EOPNOTSUPP;
> +}
> +
> +static int samsung_mipi_dcphy_rx_power_on(struct phy *phy)
> +{
> +	return -EOPNOTSUPP;
> +}
> +
> +static int samsung_mipi_dcphy_rx_power_off(struct phy *phy)
> +{
> +	return -EOPNOTSUPP;
> +}
> +
>  static const struct phy_ops samsung_mipi_dcphy_tx_ops = {
>  	.configure = samsung_mipi_dcphy_tx_configure,
>  	.power_on  = samsung_mipi_dcphy_tx_power_on,
> @@ -1520,6 +1538,15 @@ static const struct phy_ops samsung_mipi_dcphy_tx_ops = {
>  	.owner	   = THIS_MODULE,
>  };
>  
> +static const struct phy_ops samsung_mipi_dcphy_rx_ops = {
> +	.configure = samsung_mipi_dcphy_rx_configure,
> +	.power_on  = samsung_mipi_dcphy_rx_power_on,
> +	.power_off = samsung_mipi_dcphy_rx_power_off,
> +	.init = samsung_mipi_dcphy_init,
> +	.exit = samsung_mipi_dcphy_exit,
> +	.owner	   = THIS_MODULE,
> +};
> +
>  static const struct regmap_config samsung_mipi_dcphy_regmap_config = {
>  	.name = "dcphy",
>  	.reg_bits = 32,
> @@ -1532,19 +1559,42 @@ static struct phy *samsung_mipi_dcphy_xlate(struct device *dev,
>  					    const struct of_phandle_args *args)
>  {
>  	struct samsung_mipi_dcphy *samsung = dev_get_drvdata(dev);
> +	/* Device trees without the second cell describe the transmitter. */
> +	u32 direction = PHY_DIRECTION_TX;
> +	u32 type;
>  
> -	if (args->args_count != 1) {
> +	if (args->args_count < 1 || args->args_count > 2) {
>  		dev_err(dev, "invalid number of arguments\n");
>  		return ERR_PTR(-EINVAL);
>  	}
>  
> -	if (samsung->type != PHY_NONE && samsung->type != args->args[0])
> -		dev_warn(dev, "phy type select %d overwriting type %d\n",
> -			 args->args[0], samsung->type);
> +	type = args->args[0];
> +	if (type != PHY_TYPE_DPHY && type != PHY_TYPE_CPHY) {
> +		dev_err(dev, "invalid phy type %u\n", type);
> +		return ERR_PTR(-EINVAL);
> +	}
>  
> -	samsung->type = args->args[0];
> +	if (args->args_count == 2)
> +		direction = args->args[1];
>  
> -	return samsung->tx.phy;
> +	if (direction != PHY_DIRECTION_TX && direction != PHY_DIRECTION_RX) {
> +		dev_err(dev, "invalid direction %u\n", direction);
> +		return ERR_PTR(-EINVAL);
> +	}
> +
> +	/*
> +	 * The TRM (section 22.1) does not support the transmitter and the
> +	 * receiver running in different modes, so the mode belongs to the
> +	 * block.
> +	 */
> +	if (samsung->type != PHY_NONE && samsung->type != type) {
> +		dev_err(dev, "phy type %u conflicts with type %u already selected\n",
> +			type, samsung->type);
> +		return ERR_PTR(-EINVAL);
> +	}
> +	samsung->type = type;
> +
> +	return direction == PHY_DIRECTION_RX ? samsung->rx.phy : samsung->tx.phy;
>  }
>  
>  static int samsung_mipi_dcphy_probe(struct platform_device *pdev)
> @@ -1620,6 +1670,13 @@ static int samsung_mipi_dcphy_probe(struct platform_device *pdev)
>  
>  	phy_set_drvdata(samsung->tx.phy, samsung);
>  
> +	samsung->rx.phy = devm_phy_create(dev, NULL, &samsung_mipi_dcphy_rx_ops);
> +	if (IS_ERR(samsung->rx.phy))
> +		return dev_err_probe(dev, PTR_ERR(samsung->rx.phy),
> +				     "Failed to create MIPI DC-PHY receiver\n");
> +
> +	phy_set_drvdata(samsung->rx.phy, samsung);
> +
>  	phy_provider = devm_of_phy_provider_register(dev, samsung_mipi_dcphy_xlate);
>  	if (IS_ERR(phy_provider))
>  		return dev_err_probe(dev, PTR_ERR(phy_provider),
> 


  parent reply	other threads:[~2026-10-27 23:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  8:56 [PATCH v5 0/8] phy: rockchip-samsung-dcphy: Add the MIPI D-PHY receiver Jason Yang
2026-10-16  8:56 ` [PATCH v5 1/8] dt-bindings: phy: Add PHY_DIRECTION_TX/RX definitions Jason Yang
2026-10-16 10:38   ` Bryan O'Donoghue
2026-10-17 17:19   ` Krzysztof Kozlowski
2026-10-16  8:56 ` [PATCH v5 2/8] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: Add a cell to select TX or RX Jason Yang
2026-10-16 10:43   ` Bryan O'Donoghue
2026-10-19  8:51     ` 楊智成
2026-10-16 14:01   ` Rob Herring
2026-10-17 17:22     ` Krzysztof Kozlowski
2026-10-19  8:15       ` 楊智成
2026-10-19 15:06         ` Rob Herring
2026-10-19 22:20           ` Michael Riesch
2026-10-20 13:37             ` Heiko Stübner
2026-10-20 14:10               ` Rob Herring
2026-10-20 14:57                 ` Heiko Stübner
2026-10-20 18:04                   ` Michael Riesch
2026-10-20 18:24                     ` Heiko Stübner
2026-10-21  2:42                   ` Rob Herring
2026-10-21  8:03                     ` Heiko Stübner
2026-10-27 23:32                       ` Michael Riesch
2026-10-28  8:56                         ` 楊智成
2026-10-16  8:56 ` [PATCH v5 3/8] phy: rockchip-samsung-dcphy: Move block-level setup to runtime resume Jason Yang
2026-10-16 10:46   ` Bryan O'Donoghue
2026-10-26  4:38     ` 楊智成
2026-10-27 23:30   ` Michael Riesch
2026-10-16  8:56 ` [PATCH v5 4/8] phy: rockchip-samsung-dcphy: Name the transmitter helpers and ops Jason Yang
2026-10-27 23:33   ` Michael Riesch
2026-10-16  8:56 ` [PATCH v5 5/8] phy: rockchip-samsung-dcphy: Add a second PHY for the receiver Jason Yang
2026-10-17 17:24   ` Krzysztof Kozlowski
2026-10-27 23:35   ` Michael Riesch [this message]
2026-10-16  8:56 ` [PATCH v5 6/8] phy: rockchip-samsung-dcphy: Add MIPI D-PHY receiver support Jason Yang
2026-10-16  8:56 ` [PATCH v5 7/8] arm64: dts: rockchip: use two phy cells for the rk3588 mipi dcphys Jason Yang
2026-10-17 17:37   ` Krzysztof Kozlowski
2026-10-16  8:56 ` [PATCH v5 8/8] arm64: dts: rockchip: add mipi csi-2 receiver nodes for the dcphys on rk3588 Jason Yang

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=fd9aa80b-79d7-4acb-8398-3c22f74c7aea@collabora.com \
    --to=michael.riesch@collabora.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=hero.huang@rock-chips.com \
    --cc=jason98166@gmail.com \
    --cc=krzk+dt@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=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --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

all inboxes | Powered by JetHome®