CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@nabladev.com>
To: Biju <biju.das.au@gmail.com>
Cc: cip-dev@lists.cip-project.org,
	Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>,
	Pavel Machek <pavel@nabladev.com>,
	Biju Das <biju.das.jz@bp.renesas.com>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 5.10.y-cip 0/4] arm64: dts: renesas: Add max-frequency to SDHI nodes
Date: Wed, 15 Jul 2026 13:01:58 +0200	[thread overview]
Message-ID: <aldopt3Cx04KEM5L@duo.ucw.cz> (raw)
In-Reply-To: <20260713120354.29288-1-biju.das.jz@bp.renesas.com>

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]

Hi!

> This patch series aims to add the max-frequency property set to
> 133333333 Hz (133.33 MHz) to both SDHI0 and SDHI1 MMC controller nodes in
> the RZ/G2{L,LC,UL}/RZ/V2L device tree.
> 
> This change results in approximately 33% performance improvement as
> it sets the SD clk to 100 MHz instead of the max 133 MHz.
> 
> All the patches in this series are cherry-picked from mainline.

Thank you, applied.

Best regards,
								Pavel

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      parent reply	other threads:[~2026-07-15 11:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 12:03 [PATCH 5.10.y-cip 0/4] arm64: dts: renesas: Add max-frequency to SDHI nodes Biju
2026-07-13 12:03 ` [PATCH 5.10.y-cip 1/4] arm64: dts: renesas: r9a07g043: " Biju
2026-07-13 12:03 ` [PATCH 5.10.y-cip 2/4] arm64: dts: renesas: r9a07g044: Rename SDHI clocks Biju
2026-07-13 12:03 ` [PATCH 5.10.y-cip 3/4] arm64: dts: renesas: r9a07g044: Add max-frequency to SDHI nodes Biju
2026-07-13 12:03 ` [PATCH 5.10.y-cip 4/4] arm64: dts: renesas: r9a07g054: " Biju
2026-07-13 21:09 ` [PATCH 5.10.y-cip 0/4] arm64: dts: renesas: " Pavel Machek
2026-07-14  6:30   ` Biju Das
2026-07-14 18:33     ` Pavel Machek
2026-07-13 21:13 ` Pavel Machek
2026-07-15 11:01 ` Pavel Machek [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=aldopt3Cx04KEM5L@duo.ucw.cz \
    --to=pavel@nabladev.com \
    --cc=biju.das.au@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --cc=prabhakar.mahadev-lad.rj@bp.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