From: William Zhang <william.zhang@broadcom.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Subject: RE: [PATCH 0/2] Enable MMIO GPIO on BCMBCA
Date: Tue, 17 Sep 2024 11:13:00 -0700 [thread overview]
Message-ID: <6becd9863d87720dff1a1677c7433af8@mail.gmail.com> (raw)
In-Reply-To: <20240917-bcmbca-gpio-mmio-v1-0-674bae8664cc@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
Hi Linus,
> -----Original Message-----
> From: Linus Walleij <linus.walleij@linaro.org>
> Sent: Tuesday, September 17, 2024 5:45 AM
> To: Bartosz Golaszewski <brgl@bgdev.pl>; Rob Herring <robh@kernel.org>;
> Krzysztof Kozlowski <krzk+dt@kernel.org>; Conor Dooley
> <conor+dt@kernel.org>; William Zhang <william.zhang@broadcom.com>;
> Florian Fainelli <florian.fainelli@broadcom.com>
> Cc: linux-gpio@vger.kernel.org; devicetree@vger.kernel.org; Linus Walleij
> <linus.walleij@linaro.org>
> Subject: [PATCH 0/2] Enable MMIO GPIO on BCMBCA
>
> The Broadcom BCA (Broadband Access) SoC:s all have a dirt-simple
> MMIO GPIO.
>
> It's exposed as a direction register per 32-bit block at
> (base) and a data register per 32-bit block at (block+0x20).
>
> However I wouldn't want to use any of the old compatibles
> becaus for this undocumented SoC I have a gut feeling that
> there may be registers we don't know about at (block+0x40)
> etc and a separate compatible will be needed to slot in
> a more elaborate driver later.
>
For the BCMBCA SoCs(ARM based Broadcom broadband SoCs),
there is no need to access any register at block+0x40 and beyond
for gpio function to work. So I think the existing the brcm,bcm6345-gpio
fits the bill very well and don't need a new compatible IMHO. It is
the same tradition/rule for other blocks like wdt, nand controller
and etc. We use the oldest chip name that has the common IP.
If we upstream more elaborated driver later, it will be a dedicated gpio
controller driver and not use this basic mmio gpio and we can have
the new compatible.
> Let's do this the hard way and create a new compatible,
> and probe regular MMIO with that for now.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Linus Walleij (2):
> dt-bindings: gpio: Add BCMBCA to MMIO compatibles
> gpio: mmio: Support BCMBCA GPIO compatible
>
> Documentation/devicetree/bindings/gpio/gpio-mmio.yaml | 1 +
> drivers/gpio/gpio-mmio.c | 1 +
> 2 files changed, 2 insertions(+)
> ---
> base-commit: 98f7e32f20d28ec452afb208f9cffc08448a2652
> change-id: 20240917-bcmbca-gpio-mmio-5da863cf5a5d
>
> Best regards,
> --
> Linus Walleij <linus.walleij@linaro.org>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]
next prev parent reply other threads:[~2024-09-17 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 12:44 [PATCH 0/2] Enable MMIO GPIO on BCMBCA Linus Walleij
2024-09-17 12:44 ` [PATCH 1/2] dt-bindings: gpio: Add BCMBCA to MMIO compatibles Linus Walleij
2024-09-17 12:44 ` [PATCH 2/2] gpio: mmio: Support BCMBCA GPIO compatible Linus Walleij
2024-09-17 18:13 ` William Zhang [this message]
2024-09-17 19:03 ` [PATCH 0/2] Enable MMIO GPIO on BCMBCA Linus Walleij
2024-09-19 0:42 ` William Zhang
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=6becd9863d87720dff1a1677c7433af8@mail.gmail.com \
--to=william.zhang@broadcom.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=robh@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).