From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
Thanh Quan <thanh.quan.xn@renesas.com>
Subject: Re: [PATCH 1/5] pinctrl: renesas: r8a779g0: Remove AVB[01]_MII
Date: Tue, 4 Nov 2025 22:32:48 +0100 [thread overview]
Message-ID: <bd36edc8-2a74-40db-a21f-d420ef7f49f6@mailbox.org> (raw)
In-Reply-To: <58662f50136280532bcc8bbe94741d82425bd118.1762274384.git.geert+renesas@glider.be>
On 11/4/25 5:59 PM, Geert Uytterhoeven wrote:
> From: Thanh Quan <thanh.quan.xn@renesas.com>
>
> Rev.1.30 of the R-Car V4H Series Hardware User’s Manual removed the
> "AVB[01]_MII_*" signals from the pin control register tables. As these
> are further unused in the pin control driver, they can be removed
> safely.
>
> Signed-off-by: Thanh Quan <thanh.quan.xn@renesas.com>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
Matches U-Boot patch too, thanks !
next prev parent reply other threads:[~2025-11-04 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 16:59 [PATCH 0/5] pinctrl: renesas: rcar-v4x: Remove removed signals Geert Uytterhoeven
2025-11-04 16:59 ` [PATCH 1/5] pinctrl: renesas: r8a779g0: Remove AVB[01]_MII Geert Uytterhoeven
2025-11-04 21:32 ` Marek Vasut [this message]
2025-11-04 16:59 ` [PATCH 2/5] pinctrl: renesas: r8a779g0: Remove CC5_OSCOUT Geert Uytterhoeven
2025-11-04 21:27 ` Marek Vasut
2025-11-05 8:34 ` Geert Uytterhoeven
2025-11-04 16:59 ` [PATCH 3/5] pinctrl: renesas: r8a779g0: Remove STPWT_EXTFXR Geert Uytterhoeven
2025-11-04 21:28 ` Marek Vasut
2025-11-04 16:59 ` [PATCH 4/5] pinctrl: renesas: r8a779h0: Remove CC5_OSCOUT Geert Uytterhoeven
2025-11-04 21:28 ` Marek Vasut
2025-11-04 16:59 ` [PATCH 5/5] pinctrl: renesas: r8a779h0: Remove STPWT_EXTFXR Geert Uytterhoeven
2025-11-04 21:29 ` Marek Vasut
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=bd36edc8-2a74-40db-a21f-d420ef7f49f6@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=thanh.quan.xn@renesas.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).