From: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
To: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>
Cc: "Siratul Islam" <siratul.islam@linux.dev>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Luca Weiss" <luca.weiss@fairphone.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: magnetometer: add QST QMC6308
Date: Mon, 20 Jul 2026 01:58:23 +0100 [thread overview]
Message-ID: <20260720015823.0b1e62f3@jic23-huawei> (raw)
In-Reply-To: <20260716141800.82761-1-jorijnvdgraaf@catcrafts.net>
On Thu, 16 Jul 2026 16:18:00 +0200
Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net> wrote:
> Hi Sirat,
>
> On Wed, 2026-07-15 at 22:16 +0000, Siratul Islam wrote:
> > > I'd lean towards keeping the separate file.
> > Wait for more feedback before deciding, since you have a few days
> > before you send v2. DT maintainers usually prefer reusing the same
> > file where possible.
>
> Right, my previous email wasn't meant to lock in a decision,
> just my preference. If the DT maintainers want it merged in v2
> I'll happily do that.
DT maintainers may hold a different view but to me it sounds like
the overlap is small enough that the complexity of combining them
may well outweigh the advantages.
Thanks,
Jonathan
>
> > Register compatibility is driver specific. Bindings are only for
> > describing hardware. So if there are reasons to use separate
> > bindings, this isn't one of them. A fallback-compatible
> > relationship isn't needed, as we are already using an enum to list
> > which different sensors the binding supports.
>
> Fair point on both counts; I'll drop that sentence. The lack of
> property overlap is the part that matters here.
>
> Thanks,
> Jorijn
next prev parent reply other threads:[~2026-07-20 0:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 20:28 [PATCH 0/2] iio: magnetometer: add support for QST QMC6308 Jorijn van der Graaf
2026-07-14 20:28 ` [PATCH 1/2] dt-bindings: iio: magnetometer: add " Jorijn van der Graaf
2026-07-15 18:32 ` Siratul Islam
2026-07-15 20:46 ` Jorijn van der Graaf
2026-07-15 22:16 ` Siratul Islam
2026-07-16 14:18 ` Jorijn van der Graaf
2026-07-20 0:58 ` Jonathan Cameron [this message]
2026-07-20 1:09 ` Jonathan Cameron
2026-07-14 20:28 ` [PATCH 2/2] iio: magnetometer: add support for " Jorijn van der Graaf
2026-07-14 20:38 ` sashiko-bot
2026-07-14 21:21 ` Uwe Kleine-König
2026-07-15 20:46 ` Jorijn van der Graaf
2026-07-20 1:00 ` Jonathan Cameron
2026-07-16 9:52 ` Siratul Islam
2026-07-16 10:11 ` Siratul Islam
2026-07-16 14:18 ` Jorijn van der Graaf
2026-07-16 14:45 ` Siratul Islam
2026-07-16 19:06 ` Siratul Islam
2026-07-20 1:06 ` Jonathan Cameron
2026-07-20 6:01 ` Siratul Islam
2026-07-20 1:38 ` Jonathan Cameron
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=20260720015823.0b1e62f3@jic23-huawei \
--to=jonathan.cameron@oss.qualcomm.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jorijnvdgraaf@catcrafts.net \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=siratul.islam@linux.dev \
/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