From: Rob Herring <robh@kernel.org>
To: Andrej Valek <andrej.valek@siemens.com>
Cc: nick@shmanahar.org, hadess@hadess.net, dmitry.torokhov@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: goodix
Date: Wed, 4 Nov 2020 15:44:21 -0600 [thread overview]
Message-ID: <20201104214421.GA4172944@bogus> (raw)
In-Reply-To: <20201029170313.25529-3-andrej.valek@siemens.com>
On Thu, Oct 29, 2020 at 06:03:12PM +0100, Andrej Valek wrote:
> Add information about option how to disable FW loading for each boot.
Please fix your subject.
>
> Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
> ---
> Documentation/devicetree/bindings/input/touchscreen/goodix.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml b/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
> index da5b0d87e16d0..e7d9404c86abf 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
> +++ b/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
> @@ -53,6 +53,7 @@ properties:
> touchscreen-size-x: true
> touchscreen-size-y: true
> touchscreen-swapped-x-y: true
> + touchscreen-do-not-load-fw: false
This is not a generic touchscreen property. It needs a vendor prefix.
>
> additionalProperties: false
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-11-04 21:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 17:03 [PATCH 0/3] Firmware loading option Andrej Valek
2020-10-29 17:03 ` [PATCH 1/3] Input: goodix - add option to disable firmware loading Andrej Valek
2020-10-29 20:36 ` Dmitry Torokhov
2020-10-30 8:45 ` Valek, Andrej
2020-10-30 9:56 ` Hans de Goede
2020-10-30 11:02 ` Valek, Andrej
2020-11-23 6:53 ` Dmitry Torokhov
2020-11-23 8:46 ` Hans de Goede
2020-11-10 9:07 ` [PATCH v3 1/4] " Andrej Valek
2020-11-10 18:15 ` [PATCH v4 " Andrej Valek
2020-10-29 17:03 ` [PATCH 2/3] dt-bindings: goodix Andrej Valek
2020-11-04 21:44 ` Rob Herring [this message]
2020-11-10 9:07 ` [PATCH v3 2/4] dt-bindings: touchscreen: goodix: add info about disabling FW loading Andrej Valek
2020-11-10 13:43 ` Rob Herring
2020-11-10 18:15 ` [PATCH v4 " Andrej Valek
2020-11-16 17:08 ` Rob Herring
2020-10-29 17:03 ` [PATCH 3/3] Input: atmel_mxt_ts - add option to disable firmware loading Andrej Valek
2020-11-10 9:07 ` [PATCH v3 3/4] " Andrej Valek
2020-11-10 18:15 ` [PATCH v4 " Andrej Valek
2020-11-23 6:56 ` Dmitry Torokhov
2020-11-06 10:05 ` [PATCH v2 0/3] Firmware loading option Andrej Valek
2020-11-06 10:05 ` [PATCH v2 1/3] Input: st1232 - add support resolution reading Andrej Valek
2020-11-10 9:07 ` [PATCH v3 4/4] " Andrej Valek
2020-11-10 18:15 ` [PATCH v4 " Andrej Valek
2020-11-06 10:05 ` [PATCH v2 2/3] dt-bindings: goodix Andrej Valek
2020-11-09 21:37 ` Rob Herring
2020-11-06 10:05 ` [PATCH v2 3/3] Input: goodix - add option to disable firmware loading Andrej Valek
2020-11-10 9:07 ` [PATCH v3 0/4] Firmware loading option Andrej Valek
2020-11-10 18:15 ` [PATCH v4 " Andrej Valek
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=20201104214421.GA4172944@bogus \
--to=robh@kernel.org \
--cc=andrej.valek@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@shmanahar.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;
as well as URLs for NNTP newsgroup(s).