From: Chen-Yu Tsai <wens@csie.org> To: "André Przywara" <andre.przywara@arm.com> Cc: Maxime Ripard <mripard@kernel.org>, Rob Herring <robh@kernel.org>, Jernej Skrabec <jernej.skrabec@siol.net>, Icenowy Zheng <icenowy@aosc.io>, devicetree <devicetree@vger.kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, linux-sunxi <linux-sunxi@googlegroups.com> Subject: Re: [linux-sunxi] [PATCH 4/7] arm64: dts: allwinner: H6: Allow up to 150 MHz MMC bus frequency Date: Thu, 7 Jan 2021 00:01:42 +0800 [thread overview] Message-ID: <CAGb2v64NM9iyYG1x1gvBZ8biwTG-=p1a=WPidyX17sjZTVjt6Q@mail.gmail.com> (raw) In-Reply-To: <20210106150525.15403-5-andre.przywara@arm.com> On Wed, Jan 6, 2021 at 11:06 PM Andre Przywara <andre.przywara@arm.com> wrote: > > The H6 manual explicitly lists a frequency limit of 150 MHz for the bus > frequency of the MMC controllers. So far we had no explicit limits in the > DT, which limited eMMC to a rather conservative 52 MHz. I'd say this is implementation specific. FreeBSD might have other defaults? > Put those maximum frequencies in the SoC .dtsi, to allow higher speed > modes (which still would need to be explicitly enabled, per board). > > Tested with an eMMC using HS-200 on a Pine H64. Running at the spec'ed > 200 MHz indeed fails with I/O errors, but 150 MHz seems to work stably. > > Signed-off-by: Andre Przywara <andre.przywara@arm.com> Fixes tag? Thanks ChenYu
WARNING: multiple messages have this Message-ID (diff)
From: Chen-Yu Tsai <wens@csie.org> To: "André Przywara" <andre.przywara@arm.com> Cc: devicetree <devicetree@vger.kernel.org>, Jernej Skrabec <jernej.skrabec@siol.net>, Maxime Ripard <mripard@kernel.org>, linux-sunxi <linux-sunxi@googlegroups.com>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, Icenowy Zheng <icenowy@aosc.io> Subject: Re: [linux-sunxi] [PATCH 4/7] arm64: dts: allwinner: H6: Allow up to 150 MHz MMC bus frequency Date: Thu, 7 Jan 2021 00:01:42 +0800 [thread overview] Message-ID: <CAGb2v64NM9iyYG1x1gvBZ8biwTG-=p1a=WPidyX17sjZTVjt6Q@mail.gmail.com> (raw) In-Reply-To: <20210106150525.15403-5-andre.przywara@arm.com> On Wed, Jan 6, 2021 at 11:06 PM Andre Przywara <andre.przywara@arm.com> wrote: > > The H6 manual explicitly lists a frequency limit of 150 MHz for the bus > frequency of the MMC controllers. So far we had no explicit limits in the > DT, which limited eMMC to a rather conservative 52 MHz. I'd say this is implementation specific. FreeBSD might have other defaults? > Put those maximum frequencies in the SoC .dtsi, to allow higher speed > modes (which still would need to be explicitly enabled, per board). > > Tested with an eMMC using HS-200 on a Pine H64. Running at the spec'ed > 200 MHz indeed fails with I/O errors, but 150 MHz seems to work stably. > > Signed-off-by: Andre Przywara <andre.przywara@arm.com> Fixes tag? Thanks ChenYu _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-06 16:03 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-06 15:05 [PATCH 0/7] arm64: dts: allwinner: Various DT fixes Andre Przywara 2021-01-06 15:05 ` Andre Przywara 2021-01-06 15:05 ` [PATCH 1/7] arm64: dts: allwinner: H6/A64: properly connect USB PHY to port 0 Andre Przywara 2021-01-06 15:05 ` Andre Przywara 2021-01-06 15:56 ` [linux-sunxi] " Chen-Yu Tsai 2021-01-06 15:56 ` Chen-Yu Tsai 2021-01-13 10:30 ` André Przywara 2021-01-13 10:30 ` André Przywara 2021-01-13 10:43 ` Chen-Yu Tsai 2021-01-13 10:43 ` Chen-Yu Tsai 2021-01-06 15:05 ` [PATCH 2/7] arm64: dts: allwinner: Pine64-LTS: Add status LED Andre Przywara 2021-01-06 15:05 ` Andre Przywara 2021-01-06 15:53 ` [linux-sunxi] " Chen-Yu Tsai 2021-01-06 15:53 ` Chen-Yu Tsai 2021-01-06 16:08 ` André Przywara 2021-01-06 16:08 ` André Przywara 2021-01-13 14:02 ` Emmanuel Vadot 2021-01-13 14:02 ` Emmanuel Vadot 2021-01-06 16:01 ` Maxime Ripard 2021-01-06 16:01 ` Maxime Ripard 2021-01-06 15:05 ` [PATCH 3/7] arm64: dts: allwinner: Drop non-removable from SoPine/LTS SD card Andre Przywara 2021-01-06 15:05 ` Andre Przywara 2021-01-06 15:57 ` [linux-sunxi] " Chen-Yu Tsai 2021-01-06 15:57 ` Chen-Yu Tsai 2021-01-06 15:05 ` [PATCH 4/7] arm64: dts: allwinner: H6: Allow up to 150 MHz MMC bus frequency Andre Przywara 2021-01-06 15:05 ` Andre Przywara 2021-01-06 16:01 ` Chen-Yu Tsai [this message] 2021-01-06 16:01 ` [linux-sunxi] " Chen-Yu Tsai 2021-01-06 15:05 ` [PATCH 5/7] arm64: dts: allwinner: A64: Limit MMC2 bus frequency to 150 MHz Andre Przywara 2021-01-06 15:05 ` Andre Przywara 2021-01-06 15:58 ` [linux-sunxi] " Chen-Yu Tsai 2021-01-06 15:58 ` Chen-Yu Tsai 2021-01-06 15:05 ` [PATCH 6/7] arm64: dts: allwinner: Pine64-LTS/SoPine: Enable HS200 eMMC mode Andre Przywara 2021-01-06 15:05 ` Andre Przywara 2021-01-06 15:59 ` [linux-sunxi] " Chen-Yu Tsai 2021-01-06 15:59 ` Chen-Yu Tsai 2021-01-06 15:05 ` [PATCH 7/7] arm64: dts: allwinner: Pine H64: " Andre Przywara 2021-01-06 15:05 ` Andre Przywara 2021-01-06 16:00 ` [linux-sunxi] " Chen-Yu Tsai 2021-01-06 16:00 ` Chen-Yu Tsai
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='CAGb2v64NM9iyYG1x1gvBZ8biwTG-=p1a=WPidyX17sjZTVjt6Q@mail.gmail.com' \ --to=wens@csie.org \ --cc=andre.przywara@arm.com \ --cc=devicetree@vger.kernel.org \ --cc=icenowy@aosc.io \ --cc=jernej.skrabec@siol.net \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-sunxi@googlegroups.com \ --cc=mripard@kernel.org \ --cc=robh@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: linkBe 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.