public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Shawn Guo <shengchao.guo@oss.qualcomm.com>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mailbox: qcom-ipcc: Document Nord IPCC
Date: Mon, 20 Apr 2026 10:24:24 +0200	[thread overview]
Message-ID: <778475e2-0baf-4623-b927-83bddb0c92bf@kernel.org> (raw)
In-Reply-To: <1b40b1a0-983c-4eca-bdc8-6a64cf76197d@oss.qualcomm.com>

On 20/04/2026 10:18, Konrad Dybcio wrote:
> On 4/20/26 10:16 AM, Manivannan Sadhasivam wrote:
>> On Mon, Apr 20, 2026 at 12:01:41PM +0800, Shawn Guo wrote:
>>> From: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
>>>
>>> Document Inter-Processor Communication Controller on Qualcomm Nord SoC
>>> with a fallback on qcom,ipcc.
>>>
>>> Signed-off-by: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
>>> Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
>>> ---
>>>  Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml b/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml
>>> index f5c584cf2146..0a86230a2b18 100644
>>> --- a/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml
>>> +++ b/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml
>>> @@ -28,6 +28,7 @@ properties:
>>>            - qcom,glymur-ipcc
>>>            - qcom,kaanapali-ipcc
>>>            - qcom,milos-ipcc
>>> +          - qcom,nord-ipcc
>>
>> What is the difference between this and the existing 'sa8775p' compatible? Are
>> they both representing the same SoC series?
> 
> Nord is a gen newer

This should be explained somewhere, e.g. in board/soc bindings or SoC ID
bindings. None of these are posted, so most of the patches being posted
could receive that comment - what is the difference and why commit msg
explains nothing.

Best regards,
Krzysztof

  parent reply	other threads:[~2026-04-20  8:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20  4:01 [PATCH] dt-bindings: mailbox: qcom-ipcc: Document Nord IPCC Shawn Guo
2026-04-20  8:16 ` Manivannan Sadhasivam
2026-04-20  8:18   ` Konrad Dybcio
2026-04-20  8:23     ` Manivannan Sadhasivam
2026-04-20  8:24     ` Krzysztof Kozlowski [this message]
2026-04-21  7:43       ` Shawn Guo

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=778475e2-0baf-4623-b927-83bddb0c92bf@kernel.org \
    --to=krzk@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=deepti.jaggi@oss.qualcomm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=mani@kernel.org \
    --cc=robh@kernel.org \
    --cc=shengchao.guo@oss.qualcomm.com \
    /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