Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Fri, 2 Apr 2021 20:31:24 +0530 you wrote:
> On a typical end product, a vendor may choose to secure some regions in
> the NAND memory which are supposed to stay intact between FW upgrades.
> The access to those regions will be blocked by a secure element like
> Trustzone. So the normal world software like Linux kernel should not
> touch these regions (including reading).
>
> So this series adds a property for declaring such secure regions in DT
> so that the driver can skip touching them. While at it, the Qcom NANDc
> DT binding is also converted to YAML format.
>
> [...]
Here is the summary with links:
- [v11,1/4] dt-bindings: mtd: Convert Qcom NANDc binding to YAML
https://git.kernel.org/qcom/c/da386f7f2333
- [v11,2/4] dt-bindings: mtd: Add a property to declare secure regions in NAND chips
https://git.kernel.org/qcom/c/ee590106c331
- [v11,3/4] mtd: rawnand: Add support for secure regions in NAND memory
https://git.kernel.org/qcom/c/13b89768275d
- [v11,4/4] mtd: rawnand: qcom: Add missing nand_cleanup() in error path
https://git.kernel.org/qcom/c/ab2c8d3ef9b8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
