From: Paolo Abeni <pabeni@redhat.com>
To: Jacky Chou <jacky_chou@aspeedtech.com>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, p.zabel@pengutronix.de,
ratbert@faraday-tech.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/7] Add Aspeed G7 FTGMAC100 support
Date: Thu, 21 Nov 2024 09:41:39 +0100 [thread overview]
Message-ID: <13a81556-d28c-46d0-85d6-d2fb1620d24e@redhat.com> (raw)
In-Reply-To: <20241120075017.2590228-1-jacky_chou@aspeedtech.com>
On 11/20/24 08:50, Jacky Chou wrote:
> The Aspeed 7th generation SoC features three FTGMAC100.
> The main difference from the previous generation is that the
> FTGMAC100 adds support for 64-bit DMA capability. Another change
> is that the RMII/RGMII pin strap configuration is changed to be set
> in the bit 20 fo register 0x50.
>
> Jacky Chou (7):
> dt-bindings: net: ftgmac100: support for AST2700
> net: faraday: Add ARM64 in FTGMAC100 for AST2700
> net: ftgmac100: Add reset toggling for Aspeed SOCs
> net: ftgmac100: Add support for AST2700
> net: ftgmac100: add pin strap configuration for AST2700
> net: ftgmac100: Add 64-bit DMA support for AST2700
> net: ftgmac100: remove extra newline symbols
>
> .../bindings/net/faraday,ftgmac100.yaml | 3 +-
> drivers/net/ethernet/faraday/Kconfig | 5 +-
> drivers/net/ethernet/faraday/ftgmac100.c | 77 +++++++++++++++----
> drivers/net/ethernet/faraday/ftgmac100.h | 10 +++
> 4 files changed, 75 insertions(+), 20 deletions(-)
## Form letter - net-next-closed
The merge window for v6.13 has begun and net-next is closed for new
drivers, features, code refactoring and optimizations. We are currently
accepting bug fixes only.
Please repost when net-next reopens after Dec 2nd.
RFC patches sent for review only are welcome at any time.
See:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
prev parent reply other threads:[~2024-11-21 8:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 7:50 Jacky Chou
2024-11-20 7:50 ` [PATCH net-next v3 1/7] dt-bindings: net: ftgmac100: support for AST2700 Jacky Chou
2024-11-25 10:24 ` Philipp Zabel
2024-11-25 16:13 ` Krzysztof Kozlowski
2024-11-27 3:57 ` 回覆: " Jacky Chou
2024-11-27 3:50 ` Jacky Chou
2024-11-20 7:50 ` [PATCH net-next v3 2/7] net: faraday: Add ARM64 in FTGMAC100 " Jacky Chou
2024-11-25 16:12 ` Krzysztof Kozlowski
2024-11-20 7:50 ` [PATCH net-next v3 3/7] net: ftgmac100: Add reset toggling for Aspeed SOCs Jacky Chou
2024-11-25 10:27 ` Philipp Zabel
2024-11-27 3:48 ` 回覆: " Jacky Chou
2024-11-20 7:50 ` [PATCH net-next v3 4/7] net: ftgmac100: Add support for AST2700 Jacky Chou
2024-11-20 7:50 ` [PATCH net-next v3 5/7] net: ftgmac100: add pin strap configuration " Jacky Chou
2024-11-20 7:50 ` [PATCH net-next v3 6/7] net: ftgmac100: Add 64-bit DMA support " Jacky Chou
2024-11-20 7:50 ` [PATCH net-next v3 7/7] net: ftgmac100: remove extra newline symbols Jacky Chou
2024-11-21 8:41 ` Paolo Abeni [this message]
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=13a81556-d28c-46d0-85d6-d2fb1620d24e@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jacky_chou@aspeedtech.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=ratbert@faraday-tech.com \
--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
all inboxes | Powered by JetHome®