From: Greg KH <gregkh@linuxfoundation.org>
To: Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: adrian.hunter@intel.com, ulf.hansson@linaro.org,
baolin.wang@linaro.org, kstewart@linuxfoundation.org,
tglx@linutronix.de, bradleybolen@gmail.com, faiz_abbas@ti.com,
thierry.reding@gmail.com, jonathanh@nvidia.com,
bbiswas@nvidia.com, anrao@nvidia.com,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 4.19.113 0/3] Fix for long operation cmds busy detection
Date: Sun, 19 Apr 2020 18:52:04 +0200 [thread overview]
Message-ID: <20200419165204.GA3697430@kroah.com> (raw)
In-Reply-To: <6911ee08-1376-a515-9393-1ebc6cc6a255@nvidia.com>
On Sun, Apr 19, 2020 at 09:23:39AM -0700, Sowjanya Komatineni wrote:
>
> On 4/19/20 12:20 AM, Greg KH wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > On Fri, Apr 17, 2020 at 12:14:01PM -0700, Sowjanya Komatineni wrote:
> > > This series includes manually backported changes that implements Tegra
> > > specific timeout callback to switch between finite and infinite HW busy
> > > detection wait modes.
> > >
> > > sdhci-tegra driver patch implements set_timeout callback based on one of
> > > the sdhci host driver patch that refactors sdhci_set_timeout and allows
> > > drivers to call __sdhci_set_timeout with their timeout callback
> > > implementation.
> > >
> > > Both of these patches are manually backported in this series.
> > Is this a bugfix or a new feature? I can't tell, but it feels like it's
> > a new feature. What's wrong with just using the 5.4.y kernel tree?
> >
> > thanks,
> >
> > greg k-h
> Ulf recent patches for increased timeout adds capability
> MMC_CAP_NEED_RSP_BUSY for sdhci-tegra as well.
>
> So, it will always use R1B for R1B type commands so there are no known bugs
> or failures with mmc devices we use on our platforms.
I have no idea what this means, sorry.
> So, we can treat this patch as an improvement for long operation commands
> where HW will wait as long as device is busy.
Ok, so this isn't a regression and can't match the stable kernel rules,
sorry.
greg k-h
next prev parent reply other threads:[~2020-04-19 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 19:14 [PATCH 4.19.113 0/3] Fix for long operation cmds busy detection Sowjanya Komatineni
2020-04-17 19:14 ` Sowjanya Komatineni
2020-04-17 19:14 ` [PATCH 4.19.113 1/3] mmc: sdhci: Refactor sdhci_set_timeout() Sowjanya Komatineni
2020-04-17 19:14 ` Sowjanya Komatineni
2020-04-17 19:14 ` [PATCH 4.19.113 2/3] sdhci: tegra: Implement Tegra specific set_timeout callback Sowjanya Komatineni
2020-04-17 19:14 ` Sowjanya Komatineni
2020-04-17 19:14 ` [PATCH 4.19.113 3/3] sdhci: tegra: Enable MMC_CAP_WAIT_WHILE_BUSY host capability Sowjanya Komatineni
2020-04-17 19:14 ` Sowjanya Komatineni
2020-04-19 7:20 ` [PATCH 4.19.113 0/3] Fix for long operation cmds busy detection Greg KH
2020-04-19 7:20 ` Greg KH
2020-04-19 16:23 ` Sowjanya Komatineni
2020-04-19 16:23 ` Sowjanya Komatineni
2020-04-19 16:52 ` Greg KH [this message]
2020-04-20 7:01 ` Ulf Hansson
2020-04-21 17:04 ` Sowjanya Komatineni
2020-04-21 17:04 ` Sowjanya Komatineni
-- strict thread matches above, loose matches on Subject: below --
2020-04-24 20:06 Sowjanya Komatineni
2020-04-24 20:06 ` Sowjanya Komatineni
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=20200419165204.GA3697430@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adrian.hunter@intel.com \
--cc=anrao@nvidia.com \
--cc=baolin.wang@linaro.org \
--cc=bbiswas@nvidia.com \
--cc=bradleybolen@gmail.com \
--cc=faiz_abbas@ti.com \
--cc=jonathanh@nvidia.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=skomatineni@nvidia.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.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.