From: Rob Herring <robh@kernel.org>
To: David Jander <david@protonic.nl>
Cc: Robin van der Gracht <robin@protonic.nl>,
Miguel Ojeda <ojeda@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: auxdisplay: holtek,ht16k33.yaml: Add holtek,refuse-primary-fb
Date: Wed, 30 Mar 2022 13:19:05 -0500 [thread overview]
Message-ID: <YkSfGfzyCIDIpVN8@robh.at.kernel.org> (raw)
In-Reply-To: <20220330073440.3986724-3-david@protonic.nl>
On Wed, Mar 30, 2022 at 09:34:40AM +0200, David Jander wrote:
> Document the DT property that will cause the holtek auxdisplay driver to
> back off if it detects that it is the first driver to probe a framebuffer
> device.
>
> Signed-off-by: David Jander <david@protonic.nl>
> ---
> .../devicetree/bindings/auxdisplay/holtek,ht16k33.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/auxdisplay/holtek,ht16k33.yaml b/Documentation/devicetree/bindings/auxdisplay/holtek,ht16k33.yaml
> index fc4873deb76f..4de32c3e26ce 100644
> --- a/Documentation/devicetree/bindings/auxdisplay/holtek,ht16k33.yaml
> +++ b/Documentation/devicetree/bindings/auxdisplay/holtek,ht16k33.yaml
> @@ -53,6 +53,9 @@ properties:
> $ref: /schemas/leds/common.yaml#
> unevaluatedProperties: false
>
> + holtek,refuse-primary-fb:
> + description: Refuse to claim the first framebuffer device
How is this specific to this device?
Rob
prev parent reply other threads:[~2022-03-30 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 7:34 [PATCH 0/2] drivers: auxdisplay: ht16k33.c: Add option to refuse claiming primary fb David Jander
2022-03-30 7:34 ` [PATCH 1/2] " David Jander
2022-03-30 7:34 ` [PATCH 2/2] dt-bindings: auxdisplay: holtek,ht16k33.yaml: Add holtek,refuse-primary-fb David Jander
2022-03-30 13:50 ` Rob Herring
2022-03-30 18:19 ` Rob Herring [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=YkSfGfzyCIDIpVN8@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=robin@protonic.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.