The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Siratul Islam" <siratul.islam@linux.dev>
To: "Jorijn van der Graaf" <jorijnvdgraaf@catcrafts.net>,
	"Jonathan Cameron" <jic23@kernel.org>
Cc: "Jorijn van der Graaf" <jorijnvdgraaf@catcrafts.net>,
	"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: Wed, 15 Jul 2026 22:16:47 +0000	[thread overview]
Message-ID: <989a9b6a2024415ce29c1aef162c6a4d341dfa45@linux.dev> (raw)
In-Reply-To: <20260715204616.46517-1-jorijnvdgraaf@catcrafts.net>

July 16, 2026 at 2:46 AM, "Jorijn van der Graaf" <jorijnvdgraaf@catcrafts.net mailto:jorijnvdgraaf@catcrafts.net?to=%22Jorijn%20van%20der%20Graaf%22%20%3Cjorijnvdgraaf%40catcrafts.net%3E > wrote:


> 
> Hi Siratul,
> 
> On Thu, 2026-07-16 at 00:32 +0600, Siratul Islam wrote:
> 
...
> 
> > 
> > I usually don't bother with bindings. But here I have some thoughts.
> >  You could reuse the QMC5883L binding. As for the device lacking both
> >  interrupt and vddio pins, you could exclude them like
> > 
> >  allOf:
> >  - if:
> >  properties:
> >  compatible:
> >  contains:
> >  const: qstcorp,qmc6308
> >  then:
> >  properties:
> >  interrupts: false
> >  vddio-supply: false
> > 
> >  But you would also need to remove the global required vddio-supply and
> >  make it required for qmc5883l.
> >  Or flip the logic of allOf. Considering a lot of the magnetometer
> >  bindings look very similar anyway, I'm not sure if it's worth
> >  combining them. Maybe Jonathan or DT maintainers would have a better
> >  opinion.
> > 
> 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.
> The two schemas share only compatible/reg/vdd-supply: the QMC5883L has
> an interrupt pin and requires vddio-supply, while the QMC6308 (a 4-pin
> WLCSP) has neither. So a combined document would be mostly conditional
> machinery - the block you sketch plus a second one (or the flipped
> allOf you mention) for the required list. And as the two chips are not
> register-compatible, there is no fallback-compatible relationship to
> express either.
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.
> 
> Happy to fold it into qstcorp,qmc5883l.yaml in v2 if Jonathan or the
> DT maintainers prefer that shape.
> 
> Thanks,
> Jorijn
>
--
Best regards,
Sirat

  reply	other threads:[~2026-07-15 22:16 UTC|newest]

Thread overview: 14+ 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 [this message]
2026-07-16 14:18         ` Jorijn van der Graaf
2026-07-14 20:28 ` [PATCH 2/2] iio: magnetometer: add support for " Jorijn van der Graaf
2026-07-14 21:21   ` Uwe Kleine-König
2026-07-15 20:46     ` Jorijn van der Graaf
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

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=989a9b6a2024415ce29c1aef162c6a4d341dfa45@linux.dev \
    --to=siratul.islam@linux.dev \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --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 \
    /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