public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@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>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: mfd: qcom,tcsr: Add compatible for Nord
Date: Tue, 28 Apr 2026 20:52:06 +0800	[thread overview]
Message-ID: <afCtdoJrcvTMmyKo@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <20260428-qualified-pronghorn-of-success-ceb0ec@quoll>

On Tue, Apr 28, 2026 at 08:18:37AM +0200, Krzysztof Kozlowski wrote:
> On Mon, Apr 27, 2026 at 09:21:16AM +0800, Shawn Guo wrote:
> > From: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
> > 
> > Document Top Control and Status Register controller on Qualcomm Nord SoC
> > which is compatible with 'syscon'.
> 
> TCSR is not compatible with syscon, because there is no such device as
> syscon. That's Linuxism. One device cannot be compatible with non-device
> Linuxism.
> 
> Few other commits also are not helping - you keep repeating the binding,
> that device is compatible with some other "compatible". But we
> never asked for it.

Ok, I will just drop it.

Shawn

      reply	other threads:[~2026-04-28 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27  1:21 [PATCH v2] dt-bindings: mfd: qcom,tcsr: Add compatible for Nord Shawn Guo
2026-04-28  6:18 ` Krzysztof Kozlowski
2026-04-28 12:52   ` Shawn Guo [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=afCtdoJrcvTMmyKo@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=lee@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@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