From: Wolfram Sang <wsa@the-dreams.de>
To: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Simon Horman <horms@verge.net.au>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
"xu_shunji@hoperun.com" <xu_shunji@hoperun.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH] arm64: dts: renesas: hihope-common: Add uSD and eMMC
Date: Wed, 12 Jun 2019 13:19:00 +0200 [thread overview]
Message-ID: <20190612111900.2crgsg4adinrrw5u@ninjato> (raw)
In-Reply-To: <TY1PR01MB1770B85D549CD20C963620E6C0EC0@TY1PR01MB1770.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
I think it is confusing to describe a HS400 property if the HW is not
capable of it. Even if the driver has a safety check and will prevent it
from being used.
But as I said, I won't be insisting. I understood it simplifies things
in grouping boards. From my side, we can close the case here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-12 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 8:14 [PATCH] arm64: dts: renesas: hihope-common: Add uSD and eMMC Fabrizio Castro
2019-06-12 8:27 ` Geert Uytterhoeven
2019-06-12 8:39 ` Fabrizio Castro
2019-06-12 9:29 ` Geert Uytterhoeven
2019-06-12 9:45 ` Wolfram Sang
2019-06-12 10:03 ` Fabrizio Castro
2019-06-12 10:15 ` Wolfram Sang
2019-06-12 11:02 ` Fabrizio Castro
2019-06-12 11:19 ` Wolfram Sang [this message]
2019-06-12 11:55 ` Simon Horman
2019-06-12 12:29 ` Fabrizio Castro
2019-06-12 11:07 ` Geert Uytterhoeven
2019-06-12 11:06 ` Geert Uytterhoeven
2019-06-12 12:16 ` Simon Horman
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=20190612111900.2crgsg4adinrrw5u@ninjato \
--to=wsa@the-dreams.de \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=xu_shunji@hoperun.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