From: Eric Biggers <ebiggers@kernel.org>
To: Seshu Madhavi Puppala <quic_spuppala@quicinc.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, quic_rampraka@quicinc.com,
quic_nitirawa@quicinc.com, quic_sachgupt@quicinc.com,
quic_bhaskarv@quicinc.com, quic_neersoni@quicinc.com,
quic_gaurkash@quicinc.com
Subject: Re: [PATCH RFC 0/2] Avoid reprogram all keys to Inline Crypto Engine for MMC runtime suspend resume
Date: Wed, 23 Oct 2024 21:31:34 +0000 [thread overview]
Message-ID: <20241023213134.GC3736641@google.com> (raw)
In-Reply-To: <20241006135530.17363-1-quic_spuppala@quicinc.com>
On Sun, Oct 06, 2024 at 07:25:28PM +0530, Seshu Madhavi Puppala wrote:
> Crypto reprogram all keys is called for each MMC runtime
> suspend/resume in current upstream design.
Is that correct? I thought that similar to what is done for UFS, the key
reprogramming happens only after the MMC controller is reset. I thought that is
different from a runtime suspend.
If it's in fact triggering more often, maybe that is what needs to be fixed?
- Eric
next prev parent reply other threads:[~2024-10-23 21:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 13:55 [PATCH RFC 0/2] Avoid reprogram all keys to Inline Crypto Engine for MMC runtime suspend resume Seshu Madhavi Puppala
2024-10-06 13:55 ` [PATCH RFC v3 1/2] mmc: core: Add vendor hook to control reprogram keys to Crypto Engine Seshu Madhavi Puppala
2024-10-08 14:00 ` Ulf Hansson
2024-10-19 4:55 ` Seshu Madhavi Puppala
2024-10-22 12:27 ` Ulf Hansson
2024-10-23 8:59 ` Adrian Hunter
2024-10-23 21:28 ` Eric Biggers
2024-10-24 22:47 ` Ulf Hansson
2024-11-21 5:16 ` Seshu Madhavi Puppala
2024-10-06 13:55 ` [PATCH RFC v3 2/2] mmc: host: sdhci-msm: Avoid reprogram keys for QCOM socs Seshu Madhavi Puppala
2024-10-23 21:31 ` Eric Biggers [this message]
2024-10-24 23:07 ` [PATCH RFC 0/2] Avoid reprogram all keys to Inline Crypto Engine for MMC runtime suspend resume Ulf Hansson
2024-10-25 2:56 ` Eric Biggers
2024-10-25 8:42 ` Ulf Hansson
2024-11-21 5:16 ` Seshu Madhavi Puppala
2024-11-21 11:03 ` Ulf Hansson
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=20241023213134.GC3736641@google.com \
--to=ebiggers@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=quic_bhaskarv@quicinc.com \
--cc=quic_gaurkash@quicinc.com \
--cc=quic_neersoni@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_rampraka@quicinc.com \
--cc=quic_sachgupt@quicinc.com \
--cc=quic_spuppala@quicinc.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.