public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] arm64: dts: renesas: r8a779g0/white-hawk: Add SDHI/eMMC support
Date: Wed, 12 Oct 2022 20:58:29 +0200	[thread overview]
Message-ID: <Y0cOVQlZAViR1gY5@shikoro> (raw)
In-Reply-To: <cover.1665558371.git.geert+renesas@glider.be>


[-- Attachment #1.1: Type: text/plain, Size: 503 bytes --]


> The White Hawk CPU board also has a µSD-slot, which is mutually
> exclusive with the eMMC, and obstructed by a pin header on the BreakOut
> Board.  Hence accessing it requires removing the CPU board, which is a
> task I haven't undertaken.

This sounds pretty similar to the uSD slot on the Spider board.
Shimoda-san and I have decided there to only upstream eMMC support. I
think the same can easily be argued for WhiteHawk, so your series looks
fine as is regarding upstream, I'd say.


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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

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

      parent reply	other threads:[~2022-10-12 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12  7:12 [PATCH 0/2] arm64: dts: renesas: r8a779g0/white-hawk: Add SDHI/eMMC support Geert Uytterhoeven
2022-10-12  7:12 ` [PATCH 1/2] arm64: dts: renesas: r8a779g0: Add SDHI node Geert Uytterhoeven
2022-10-12 19:00   ` Wolfram Sang
2022-10-12  7:12 ` [PATCH 2/2] arm64: dts: renesas: white-hawk-cpu: Add eMMC support Geert Uytterhoeven
2022-10-12 19:01   ` Wolfram Sang
2022-10-12 18:58 ` Wolfram Sang [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=Y0cOVQlZAViR1gY5@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=yoshihiro.shimoda.uh@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