[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYyYAaW8AYqpC3E7eBx25-3yJqitSE=0yVfxCDtM-CwqA@mail.gmail.com>
Date: Wed, 13 Nov 2019 00:11:11 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Rob Herring <robh@...nel.org>,
Eugeniu Rosca <erosca@...adit-jv.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
linux-mmc <linux-mmc@...r.kernel.org>,
Mathieu Malaterre <malat@...ian.org>,
Pavel Machek <pavel@....cz>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Eugeniu Rosca <roscaeugeniu@...il.com>
Subject: Re: [PATCH 1/3] dt-bindings: mmc: Add 'fixed-emmc-driver-type-hs{200,400}'
On Tue, Nov 12, 2019 at 10:19 PM Wolfram Sang <wsa@...-dreams.de> wrote:
> What I have seen so far: setting drive strength alone is more on the
> rare side. Setting specific values for default and HS200/400 seems even
> more rare to me. With this patchset, it is the first time I hear about
> it.
Like I wrote to Eugeniu this sounds like some kind of errata
for the eMMC ext CSD and should likely be a card quirk rather
than some generic device tree properties.
I might be wrong, we'll hash it out.
Yours,
Linus Walleij
Powered by blists - more mailing lists