All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Sergey Shtylyov <s.shtylyov@omp.ru>
Cc: linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/2] arm64: dts: renesas: rcar-gen4: Correct avb[01] reg sizes
Date: Sun, 11 Feb 2024 15:21:29 +0100	[thread overview]
Message-ID: <cover.1707660323.git.geert+renesas@glider.be> (raw)

	Hi all,

All Ethernet AVB instances on R-Car Gen4 SoCs have registers related to
UDP/IP support, starting at offset 0x800.  However, the register blocks
for some (but not all) instances are too small to cover them.

This patch series fixes this by extending the register block sizes where
needed.  Note that this has no immediate impact on actual operation, as
the Linux driver does not use the UDP/IP registers.  Besides, ioremap()
granulatity is PAGE_SIZE, so the registers are accessible anyway.

I also considered introducing a new reg tuplet to cover the UDP/IP
registers.  However, that would complicate handling as some instances
(on some R-Car Gen2/3 SoCs) already have two reg tuplets, and there are
no reg-names defined:

    reg:
      items:
	- description: MAC register block
	- description: Stream buffer

So I think just enlarging the first register block would be fine.

To be queued in renesas-devel for v6.9, if you agree.

Thanks for your comments!

Geert Uytterhoeven (2):
  arm64: dts: renesas: r8a779a0: Correct avb[01] reg sizes
  arm64: dts: renesas: r8a779g0: Correct avb[01] reg sizes

 arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 4 ++--
 arch/arm64/boot/dts/renesas/r8a779g0.dtsi | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.34.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Sergey Shtylyov <s.shtylyov@omp.ru>
Cc: linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/2] arm64: dts: renesas: rcar-gen4: Correct avb[01] reg sizes
Date: Sun, 11 Feb 2024 15:21:29 +0100	[thread overview]
Message-ID: <cover.1707660323.git.geert+renesas@glider.be> (raw)

	Hi all,

All Ethernet AVB instances on R-Car Gen4 SoCs have registers related to
UDP/IP support, starting at offset 0x800.  However, the register blocks
for some (but not all) instances are too small to cover them.

This patch series fixes this by extending the register block sizes where
needed.  Note that this has no immediate impact on actual operation, as
the Linux driver does not use the UDP/IP registers.  Besides, ioremap()
granulatity is PAGE_SIZE, so the registers are accessible anyway.

I also considered introducing a new reg tuplet to cover the UDP/IP
registers.  However, that would complicate handling as some instances
(on some R-Car Gen2/3 SoCs) already have two reg tuplets, and there are
no reg-names defined:

    reg:
      items:
	- description: MAC register block
	- description: Stream buffer

So I think just enlarging the first register block would be fine.

To be queued in renesas-devel for v6.9, if you agree.

Thanks for your comments!

Geert Uytterhoeven (2):
  arm64: dts: renesas: r8a779a0: Correct avb[01] reg sizes
  arm64: dts: renesas: r8a779g0: Correct avb[01] reg sizes

 arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 4 ++--
 arch/arm64/boot/dts/renesas/r8a779g0.dtsi | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.34.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2024-02-11 14:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 14:21 Geert Uytterhoeven [this message]
2024-02-11 14:21 ` [PATCH 0/2] arm64: dts: renesas: rcar-gen4: Correct avb[01] reg sizes Geert Uytterhoeven
2024-02-11 14:21 ` [PATCH 1/2] arm64: dts: renesas: r8a779a0: " Geert Uytterhoeven
2024-02-11 14:21   ` Geert Uytterhoeven
2024-02-11 14:21 ` [PATCH 2/2] arm64: dts: renesas: r8a779g0: " Geert Uytterhoeven
2024-02-11 14:21   ` Geert Uytterhoeven
2024-02-11 17:01 ` [PATCH 0/2] arm64: dts: renesas: rcar-gen4: " Sergey Shtylyov
2024-02-11 17:01   ` Sergey Shtylyov
2024-02-11 18:17   ` Geert Uytterhoeven
2024-02-11 18:17     ` Geert Uytterhoeven

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=cover.1707660323.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=s.shtylyov@omp.ru \
    --cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.