devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: agross@kernel.org, robh+dt@kernel.org, krzk+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	dmitry.baryshkov@linaro.org, jonathan@marek.ca, hfink@snap.com,
	jgrahsl@snap.com
Subject: Re: [PATCH 3/4] arm64: dts: qcom: sm8250: camss: Add downstream camera pin definitions
Date: Mon, 11 Apr 2022 21:04:05 -0500	[thread overview]
Message-ID: <YlTeFYp6IoPJfHEb@builder.lan> (raw)
In-Reply-To: <20220409164556.2832782-4-bryan.odonoghue@linaro.org>

On Sat 09 Apr 11:45 CDT 2022, Bryan O'Donoghue wrote:

> There are a number of pin mux descriptions for the CAMSS block which are
> defined downstream.
> 
> Bring in the definitions now. Subsequent changes will optionally activate
> those muxes for different sm8250 based boards.
> 

I'm not able to spot where these are referenced, are they not used or am
I just failing the search today?

I would prefer that we don't sprinkle pinctrl states that potentially
might be used at a later time...

> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> ---
>  arch/arm64/boot/dts/qcom/sm8250.dtsi | 471 +++++++++++++++++++++++++++
>  1 file changed, 471 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> index 3d6c617de045..91ed079edbf7 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> @@ -3687,6 +3687,477 @@ tlmm: pinctrl@f100000 {
>  			gpio-ranges = <&tlmm 0 0 181>;
>  			wakeup-parent = <&pdc>;
>  
> +			cam_sensor_mclk0_active: cam_sensor_mclk0_active {

Please don't use '_' in the node name.

> +				/* MCLK0 */

I would prefer that we don't inherit the mux/config split upstream.

You can either do:

cam-sensor-mclk0-active-state {
	pins = ;
	function = ;
	bias...
};

or:

cam-sensor-mclk0-active-state {
	mclk0 {
		pins = ;
		function = ;
		bias...
	};
};

And depending on how this state is actually used you could lump together
the configuration of several pins - with different properties - in the
same state node.

Regards,
Bjorn

  reply	other threads:[~2022-04-12  2:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09 16:45 [PATCH 0/4] Add camss to SM8250 dtsi Bryan O'Donoghue
2022-04-09 16:45 ` [PATCH 1/4] arm64: dts: qcom: sm8250: Add camcc DT node Bryan O'Donoghue
2022-04-09 16:45 ` [PATCH 2/4] arm64: dts: qcom: sm8250: camss: Add CAMSS block definition Bryan O'Donoghue
2022-04-12  2:07   ` Bjorn Andersson
2022-04-09 16:45 ` [PATCH 3/4] arm64: dts: qcom: sm8250: camss: Add downstream camera pin definitions Bryan O'Donoghue
2022-04-12  2:04   ` Bjorn Andersson [this message]
2022-04-12 23:50     ` Bryan O'Donoghue
2022-04-09 16:45 ` [PATCH 4/4] arm64: dts: qcom: sm8250: camss: Add CCI definitions Bryan O'Donoghue
2022-04-12  2:06   ` Bjorn Andersson
2022-04-12 23:58     ` Bryan O'Donoghue
2022-04-13  1:08     ` Bryan O'Donoghue

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=YlTeFYp6IoPJfHEb@builder.lan \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=hfink@snap.com \
    --cc=jgrahsl@snap.com \
    --cc=jonathan@marek.ca \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).