[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8A2468D5-B435-4923-BA4F-7BF7CC0FF207@linaro.org>
Date: Wed, 03 Feb 2021 16:22:42 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
To: Boris Brezillon <boris.brezillon@...labora.com>
CC: Miquel Raynal <miquel.raynal@...tlin.com>, richard@....at,
vigneshr@...com, linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
bjorn.andersson@...aro.org
Subject: Re: [PATCH] mtd: rawnand: Do not check for bad block if bbt is unavailable
On 3 February 2021 3:49:14 PM IST, Boris Brezillon <boris.brezillon@...labora.com> wrote:
>On Wed, 03 Feb 2021 15:42:02 +0530
>Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org> wrote:
>
>> >>
>> >> I got more information from the vendor, Telit. The access to the
>3rd
>> >partition is protected by Trustzone and any access in non privileged
>> >mode (where Linux kernel runs) causes kernel panic and the device
>> >reboots.
>
>Out of curiosity, is it a per-CS-line thing or is this section
>protected on all CS?
>
Sorry, I didn't get your question.
>> >
>> >Ok, so this is not a chip feature but more a host constraint.
>> >
>> >In this case it would be a good idea to add a host DT property which
>> >describes the zone to avoid accessing it. Something like:
>> >
>> > secure-area/secure-section = <start length>;
>> >
>> >From the core perspective, we should parse this property early
>enough
>> >and return -EIO when trying to access this area.
>
>FWIW, I'm not sure making it part of the core is a good idea, at least
>not until we have a different platform with a same needs. The
>controller driver can parse it and return -EACCESS (or -EIO) when this
>section is accessed.
Fine with me.
Thanks,
Mani
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists