From: Rob Herring <robh@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: "Jamie Gibbons" <jamie.gibbons@microchip.com>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
linux-kernel@vger.kernel.org,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Daire McNamara" <daire.mcnamara@microchip.com>,
devicetree@vger.kernel.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
linux-pci@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
linux-gpio@vger.kernel.org,
"Valentina Fernandez" <valentina.fernandezalanis@microchip.com>,
linux-riscv@lists.infradead.org,
"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH v1 2/5] dt-bindings: gpio: mpfs: add coreGPIO support
Date: Wed, 27 Mar 2024 12:57:16 -0500 [thread overview]
Message-ID: <171156223562.3706464.15520740960365102234.robh@kernel.org> (raw)
In-Reply-To: <20240327-procurer-rascal-33bca7d5d14b@spud>
On Wed, 27 Mar 2024 12:24:37 +0000, Conor Dooley wrote:
> From: Jamie Gibbons <jamie.gibbons@microchip.com>
>
> The GPIO controllers on PolarFire SoC were based on the "soft" IP
> CoreGPIO, but the inp/outp registers are at different offsets. Add
> compatible to allow for support of both sets of offsets. The soft
> core will not always have interrupts wired up, so only enforce them for
> the "hard" core on PolarFire SoC.
>
> Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> .../bindings/gpio/microchip,mpfs-gpio.yaml | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2024-03-27 17:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 12:24 [PATCH v1 0/5] BeagleV Fire support Conor Dooley
2024-03-27 12:24 ` [PATCH v1 1/5] dt-bindings: riscv: microchip: document beaglev-fire Conor Dooley
2024-03-27 17:56 ` Rob Herring
2024-03-27 12:24 ` [PATCH v1 2/5] dt-bindings: gpio: mpfs: add coreGPIO support Conor Dooley
2024-03-27 17:57 ` Rob Herring [this message]
2024-03-29 10:28 ` Bartosz Golaszewski
2024-03-27 12:24 ` [PATCH v1 3/5] dt-bindings: gpio: mpfs: allow gpio-line-names Conor Dooley
2024-03-27 17:57 ` Rob Herring
2024-03-29 10:29 ` Bartosz Golaszewski
2024-03-27 12:24 ` [PATCH v1 4/5] dt-bindings: PCI: microchip: increase number of items in ranges property Conor Dooley
2024-03-27 17:57 ` Rob Herring
2024-04-19 15:57 ` Conor Dooley
2024-03-27 12:24 ` [PATCH v1 5/5] riscv: dts: microchip: add an initial devicetree for the BeagleV Fire Conor Dooley
2024-05-28 11:57 ` Conor Dooley
2024-05-22 23:32 ` [PATCH v1 0/5] BeagleV Fire support patchwork-bot+linux-riscv
2024-06-19 11:24 ` (subset) " Conor Dooley
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=171156223562.3706464.15520740960365102234.robh@kernel.org \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jamie.gibbons@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=valentina.fernandezalanis@microchip.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).