On Mon, Mar 08, 2021 at 07:04:17PM +0530, Manivannan Sadhasivam wrote:
> On Mon, Mar 08, 2021 at 10:02:47AM +0100, Boris Brezillon wrote:
> > On Mon, 8 Mar 2021 11:14:47 +0530
> > Manivannan Sadhasivam wrote:
> >
>
> [...]
>
> > > /* helper to configure address register values */
> > > -stati
On Mon, Mar 08, 2021 at 10:02:47AM +0100, Boris Brezillon wrote:
> On Mon, 8 Mar 2021 11:14:47 +0530
> Manivannan Sadhasivam wrote:
>
[...]
> > /* helper to configure address register values */
> > -static void set_address(struct qcom_nand_host *host, u16 column, int page)
> > +static int set
On Mon, 8 Mar 2021 11:14:47 +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. So
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 region
4 matches
Mail list logo