All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Marco Felsch <m.felsch@pengutronix.de>,
	Maxime Ripard <mripard@kernel.org>,
	linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Extend phy_configure_opts_mipi_dphy to support position and polarity
Date: Tue, 19 May 2026 15:57:15 +0530	[thread overview]
Message-ID: <agw7A9qkiAs0OUiq@vaman> (raw)
In-Reply-To: <20260325-dphy-params-extension-v1-0-c6df5599284a@linaro.org>

On 25-03-26, 21:47, Bryan O'Donoghue wrote:
> struct phy_configure_opts_mipi_dphy currently passes @lanes as a linear
> count of data-lanes starting from lane zero to a consuming DPHY driver.
> 
> This proves insufficient when we want to specify lane location and lane
> polarity.
> 
> To address this gap extend the structure to pass four new fields.

Sure, but where is the user...?
Please repost with users added in

Thanks

pw-bot: cr

-- 
~Vinod

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Marco Felsch <m.felsch@pengutronix.de>,
	Maxime Ripard <mripard@kernel.org>,
	linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Extend phy_configure_opts_mipi_dphy to support position and polarity
Date: Tue, 19 May 2026 15:57:15 +0530	[thread overview]
Message-ID: <agw7A9qkiAs0OUiq@vaman> (raw)
In-Reply-To: <20260325-dphy-params-extension-v1-0-c6df5599284a@linaro.org>

On 25-03-26, 21:47, Bryan O'Donoghue wrote:
> struct phy_configure_opts_mipi_dphy currently passes @lanes as a linear
> count of data-lanes starting from lane zero to a consuming DPHY driver.
> 
> This proves insufficient when we want to specify lane location and lane
> polarity.
> 
> To address this gap extend the structure to pass four new fields.

Sure, but where is the user...?
Please repost with users added in

Thanks

pw-bot: cr

-- 
~Vinod

  parent reply	other threads:[~2026-05-19 10:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 21:47 [PATCH 0/4] Extend phy_configure_opts_mipi_dphy to support position and polarity Bryan O'Donoghue
2026-03-25 21:47 ` Bryan O'Donoghue
2026-03-25 21:47 ` [PATCH 1/4] phy: dphy: Add lane_positions to DPHY config struct Bryan O'Donoghue
2026-03-25 21:47   ` Bryan O'Donoghue
2026-03-25 21:47 ` [PATCH 2/4] phy: dphy: Add lane_polarities " Bryan O'Donoghue
2026-03-25 21:47   ` Bryan O'Donoghue
2026-03-25 21:47 ` [PATCH 3/4] phy: dphy: Add clock_lane_position " Bryan O'Donoghue
2026-03-25 21:47   ` Bryan O'Donoghue
2026-03-25 21:48 ` [PATCH 4/4] phy: dphy: Add clock_lane_polarity " Bryan O'Donoghue
2026-03-25 21:48   ` Bryan O'Donoghue
2026-05-19 10:27 ` Vinod Koul [this message]
2026-05-19 10:27   ` [PATCH 0/4] Extend phy_configure_opts_mipi_dphy to support position and polarity 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=agw7A9qkiAs0OUiq@vaman \
    --to=vkoul@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=m.felsch@pengutronix.de \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.