The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Aswath Govindraju <a-govindraju@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] mmc: J7200: Add support for higher speed modes in MMCSD subsystems
Date: Mon, 25 Jan 2021 19:43:22 +0530	[thread overview]
Message-ID: <fd7ac744-a6dc-9f1f-c13f-96faca14d75b@ti.com> (raw)
In-Reply-To: <20210125135112.gvddr4uv7vx7kfrq@triangle>

Hi Nishanth,

On 25/01/21 7:21 pm, Nishanth Menon wrote:
> On 19:12-20210125, Aswath Govindraju wrote:
>> Hi Nishanth,
>>
>> On 22/01/21 11:36 pm, Nishanth Menon wrote:
>>> On 21:54-20210122, Aswath Govindraju wrote:
>>>> The following series of patches
>>>> - adds support for HS200 and HS400 speed modes in MMCSD0 subsystem
>>>> - adds support for UHS-I speed modes in MMCSD1 subsystem 
>>>>
>>>> Aswath Govindraju (2):
>>>>   arm64: dts: ti: k3-j7200-main: Add support for HS200 and HS400 modes
>>>>     in MMCSD0 subsystem
>>>>   arm64: dts: ti: k3-j7200-main: Add support for UHS-I modes in MMCSD1
>>>>     subsystem
>>>
>>>
>>> Just a curious couple of questions:
>>> Does squashing both the patches create a problem for understanding or a
>>> later bisect? I kind of thought these mostly go hand in hand between the
>>> instances, am I mistaken?
>>>
>>
>> Yes, they can be squashed. I post a respin doing this.
> 
> Thanks.
> 
>>
>>> Are there any otap delay params update needed or the defaults are good
>>> to go?
>>>
>>
>> The otap values are already up-to-date with the data sheet and don't
>> need updation.
> 
> Thanks for the clarification.
> 
>>
>>> Will also help to provide some verification log along with this.
>>>
>>
>> May I know what sort of logs would be best to provide. Would enumeration
>> logs during boot suffice ?
>>
>> Like this,
>> https://pastebin.ubuntu.com/p/v9NRV7GwMw/ ?
> 
> That just says we detected the cards, no?
> I thought we had tests around this? Something including /sys/kernel/debug/mmc*/ios
> 
> Something that demonstrates that this actually runs at the claimed
> speeds? That would be nice on linux-next, if possible as well..
> 

Yes there are tests which confirm that claimed speeds are functional. I
will add them in the respin.

Thanks,
Aswath

  reply	other threads:[~2021-01-25 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 16:24 [PATCH 0/2] mmc: J7200: Add support for higher speed modes in MMCSD subsystems Aswath Govindraju
2021-01-22 16:24 ` [PATCH 1/2] arm64: dts: ti: k3-j7200-main: Add support for HS200 and HS400 modes in MMCSD0 subsystem Aswath Govindraju
2021-01-22 16:24 ` [PATCH 2/2] arm64: dts: ti: k3-j7200-main: Add support for UHS-I modes in MMCSD1 subsystem Aswath Govindraju
2021-01-22 18:06 ` [PATCH 0/2] mmc: J7200: Add support for higher speed modes in MMCSD subsystems Nishanth Menon
2021-01-25 13:42   ` Aswath Govindraju
2021-01-25 13:51     ` Nishanth Menon
2021-01-25 14:13       ` Aswath Govindraju [this message]
2021-01-25 14:18         ` Nishanth Menon

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=fd7ac744-a6dc-9f1f-c13f-96faca14d75b@ti.com \
    --to=a-govindraju@ti.com \
    --cc=devicetree@vger.kernel.org \
    --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=nm@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