Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vikram Sharma <quic_vikramsa@quicinc.com>
Cc: rfoss@kernel.org, todor.too@gmail.com,
	bryan.odonoghue@linaro.org, mchehab@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, andersson@kernel.org,
	konradybcio@kernel.org, hverkuil-cisco@xs4all.nl,
	cros-qcom-dts-watchers@chromium.org, catalin.marinas@arm.com,
	will@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] media: dt-bindings: Add qcom,qcs8300-camss
Date: Tue, 18 Mar 2025 08:16:11 +0100	[thread overview]
Message-ID: <f2899540-f9ac-4013-a703-25800429f97d@kernel.org> (raw)
In-Reply-To: <66c35bce-c657-4c12-ad02-58c995ae385a@quicinc.com>

On 18/03/2025 06:52, Vikram Sharma wrote:
> 
> On 2/23/2025 5:03 PM, Krzysztof Kozlowski wrote:
>> On Fri, Feb 14, 2025 at 03:17:46PM +0530, Vikram Sharma wrote:
>>> +properties:
>>> +  compatible:
>>> +    const: qcom,qcs8300-camss
>>> +
>>> +  reg:
>>> +    maxItems: 21
>>> +
>>> +  reg-names:
>>> +    items:
>>> +      - const: csid_wrapper
>> Why different order of entries than sm8550?
> 
> Hi Krzysztof,
> 
> Thanks for your review.
> I did this change to address a comment from Bryan on another series.
> https://lore.kernel.org/linux-arm-msm/e152ff78-caa5-493a-88da-96a6670eb2a2@linaro.org/
> 
> Please suggest if I should keep the order same as sm8550?
If you chosen the same order as x1e80100 then it is fine, but that file
is not merged so it is your responsibility to track any differences and
be sure whatever you send is always in sync with x1e.

Best regards,
Krzysztof


  parent reply	other threads:[~2025-03-18  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14  9:47 [PATCH v1 0/2] arm64: dts: qcom: qcs8300: Add qcs8300 camss support Vikram Sharma
2025-02-14  9:47 ` [PATCH v1 1/2] media: dt-bindings: Add qcom,qcs8300-camss Vikram Sharma
2025-02-23 11:33   ` Krzysztof Kozlowski
     [not found]     ` <66c35bce-c657-4c12-ad02-58c995ae385a@quicinc.com>
2025-03-18  7:16       ` Krzysztof Kozlowski [this message]
2025-03-18 21:48         ` Bryan O'Donoghue
2025-03-19  6:24           ` Vikram Sharma
2025-02-14  9:47 ` [PATCH v1 2/2] arm64: dts: qcom: qcs8300: Add support for camss Vikram Sharma
2025-02-23 11:34   ` Krzysztof Kozlowski

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=f2899540-f9ac-4013-a703-25800429f97d@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=cros-qcom-dts-watchers@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=quic_vikramsa@quicinc.com \
    --cc=rfoss@kernel.org \
    --cc=robh@kernel.org \
    --cc=todor.too@gmail.com \
    --cc=will@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