From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
"open list:BAREBOX" <barebox@lists.infradead.org>
Subject: Re: [PATCH 4/9] mci: add RPMB support
Date: Mon, 17 Mar 2025 16:18:32 +0100 [thread overview]
Message-ID: <9c66b31b-a79c-4a07-a03f-119c7c3dadc7@pengutronix.de> (raw)
In-Reply-To: <20250312-rpmb-v1-4-0f213382a3f3@pengutronix.de>
Hello Sascha,
On 3/12/25 13:16, Sascha Hauer wrote:
> +
> +int mci_rpmb_route_frames(struct mci *mci, void *req, unsigned long reqlen,
> + void *rsp, unsigned long rsplen)
> +{
> + /*
> + * Whoever crafted the data supplied to this function knows how to
> + * format the PRMB frames and which response is expected. If
> + * there's some unexpected mismatch it's more helpful to report an
> + * error immediately than trying to guess what was the intention
> + * and possibly just delay an eventual error which will be harder
> + * to track down.
> + */
> + void *rpmb_data = NULL;
> + int ret;
> +
> + mci_blk_part_switch(mci->rpmb_part);
> +
> + if (!IS_ALIGNED((uintptr_t)req, ARCH_DMA_MINALIGN)) {
Even if alignment happens to be correct, there is no guarantee that
there is no other data sharing a cache line.
Let's just return an error for the unaligned case instead and expect
users to align the request.
Thanks,
Ahmad
> + /* Memory alignment is required by MMC driver */
> + rpmb_data = dma_alloc(reqlen);
> + if (!rpmb_data)
> + return -ENOMEM;
> +
> + memcpy(rpmb_data, req, reqlen);
> + req = rpmb_data;
> + }
> +
> + ret = rpmb_route_frames(mci, req, reqlen, rsp, rsplen);
> +
> + free(rpmb_data);
> +
> + return ret;
> +}
> diff --git a/include/mci.h b/include/mci.h
> index 08a3e46f7d..ec0390eedf 100644
> --- a/include/mci.h
> +++ b/include/mci.h
> @@ -736,6 +736,9 @@ int mmc_select_timing(struct mci *mci);
> int mci_set_blockcount(struct mci *mci, unsigned int cmdarg);
> int mci_blk_part_switch(struct mci_part *part);
> int mci_send_cmd(struct mci *mci, struct mci_cmd *cmd, struct mci_data *data);
> +struct mci *mci_get_rpmb_dev(void);
> +int mci_rpmb_route_frames(struct mci *mci, void *req, unsigned long reqlen,
> + void *rsp, unsigned long rsplen);
>
> static inline bool mmc_card_hs200(struct mci *mci)
> {
>
next prev parent reply other threads:[~2025-03-17 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 12:16 [PATCH 0/9] Add " Sascha Hauer
2025-03-12 12:16 ` [PATCH 1/9] mci: implement mci_set_blockcount() Sascha Hauer
2025-03-12 12:16 ` [PATCH 2/9] mci: export some functions for RPMB support Sascha Hauer
2025-03-12 12:16 ` [PATCH 3/9] mci: detect RPMB partitions Sascha Hauer
2025-03-12 12:16 ` [PATCH 4/9] mci: add RPMB support Sascha Hauer
2025-03-17 15:18 ` Ahmad Fatoum [this message]
2025-03-12 12:16 ` [PATCH 5/9] tee: optee: probe successfully even when no devices are found Sascha Hauer
2025-03-12 12:16 ` [PATCH 6/9] tee: optee: implement shared mem alloc/free RPC commands Sascha Hauer
2025-03-12 12:16 ` [PATCH 7/9] tee: optee: implement RPMB support Sascha Hauer
2025-03-12 12:16 ` [PATCH 8/9] tee: optee: implement AVB named persistent values support Sascha Hauer
2025-03-12 12:16 ` [PATCH 9/9] commands: add avb_pvalue command Sascha Hauer
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=9c66b31b-a79c-4a07-a03f-119c7c3dadc7@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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