From: Rob Herring <robh@kernel.org>
To: Emil Renner Berthing <emil.renner.berthing@canonical.com>
Cc: Fu Wei <wefu@redhat.com>, Conor Dooley <conor+dt@kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Hoan Tran <hoan@os.amperecomputing.com>,
Linus Walleij <linus.walleij@linaro.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Rob Herring <robh+dt@kernel.org>,
linux-gpio@vger.kernel.org, Andy Shevchenko <andy@kernel.org>,
linux-kernel@vger.kernel.org, Jisheng Zhang <jszhang@kernel.org>,
Serge Semin <fancer.lancer@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Guo Ren <guoren@kernel.org>,
linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v1 4/8] dt-bindings: gpio: dwapb: allow gpio-ranges
Date: Fri, 15 Dec 2023 14:21:58 -0600 [thread overview]
Message-ID: <170267171586.328597.4361294916580351710.robh@kernel.org> (raw)
In-Reply-To: <20231215143906.3651122-5-emil.renner.berthing@canonical.com>
On Fri, 15 Dec 2023 15:39:02 +0100, Emil Renner Berthing wrote:
> Allow the generic gpio-ranges property so GPIOs can be mapped to their
> corresponding pin. This way control of GPIO on pins that are already used
> by other peripherals can be denied and basic pinconf can be done on pin
> controllers that support it.
>
> Signed-off-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>
> ---
> Documentation/devicetree/bindings/gpio/snps,dw-apb-gpio.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-12-15 20:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 14:38 [PATCH v1 0/8] Add T-Head TH15020 SoC pin control Emil Renner Berthing
2023-12-15 14:38 ` [PATCH v1 1/8] dt-bindings: pinctrl: Add thead,th1520-pinctrl bindings Emil Renner Berthing
2023-12-15 20:21 ` Rob Herring
2023-12-16 13:57 ` Emil Renner Berthing
2023-12-20 19:24 ` Linus Walleij
2023-12-21 12:28 ` Emil Renner Berthing
2023-12-21 13:44 ` Linus Walleij
2023-12-21 14:07 ` Emil Renner Berthing
2023-12-23 0:18 ` Linus Walleij
2023-12-20 19:20 ` Linus Walleij
2023-12-21 12:21 ` Emil Renner Berthing
2023-12-15 14:39 ` [PATCH v1 2/8] pinctrl: Add driver for the T-Head TH1520 SoC Emil Renner Berthing
2023-12-15 17:27 ` Andy Shevchenko
2023-12-15 14:39 ` [PATCH v1 3/8] riscv: dts: thead: Add TH1520 pin control nodes Emil Renner Berthing
2023-12-15 14:39 ` [PATCH v1 4/8] dt-bindings: gpio: dwapb: allow gpio-ranges Emil Renner Berthing
2023-12-15 20:21 ` Rob Herring [this message]
2023-12-18 10:05 ` Bartosz Golaszewski
2023-12-15 14:39 ` [PATCH v1 5/8] riscv: dts: thead: Add TH1520 GPIO ranges Emil Renner Berthing
2023-12-15 14:39 ` [PATCH v1 6/8] riscv: dts: thead: Adjust TH1520 GPIO labels Emil Renner Berthing
2023-12-15 14:39 ` [PATCH v1 7/8] riscv: dts: thead: Add TH1520 pinctrl settings for UART0 Emil Renner Berthing
2023-12-15 14:39 ` [PATCH v1 8/8] riscv: dtb: thead: Add BeagleV Ahead LEDs Emil Renner Berthing
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=170267171586.328597.4361294916580351710.robh@kernel.org \
--to=robh@kernel.org \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=fancer.lancer@gmail.com \
--cc=guoren@kernel.org \
--cc=hoan@os.amperecomputing.com \
--cc=jszhang@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=wefu@redhat.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