All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>
To: Christian Loehle <christian.loehle@arm.com>
Cc: Jorge Ramirez-Ortiz <jorge@foundries.io>,
	Avri.Altman@wdc.com, adrian.hunter@intel.com,
	ulf.hansson@linaro.org, linux-kernel@vger.kernel.org,
	linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: rpmb: do not force a retune before RPMB switch
Date: Mon, 4 Dec 2023 19:10:05 +0100	[thread overview]
Message-ID: <ZW4V/XzXY114l5/a@trax> (raw)
In-Reply-To: <9747ebb3-98e6-47da-8a9b-9b7dcf7909f6@arm.com>

On 04/12/23 17:52:24, Christian Loehle wrote:
> On 04/12/2023 17:22, Jorge Ramirez-Ortiz wrote:
> > Requesting a retune before switching to the RPMB partition has been
> > observed to cause CRC errors on the RPMB reads (-EILSEQ).
> >
> > Since RPMB reads can not be retried, the clients would be directly
> > affected by the errors.
> >
> > This commit disables the request prior to RPMB switching while allowing
> > the pause interface to still request a retune before the pause for other
> > use cases.
> >
> > This was verified with the sdhci-of-arasan driver (ZynqMP) configured
> > for HS200 using two separate eMMC cards (DG4064 and 064GB2). In both
> > cases, the error was easy to reproduce triggering every few tenths of
> > reads.
> >
> > Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io>
> > Acked-by: Avri Altman <avri.altman@wdc.com>
>
> Is the difference between this mail and the previous one just Avri's Ack?
> No need to resend for every tag you receive.

oops, every project with its own little idiosyncrasies sometimes I get
confused (u-boot, optee, ssl, tf-a..) yes, sorry about it, no differences.

  reply	other threads:[~2023-12-04 18:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 17:22 [PATCH] mmc: rpmb: do not force a retune before RPMB switch Jorge Ramirez-Ortiz
2023-12-04 17:52 ` Christian Loehle
2023-12-04 18:10   ` Jorge Ramirez-Ortiz, Foundries [this message]
2023-12-11 16:17 ` Adrian Hunter
  -- strict thread matches above, loose matches on Subject: below --
2023-12-11 16:55 Jorge Ramirez-Ortiz
2024-01-03  8:08 ` Adrian Hunter
2024-01-03 10:35 ` Ulf Hansson
2023-12-04 15:01 Jorge Ramirez-Ortiz
2023-12-04 16:22 ` Avri Altman
2023-12-04 17:58 ` Avri Altman
2023-12-04 18:14   ` Jorge Ramirez-Ortiz, Foundries
2023-12-05 16:10     ` Jorge Ramirez-Ortiz, Foundries
2023-12-05 20:12 ` Adrian Hunter
2023-12-05 20:14   ` Adrian Hunter
2023-12-06  7:02   ` Avri Altman
2023-12-06 10:00     ` Jorge Ramirez-Ortiz, Foundries
2023-12-11  8:00       ` Jorge Ramirez-Ortiz, Foundries
2023-12-11 10:25         ` Adrian Hunter
2023-12-11 11:06           ` Jorge Ramirez-Ortiz, Foundries
2023-12-11 11:32             ` Adrian Hunter
2023-12-11 15:05               ` Jorge Ramirez-Ortiz, Foundries
2023-12-14  9:15                 ` Adrian Hunter
2023-12-14 11:16                   ` Jorge Ramirez-Ortiz, Foundries
2024-01-02 10:41         ` Jorge Ramirez-Ortiz, Foundries
2024-01-02 19:01           ` Adrian Hunter
2024-01-02 22:01             ` Jorge Ramirez-Ortiz, Foundries
2024-01-03  8:03               ` Adrian Hunter
2024-01-03  9:20                 ` Jorge Ramirez-Ortiz, Foundries
2024-01-04 18:34                   ` Adrian Hunter
2024-01-05  8:49                     ` Jorge Ramirez-Ortiz, Foundries
2024-01-05 13:00                       ` Michal Simek
2023-12-11  8:03     ` Adrian Hunter
2024-01-02 19:02 ` Adrian Hunter
2024-01-03  8:08   ` Adrian Hunter

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=ZW4V/XzXY114l5/a@trax \
    --to=jorge@foundries.io \
    --cc=Avri.Altman@wdc.com \
    --cc=adrian.hunter@intel.com \
    --cc=christian.loehle@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --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.