On Fri, Mar 19, 2021 at 05:56:59PM +0100, Boris Brezillon wrote:
> On Fri, 19 Mar 2021 20:30:10 +0530
> Manivannan Sadhasivam wrote:
>
> > @@ -2737,6 +2783,11 @@ static int nand_read_page_swecc(struct nand_chip
> > *chip, uint8_t *buf,
> > uint8_t *ecc_code = chip->ecc.code_buf;
> >
On Fri, Mar 19, 2021 at 05:52:58PM +0100, Boris Brezillon wrote:
> On Fri, 19 Mar 2021 20:30:10 +0530
> Manivannan Sadhasivam 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
On Fri, 19 Mar 2021 20:30:10 +0530
Manivannan Sadhasivam wrote:
> @@ -2737,6 +2783,11 @@ static int nand_read_page_swecc(struct nand_chip
> *chip, uint8_t *buf,
> uint8_t *ecc_code = chip->ecc.code_buf;
> unsigned int max_bitflips = 0;
>
> + /* Check if the region is secured
On Fri, 19 Mar 2021 20:30:10 +0530
Manivannan Sadhasivam 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.
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
5 matches
Mail list logo