From: Nishanth Menon <nm@ti.com>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: devicetree@vger.kernel.org, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
Lokesh Vutla <lokeshvutla@ti.com>,
linux-kernel@vger.kernel.org, Faiz Abbas <faiz_abbas@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/2] arm64: dts: ti: k3-j7200: Add support for higher speed modes in MMCSD subsystems
Date: Wed, 27 Jan 2021 09:54:52 -0600 [thread overview]
Message-ID: <20210127155452.27unsnisenm42nb4@budding> (raw)
In-Reply-To: <6f9ddf85-e1e9-426a-2436-7f323314959a@ti.com>
On 20:50-20210127, Aswath Govindraju wrote:
> Hi Nishanth,
>
> On 27/01/21 8:44 pm, Nishanth Menon wrote:
> > On 20:38-20210127, Aswath Govindraju wrote:
> >> The following speed modes are now supported in J7200 SoC,
> >> - HS200 and HS400 modes at 1.8 V card voltage, in MMCSD0 subsystem [1].
> >> - UHS-I speed modes in MMCSD1 subsystem [1].
> >>
> >> Add support for UHS-I modes by adding voltage regulator device tree nodes
> >> and corresponding pinmux details, to power cycle and voltage switch cards.
> >> Also set respective tags in sdhci0 and remove no-1-8-v tag from sdhci1
> >> device tree nodes.
> >>
> >> [1] - section 12.3.6.1.1 MMCSD Features, in
> >> https://www.ti.com/lit/ug/spruiu1a/spruiu1a.pdf
> >>
> >> Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
> >> ---
> >>
> >> performance test logs using EXT4 filesystem for eMMC HS400 speed mode,
> >> https://pastebin.ubuntu.com/p/KFphDYXj93/
> >>
> >
> > 5.11.0-rc3-next-20210118-00004 :
> >
> > a) could you make sure to post patches when you test with latest next?
> > b) I see 2 patches in this series, but delta seems to be 4 patches, is
> > there a dependency I am not aware of?
> >
>
> There are no dependencies. The other two commits are completely
> unrelated. From next time I will make sure that I use the latest next
> and the delta matches.
Thanks.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-01-27 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 15:08 [PATCH v3 0/2] J7200: Add support for higher speed modes in MMCSD subsystems Aswath Govindraju
2021-01-27 15:08 ` [PATCH v3 1/2] dts: ti: k3-j7200-main: Add support for zeroth instance of GPIO subsystem Aswath Govindraju
2021-01-27 15:12 ` Nishanth Menon
2021-01-27 15:26 ` Aswath Govindraju
2021-01-27 15:54 ` Nishanth Menon
2021-01-28 16:21 ` Aswath Govindraju
2021-01-27 15:08 ` [PATCH v3 2/2] arm64: dts: ti: k3-j7200: Add support for higher speed modes in MMCSD subsystems Aswath Govindraju
2021-01-27 15:14 ` Nishanth Menon
2021-01-27 15:20 ` Aswath Govindraju
2021-01-27 15:54 ` Nishanth Menon [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=20210127155452.27unsnisenm42nb4@budding \
--to=nm@ti.com \
--cc=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=kishon@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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