From: Rob Herring <robh@kernel.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH 1/2] dt-bindings: net: Add rfkill-gpio binding
Date: Wed, 21 Dec 2022 08:45:05 -0600 [thread overview]
Message-ID: <20221221144505.GA2848091-robh@kernel.org> (raw)
In-Reply-To: <20221221104803.1693874-1-p.zabel@pengutronix.de>
On Wed, Dec 21, 2022 at 11:48:02AM +0100, Philipp Zabel wrote:
> Add a device tree binding document for GPIO controlled rfkill switches.
> The name, type, shutdown-gpios and reset-gpios properties are the same
> as defined for ACPI.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
> .../devicetree/bindings/net/rfkill-gpio.yaml | 60 +++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/rfkill-gpio.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/rfkill-gpio.yaml b/Documentation/devicetree/bindings/net/rfkill-gpio.yaml
> new file mode 100644
> index 000000000000..6e62e6c96456
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/rfkill-gpio.yaml
> @@ -0,0 +1,60 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/net/rfkill-gpio.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: GPIO controlled rfkill switch
> +
> +maintainers:
> + - Johannes Berg <johannes@sipsolutions.net>
> + - Philipp Zabel <p.zabel@pengutronix.de>
> +
> +properties:
> + compatible:
> + const: rfkill-gpio
> +
> + name:
Did you test this? Something should complain, but maybe not. The problem
is 'name' is already a property in the unflattened DT (and old FDT
formats).
'label' would be appropriate perhaps, but why do we care what the name
is?
> + $ref: /schemas/types.yaml#/definitions/string
> + description: rfkill switch name, defaults to node name
> +
> + type:
Too generic. Property names should ideally have 1 type globally. I think
'type' is already in use. 'radio-type' instead?
> + description: rfkill radio type
> + enum:
> + - wlan
> + - bluetooth
> + - ultrawideband
> + - wimax
> + - wwan
> + - gps
> + - fm
> + - nfc
> +
> + shutdown-gpios:
> + maxItems: 1
> +
> + reset-gpios:
> + maxItems: 1
I'm lost as to why there are 2 GPIOs.
> +
> +required:
> + - compatible
> + - type
> +
> +oneOf:
> + - required:
> + - shutdown-gpios
> + - required:
> + - reset-gpios
But only 1 can be present? So just define 1 GPIO name.
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + rfkill-pcie-wlan {
Node names should be generic.
> + compatible = "rfkill-gpio";
> + name = "rfkill-pcie-wlan";
> + type = "wlan";
> + shutdown-gpios = <&gpio2 25 GPIO_ACTIVE_HIGH>;
> + };
> --
> 2.30.2
>
>
next prev parent reply other threads:[~2022-12-21 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 10:48 [PATCH 1/2] dt-bindings: net: Add rfkill-gpio binding Philipp Zabel
2022-12-21 10:48 ` [PATCH 2/2] net: rfkill: gpio: add DT support Philipp Zabel
2022-12-22 10:32 ` Krzysztof Kozlowski
2022-12-21 14:45 ` Rob Herring [this message]
2022-12-21 15:36 ` [PATCH 1/2] dt-bindings: net: Add rfkill-gpio binding Philipp Zabel
2022-12-22 10:32 ` Krzysztof Kozlowski
2022-12-22 10:20 ` Krzysztof Kozlowski
2023-01-02 17:40 ` Philipp Zabel
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=20221221144505.GA2848091-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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).