devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: linux-riscv@lists.infradead.org, Anup Patel <anup.patel@wdc.com>,
	Atish Patra <atish.patra@wdc.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	devicetree@vger.kernel.org, Sean Anderson <seanga2@gmail.com>,
	Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH v19 08/17] dt-bindings: fix sifive gpio properties
Date: Wed, 10 Feb 2021 10:56:27 -0600	[thread overview]
Message-ID: <20210210165627.GA2327971@robh.at.kernel.org> (raw)
In-Reply-To: <20210210050230.131281-9-damien.lemoal@wdc.com>

On Wed, 10 Feb 2021 14:02:21 +0900, Damien Le Moal wrote:
> The sifive gpio IP block supports up to 32 GPIOs. Reflect that in the
> interrupts property description and maxItems. Also add the standard
> ngpios property to describe the number of GPIOs available on the
> implementation.
> 
> Also add the "canaan,k210-gpiohs" compatible string to indicate the use
> of this gpio controller in the Canaan Kendryte K210 SoC. If this
> compatible string is used, do not define the clocks property as
> required as the K210 SoC does not have a software controllable clock
> for the Sifive gpio IP block.
> 
> Cc: Paul Walmsley <paul.walmsley@sifive.com>
> Cc: Rob Herring <robh@kernel.org>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
> ---
>  .../devicetree/bindings/gpio/sifive,gpio.yaml | 25 ++++++++++++++++---
>  1 file changed, 22 insertions(+), 3 deletions(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2021-02-10 16:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210210050230.131281-1-damien.lemoal@wdc.com>
2021-02-10  5:02 ` [PATCH v19 02/17] dt-bindings: update MAINTAINERS file Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 03/17] dt-bindings: add Canaan boards compatible strings Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 04/17] dt-bindings: update risc-v cpu properties Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 05/17] dt-bindings: update sifive plic compatible string Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 06/17] dt-bindings: update sifive clint " Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 07/17] dt-bindings: update sifive uart " Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 08/17] dt-bindings: fix sifive gpio properties Damien Le Moal
2021-02-10 16:56   ` Rob Herring [this message]
2021-02-10  5:02 ` [PATCH v19 09/17] dt-bindings: add resets property to dw-apb-timer Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 10/17] riscv: Update Canaan Kendryte K210 device tree Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 11/17] riscv: Add SiPeed MAIX BiT board " Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 12/17] riscv: Add SiPeed MAIX DOCK " Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 13/17] riscv: Add SiPeed MAIX GO " Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 14/17] riscv: Add SiPeed MAIXDUINO " Damien Le Moal
2021-02-10  5:02 ` [PATCH v19 15/17] riscv: Add Kendryte KD233 " Damien Le Moal

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=20210210165627.GA2327971@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=anup.patel@wdc.com \
    --cc=atish.patra@wdc.com \
    --cc=damien.lemoal@wdc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=seanga2@gmail.com \
    /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).