devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <pure.logic@nexus-software.ie>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	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 4/4] arm64: dts: qcom: sm8250: camss: Add CCI definitions
Date: Wed, 13 Apr 2022 02:08:45 +0100	[thread overview]
Message-ID: <0617782b-e24b-cd67-ffca-5cf95417ca21@nexus-software.ie> (raw)
In-Reply-To: <YlTeng8OcnvUnILZ@builder.lan>

On 12/04/2022 03:06, Bjorn Andersson wrote:
>> +			pinctrl-names = "default", "sleep";
>> +			pinctrl-0 = <&cci0_default &cci1_default>;
>> +			pinctrl-1 = <&cci0_sleep &cci1_sleep>;
> I would prefer that you include these in the same patch.
> 

You mean the CCI definition and the pinmux for it

OK, yes

      parent reply	other threads:[~2022-04-13  1:08 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
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 [this message]

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=0617782b-e24b-cd67-ffca-5cf95417ca21@nexus-software.ie \
    --to=pure.logic@nexus-software.ie \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.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).