On Thu, May 23, 2024 at 06:41:04AM +0000, Lin Gui (桂林) wrote:
> Dear @Greg KH<mailto:gregkh@linuxfoundation.org>,
>
>
> What is the git id of it in Linus's tree?
> [MTK]
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/d…
>
>
> author Mengqi Zhang <mengqi.zhang(a)mediatek.com> 2023-12-25 17:38:40 +0800
> committer Ulf Hansson <ulf.hansson(a)linaro.org> 2024-01-02 17:54:05 +0100
> commit 77e01b49e35f24ebd1659096d5fc5c3b75975545 (patch)
> tree 02a13063666685bc7061b46183fc45298b2dc9f4 /drivers/mmc/core/mmc.c
> parent 09f164d393a6671e5ff8342ba6b3cb7fe3f20208 (diff)
> download linux-77e01b49e35f24ebd1659096d5fc5c3b75975545.tar.gz
> mmc: core: Add HS400 tuning in HS400es initialization
> During the initialization to HS400es stage, add a HS400 tuning flow as an
> optional process. For Mediatek IP, the HS400es mode requires a specific
> tuning to ensure the correct HS400 timing setting.
>
> Signed-off-by: Mengqi Zhang <mengqi.zhang(a)mediatek.com>
> Link: https://lore.kernel.org/r/20231225093839.22931-2-mengqi.zhang@mediatek.com
> Signed-off-by: Ulf Hansson ulf.hansson(a)linaro.org<mailto:ulf.hansson@linaro.org>
I don't understand, why does this qualify as a stable patch? The
changes says this is "optional", which means the device should work just
fine without it, right?
Is this a regression fix from something that previously used to work
properly?
You have read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
right?
thanks,
greg k-h
Hi reviewers,
I suggest to backport a commit to Linux kernel-5.10 and 6.6 stable tree.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/d…
author Lin Gui lin.gui(a)mediatek.com 2023-12-19 07:05:32 +0800
committer Ulf Hansson ulf.hansson(a)linaro.org 2024-01-02 17:54:05 +0100
commit e4df56ad0bf3506c5189abb9be83f3bea05a4c4f (patch)
tree a5db3a85f44b29dd773c5c65c3340d50b74b6687 /drivers/mmc/core/mmc.c
parent b062136d0d6f46d7ad5c88219cbd75f90cb18e81 (diff)
download linux-e4df56ad0bf3506c5189abb9be83f3bea05a4c4f.tar.gz
mmc: core: Add wp_grp_size sysfs node
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.
To allow userspace easy access of the CSD register bits, let's add sysfs
node "wp_grp_size".
Signed-off-by: Lin Gui lin.gui(a)mediatek.com
Signed-off-by: Bo Ye bo.ye(a)mediatek.com
Reviewed-by: AngeloGioacchino Del Regno angelogioacchino.delregno(a)collabora.com
Link: https://lore.kernel.org/r/20231218230532.82427-1-bo.ye@mediatek.com
Signed-off-by: Ulf Hansson ulf.hansson(a)linaro.org
------------------------------------
Best Regards !
Guilin
=====================================
MediaTek(ChengDu)Inc.
Email: mailto:lin.gui@mediatek.com
tel:+86-28-85939000-67009
Fax:+86-28-85929875
==============================================