From: Conor Dooley <conor@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v3 1/6] dt-bindings: gpio: aspeed,ast2400-gpio: Support ast2700
Date: Fri, 13 Sep 2024 19:22:43 +0100 [thread overview]
Message-ID: <20240913-swipe-crummiest-0d449f2e3314@spud> (raw)
In-Reply-To: <20240913074325.239390-2-billy_tsai@aspeedtech.com>
On Fri, Sep 13, 2024 at 03:43:20PM +0800, Billy Tsai wrote:
> The AST2700 is the 7th generation SoC from Aspeed, featuring two GPIO
> controllers: one with 12 GPIO pins and another with 216 GPIO pins.
>
> Signed-off-by: Billy Tsai <billy_tsai@aspeedtech.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/linux-aspeed/attachments/20240913/425f986c/attachment.sig>
next prev parent reply other threads:[~2024-09-13 18:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 7:43 [PATCH v3 0/6] Add Aspeed G7 gpio support Billy Tsai
2024-09-13 7:43 ` [PATCH v3 1/6] dt-bindings: gpio: aspeed,ast2400-gpio: Support ast2700 Billy Tsai
2024-09-13 18:22 ` Conor Dooley [this message]
2024-09-13 7:43 ` [PATCH v3 2/6] gpio: aspeed: Remove the name for bank array Billy Tsai
2024-09-16 1:51 ` Andrew Jeffery
2024-09-13 7:43 ` [PATCH v3 3/6] gpio: aspeed: Create llops to handle hardware access Billy Tsai
2024-09-16 2:43 ` Andrew Jeffery
2024-09-16 3:00 ` Andrew Jeffery
2024-09-19 6:12 ` Billy Tsai
2024-09-13 7:43 ` [PATCH v3 4/6] gpio: aspeed: Support G7 Aspeed gpio controller Billy Tsai
2024-09-13 7:43 ` [PATCH v3 5/6] gpio: aspeed: Change the macro to support deferred probe Billy Tsai
2024-09-14 8:44 ` kernel test robot
2024-09-14 15:33 ` kernel test robot
2024-09-13 7:43 ` [PATCH v3 6/6] gpio: aspeed: Add the flush write to ensure the write complete Billy Tsai
2024-09-16 3:03 ` Andrew Jeffery
2024-09-19 6:07 ` Billy Tsai
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=20240913-swipe-crummiest-0d449f2e3314@spud \
--to=conor@kernel.org \
--cc=linux-aspeed@lists.ozlabs.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