devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: robh+dt@kernel.org, jdelvare@suse.com,
	devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: Add vendor prefix and trivial device for BluTek BPA-RS600
Date: Fri, 19 Mar 2021 14:31:09 -0700	[thread overview]
Message-ID: <20210319213109.GA24334@roeck-us.net> (raw)
In-Reply-To: <20210317040231.21490-1-chris.packham@alliedtelesis.co.nz>

On Wed, Mar 17, 2021 at 05:02:29PM +1300, Chris Packham wrote:
> Add vendor prefix "blutek" for BluTek Power.
> Add trivial device entry for BPA-RS600.
> 
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>

For my reference (waiting for bindings approval):

Reviewed-by: Guenter Roeck <linux@roeck-us.net>

Guenter

> ---
> 
> Notes:
>     Changes in v3:
>     - None
>     Changes in v2:
>     - None
> 
>  Documentation/devicetree/bindings/trivial-devices.yaml | 2 ++
>  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>  2 files changed, 4 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
> index a327130d1faa..569236e9bed0 100644
> --- a/Documentation/devicetree/bindings/trivial-devices.yaml
> +++ b/Documentation/devicetree/bindings/trivial-devices.yaml
> @@ -50,6 +50,8 @@ properties:
>            - atmel,atsha204a
>              # i2c h/w elliptic curve crypto module
>            - atmel,atecc508a
> +            # BPA-RS600: Power Supply
> +          - blutek,bpa-rs600
>              # Bosch Sensortec pressure, temperature, humididty and VOC sensor
>            - bosch,bme680
>              # CM32181: Ambient Light Sensor
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index f6064d84a424..d9d7226f5dfe 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -169,6 +169,8 @@ patternProperties:
>      description: Beckhoff Automation GmbH & Co. KG
>    "^bitmain,.*":
>      description: Bitmain Technologies
> +  "^blutek,.*":
> +    description: BluTek Power
>    "^boe,.*":
>      description: BOE Technology Group Co., Ltd.
>    "^bosch,.*":

  parent reply	other threads:[~2021-03-19 21:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  4:02 [PATCH v3 1/3] dt-bindings: Add vendor prefix and trivial device for BluTek BPA-RS600 Chris Packham
2021-03-17  4:02 ` [PATCH v3 2/3] hwmon: (pmbus): Replace - with _ in device names before registration Chris Packham
2021-03-19 21:30   ` Guenter Roeck
2021-03-17  4:02 ` [PATCH v3 3/3] hwmon: (pmbus): Add driver for BluTek BPA-RS600 Chris Packham
2021-03-19 21:31   ` Guenter Roeck
2021-03-29 22:05   ` Guenter Roeck
2021-03-19 21:31 ` Guenter Roeck [this message]
2021-03-26  0:17 ` [PATCH v3 1/3] dt-bindings: Add vendor prefix and trivial device " Rob Herring
2021-03-29 22:03 ` Guenter Roeck

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=20210319213109.GA24334@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).