From: Siratul Islam <siratul.islam@linux.dev>
To: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>,
Jonathan Cameron <jic23@kernel.org>
Cc: "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: Thu, 16 Jul 2026 00:32:20 +0600 [thread overview]
Message-ID: <03e59d2907ffccc2cecd94ab44d19359f2474733.camel@linux.dev> (raw)
In-Reply-To: <20260714202842.340293-2-jorijnvdgraaf@catcrafts.net>
On Tue, 2026-07-14 at 22:28 +0200, Jorijn van der Graaf wrote:
> Add device tree bindings for the QST QMC6308, a 3-axis AMR
> magnetometer. It is an I2C device in a 4-pin WLCSP package with a
> single supply and no interrupt pin, at I2C address 0x2c.
>
> Assisted-by: Claude:claude-fable-5
> Signed-off-by: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>
> ---
>
...
> +properties:
> + compatible:
> + enum:
> + - qstcorp,qmc6308
> +
> + reg:
> + maxItems: 1
> +
> + vdd-supply: true
> +
> + mount-matrix: true
You could add this prop to the existing QMC5883l binding. See the comment below.
> +
> +additionalProperties: false
> +
> +required:
> + - compatible
> + - reg
> + - vdd-supply
> +
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.
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + magnetometer@2c {
> + compatible = "qstcorp,qmc6308";
> + reg = <0x2c>;
> + vdd-supply = <&vdd_1v8_reg>;
> + };
> + };
>
--
Best regards,
Sirat
next prev parent reply other threads:[~2026-07-15 18:32 UTC|newest]
Thread overview: 8+ 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 [this message]
2026-07-15 20:46 ` Jorijn van der Graaf
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
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=03e59d2907ffccc2cecd94ab44d19359f2474733.camel@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