public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: arm: cpus: Add compatible qcom,oryon-1-5
Date: Mon, 13 Apr 2026 22:34:35 +0800	[thread overview]
Message-ID: <adz--4_2qAs7lkTu@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <cc08a091-9f2d-48de-9284-2f0c68fd343a@kernel.org>

On Mon, Apr 13, 2026 at 03:30:28PM +0200, Krzysztof Kozlowski wrote:
> On 13/04/2026 15:10, Shawn Guo wrote:
> > On Mon, Apr 13, 2026 at 02:40:18PM +0200, Krzysztof Kozlowski wrote:
> >>>> Please organize your patchset correctly.
> >>>
> >>> Are you asking for a big series that consists of all the new bindings
> >>> used by Nord DTS and DTS itself?  Unless this big series gets applied as
> >>> one-go, there are still chances that bindings get into a kernel release
> >>> without any users, e.g. subsystem maintainers pick up bindgins being
> >>> reviewed, but DTS requires more iterations and thus misses the release.
> >>
> >> Please follow existing rules, communicated multiple times on the mailing
> >> list. Qualcomm also has internal guideline clarifying this.
> >>
> >> Below are some upstream discussion clarifying this:
> >> https://lore.kernel.org/linux-samsung-soc/CADrjBPq_0nUYRABKpskRF_dhHu+4K=duPVZX==0pr+cjSL_caQ@mail.gmail.com/T/#m2d9130a1342ab201ab49670fa6c858ee3724c83c
> >> https://lore.kernel.org/all/49258645-d4d8-44a5-a4fc-b403c926a5d1@kernel.org/
> >>
> >> And how to do it:
> >> https://lore.kernel.org/all/20231121-topic-sm8650-upstream-dt-v3-0-db9d0507ffd3@linaro.org/
> > 
> > That's what I'm trying to do, posting bindings in prior to DTS, so that
> 
> Hm? Nothing above claimed that. I am sorry, but which rule either
> communicated publicly or privately encouraged or even allowed that?
> 
> > when posting DTS, either bindings is already merged or we can refer to
> > lore link of bindings.
> > 
> > I still need to understand you comment "Bindings come with the user".
> > Are you saying that bindings and DTS in different series should be posted
> > at the same time to show bindings has an user?
> 
> I am saying that you cannot post bindings alone where there is no user.
> Why do want even such binding? I see no point in having it in the
> kernel, unless you speak about very specific exception, but then please
> clarify that exception and why it applies to this work.

I think I'm getting what the requirement is now, but still not sure what
the point of the requirement is.

- Posting bindings and DTS at the same time doesn't guarantee they get
  into the same release.  It can often happen that bindings are merged
  alone into a release.  So it doesn't really help to avoid situation of
  there is bindings in-tree with no users.

- From what I can see, there are always DTS patches coming after bindings
  changes, sooner or later.  No one would be bothered to submit a bindings
  if the DTS using the bindings is only kept out of tree.

In short, there will be Nord DTS using the binding coming, and I do not
think posting them at the same time should be a requirement.

Shawn

  reply	other threads:[~2026-04-13 14:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13  9:16 [PATCH 0/2] dt-bindings: arm: cpus: Fix and extend Qualcomm Oryon compatibles Shawn Guo
2026-04-13  9:16 ` [PATCH 1/2] dt-bindings: arm: cpus: Restore qcom,oryon-1-4 compatible Shawn Guo
2026-04-13  9:57   ` Konrad Dybcio
2026-04-13 10:01   ` Krzysztof Kozlowski
2026-04-13 12:06     ` Shawn Guo
2026-04-13  9:16 ` [PATCH 2/2] dt-bindings: arm: cpus: Add compatible qcom,oryon-1-5 Shawn Guo
2026-04-13  9:58   ` Konrad Dybcio
2026-04-13 10:02   ` Krzysztof Kozlowski
2026-04-13 12:36     ` Shawn Guo
2026-04-13 12:40       ` Krzysztof Kozlowski
2026-04-13 13:10         ` Shawn Guo
2026-04-13 13:30           ` Krzysztof Kozlowski
2026-04-13 14:34             ` Shawn Guo [this message]
2026-04-13 16:08               ` Krzysztof Kozlowski
2026-04-14  1:21                 ` Shawn Guo
2026-04-14  6:23                   ` Krzysztof Kozlowski
2026-04-14  6:59                     ` Shawn Guo
2026-04-14  7:05                       ` Krzysztof Kozlowski
2026-04-14  7:11                       ` Krzysztof Kozlowski
2026-04-14  8:01                         ` 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=adz--4_2qAs7lkTu@QCOM-aGQu4IUr3Y \
    --to=shengchao.guo@oss.qualcomm.com \
    --cc=andersson@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=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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