public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: marcpaolo.sosa@analog.com,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: input: add adi,max16150.yaml
Date: Mon, 23 Feb 2026 18:01:46 +0100	[thread overview]
Message-ID: <c2985ac9-1917-4044-a896-8e701a3046af@kernel.org> (raw)
In-Reply-To: <20260223-max16150-v1-1-38e2a4f0d0f1@analog.com>

On 23/02/2026 12:03, Marc Paolo Sosa via B4 Relay wrote:
> +
> +properties:
> +  compatible:
> +    description:
> +      Specifies the supported device variants. The MAX16150 and MAX16169 are supported.
> +    enum:
> +      - adi,max16150a
> +      - adi,max16150b
> +      - adi,max16169a
> +      - adi,max16169b

Your driver code says 16150 and 16169 are compatible, to express it with
fallback (oneOf). See example-schema.

Best regards,
Krzysztof

  parent reply	other threads:[~2026-02-23 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 11:03 [PATCH 0/2] add driver for max16150 Marc Paolo Sosa via B4 Relay
2026-02-23 11:03 ` [PATCH 1/2] dt-bindings: input: add adi,max16150.yaml Marc Paolo Sosa via B4 Relay
2026-02-23 12:24   ` Rob Herring (Arm)
2026-03-17  3:14     ` Sosa, Marc Paolo
2026-02-23 16:50   ` Rob Herring
2026-03-17  3:13     ` Sosa, Marc Paolo
2026-02-23 17:01   ` Krzysztof Kozlowski [this message]
2026-03-17  1:51     ` Sosa, Marc Paolo
2026-02-23 11:03 ` [PATCH 2/2] input: misc: add driver for max16150 Marc Paolo Sosa via B4 Relay
2026-02-24 22:42   ` Dmitry Torokhov
2026-03-17  3:12     ` Sosa, Marc Paolo

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=c2985ac9-1917-4044-a896-8e701a3046af@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcpaolo.sosa@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