From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
patchwork-bot+notify@kernel.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH 0/6] arm64: dts: meson: mmc clean-up
Date: Fri, 03 May 2019 15:04:27 -0700 [thread overview]
Message-ID: <7hh8abkxec.fsf@baylibre.com> (raw)
In-Reply-To: <20190418122714.30805-1-jbrunet@baylibre.com>
Jerome Brunet <jbrunet@baylibre.com> writes:
> The patchset is bunch of clean-up found while debugging meson mmc.
>
> * The first 2 patches address the libretech-cc which actually uses 1.8v
> eMMC modules.
> * Patch 3 is a pin bias fixup depending on mmc pins.
> * Patch 4 lower the mmc max frequencies on gx chips. It was not easy
> to spot but, according to the datasheet, the maximum UHS rate
> supported by these chips is 100MHz (SDR50). This explains why we
> never really managed to get a stable SDR104. SDIO is limited to HS.
> * Patch 5 adds missing pinctrl definition on the vim2
> * Patch 6 remove hs400 from the supported modes of the vim2. This mode is
> mode reliable enough with HW/SW ATM.
Queued for v5.3 (branch: v5.3/dt64)
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
patchwork-bot+notify@kernel.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH 0/6] arm64: dts: meson: mmc clean-up
Date: Fri, 03 May 2019 15:04:27 -0700 [thread overview]
Message-ID: <7hh8abkxec.fsf@baylibre.com> (raw)
In-Reply-To: <20190418122714.30805-1-jbrunet@baylibre.com>
Jerome Brunet <jbrunet@baylibre.com> writes:
> The patchset is bunch of clean-up found while debugging meson mmc.
>
> * The first 2 patches address the libretech-cc which actually uses 1.8v
> eMMC modules.
> * Patch 3 is a pin bias fixup depending on mmc pins.
> * Patch 4 lower the mmc max frequencies on gx chips. It was not easy
> to spot but, according to the datasheet, the maximum UHS rate
> supported by these chips is 100MHz (SDR50). This explains why we
> never really managed to get a stable SDR104. SDIO is limited to HS.
> * Patch 5 adds missing pinctrl definition on the vim2
> * Patch 6 remove hs400 from the supported modes of the vim2. This mode is
> mode reliable enough with HW/SW ATM.
Queued for v5.3 (branch: v5.3/dt64)
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, patchwork-bot+notify@kernel.org
Subject: Re: [PATCH 0/6] arm64: dts: meson: mmc clean-up
Date: Fri, 03 May 2019 15:04:27 -0700 [thread overview]
Message-ID: <7hh8abkxec.fsf@baylibre.com> (raw)
In-Reply-To: <20190418122714.30805-1-jbrunet@baylibre.com>
Jerome Brunet <jbrunet@baylibre.com> writes:
> The patchset is bunch of clean-up found while debugging meson mmc.
>
> * The first 2 patches address the libretech-cc which actually uses 1.8v
> eMMC modules.
> * Patch 3 is a pin bias fixup depending on mmc pins.
> * Patch 4 lower the mmc max frequencies on gx chips. It was not easy
> to spot but, according to the datasheet, the maximum UHS rate
> supported by these chips is 100MHz (SDR50). This explains why we
> never really managed to get a stable SDR104. SDIO is limited to HS.
> * Patch 5 adds missing pinctrl definition on the vim2
> * Patch 6 remove hs400 from the supported modes of the vim2. This mode is
> mode reliable enough with HW/SW ATM.
Queued for v5.3 (branch: v5.3/dt64)
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
devicetree@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, patchwork-bot+notify@kernel.org
Subject: Re: [PATCH 0/6] arm64: dts: meson: mmc clean-up
Date: Fri, 03 May 2019 15:04:27 -0700 [thread overview]
Message-ID: <7hh8abkxec.fsf@baylibre.com> (raw)
In-Reply-To: <20190418122714.30805-1-jbrunet@baylibre.com>
Jerome Brunet <jbrunet@baylibre.com> writes:
> The patchset is bunch of clean-up found while debugging meson mmc.
>
> * The first 2 patches address the libretech-cc which actually uses 1.8v
> eMMC modules.
> * Patch 3 is a pin bias fixup depending on mmc pins.
> * Patch 4 lower the mmc max frequencies on gx chips. It was not easy
> to spot but, according to the datasheet, the maximum UHS rate
> supported by these chips is 100MHz (SDR50). This explains why we
> never really managed to get a stable SDR104. SDIO is limited to HS.
> * Patch 5 adds missing pinctrl definition on the vim2
> * Patch 6 remove hs400 from the supported modes of the vim2. This mode is
> mode reliable enough with HW/SW ATM.
Queued for v5.3 (branch: v5.3/dt64)
Kevin
next prev parent reply other threads:[~2019-05-03 22:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 12:27 [PATCH 0/6] arm64: dts: meson: mmc clean-up Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` [PATCH 1/6] arm64: dts: meson: libretech-cc: set eMMC as removable Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 20:21 ` Martin Blumenstingl
2019-04-18 20:21 ` Martin Blumenstingl
2019-04-18 20:21 ` Martin Blumenstingl
2019-04-18 12:27 ` [PATCH 2/6] arm64: dts: meson: libretech-cc: switch eMMC to 1.8v Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 19:46 ` Martin Blumenstingl
2019-04-18 19:46 ` Martin Blumenstingl
2019-04-18 19:46 ` Martin Blumenstingl
2019-04-18 12:27 ` [PATCH 3/6] arm64: dts: meson: fix mmc pin bias Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` [PATCH 4/6] arm64: dts: meson: fix mmc v2 chips max frequencies Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` [PATCH 5/6] arm64: dts: meson: vim2: add missing clk-gate pinctrl Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 20:21 ` Martin Blumenstingl
2019-04-18 20:21 ` Martin Blumenstingl
2019-04-18 20:21 ` Martin Blumenstingl
2019-04-18 12:27 ` [PATCH 6/6] arm64: dts: meson: vim2: remove sd hs and hs400 modes from emmc Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-04-18 12:27 ` Jerome Brunet
2019-05-03 22:04 ` Kevin Hilman [this message]
2019-05-03 22:04 ` [PATCH 0/6] arm64: dts: meson: mmc clean-up Kevin Hilman
2019-05-03 22:04 ` Kevin Hilman
2019-05-03 22:04 ` Kevin Hilman
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=7hh8abkxec.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+notify@kernel.org \
/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.