From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Bo Ye <bo.ye@mediatek.com>,
avri.altman@wdc.com, dominique.martinet@atmark-techno.com,
rafael.beims@toradex.com, vincent.whitchurch@axis.com,
Ulf Hansson <ulf.hansson@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: yongdong.zhang@mediatek.com, "lin.gui" <lin.gui@mediatek.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2] mmc: add wp_grp_size node
Date: Tue, 19 Dec 2023 11:55:30 +0100 [thread overview]
Message-ID: <716db737-940a-4a28-bd54-b1dce76174d2@collabora.com> (raw)
In-Reply-To: <20231218230532.82427-1-bo.ye@mediatek.com>
Il 19/12/23 00:05, Bo Ye ha scritto:
> From: "lin.gui" <lin.gui@mediatek.com>
>
> Detail:
> Add node "wp_grp_size", corresponding to WP_GRP_SIZE
> (write protect group size) of eMMC's CSD register.
>
> Scenario:
> The eMMC card can be set into write-protected mode to
> prevent data from being accidentally modified or deleted.
> Wp_grp_size (Write Protect Group Size) refers to an
> attribute of the eMMC card, used to manage write protection,
> and is the CSD register [36:32] of the eMMC device.
> Wp_grp_size (Write Protect Group Size) indicates how many
> eMMC blocks are contained in each write protection group on the eMMC card.
>
> Final rendered file:
> "/sys/class/mmc_host/mmc0/mmc0:0001/wp_grp_size"
>
> Signed-off-by: Lin Gui <lin.gui@mediatek.com>
> Signed-off-by: Bo Ye <bo.ye@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2023-12-19 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 22:48 [PATCH v2] mmc: add wp_grp_size node Bo Ye
2023-12-18 23:05 ` Bo Ye
2023-12-19 10:55 ` AngeloGioacchino Del Regno [this message]
2024-01-02 16:57 ` 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=716db737-940a-4a28-bd54-b1dce76174d2@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.com \
--cc=bo.ye@mediatek.com \
--cc=dominique.martinet@atmark-techno.com \
--cc=lin.gui@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rafael.beims@toradex.com \
--cc=ulf.hansson@linaro.org \
--cc=vincent.whitchurch@axis.com \
--cc=yongdong.zhang@mediatek.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