All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
	richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	bjorn.andersson@linaro.org
Subject: Re: [PATCH] mtd: rawnand: Do not check for bad block if bbt is unavailable
Date: Thu, 4 Feb 2021 14:22:21 +0530	[thread overview]
Message-ID: <20210204085221.GB8235@thinkpad> (raw)
In-Reply-To: <20210204091336.1406ca3b@xps13>

On Thu, Feb 04, 2021 at 09:13:36AM +0100, Miquel Raynal wrote:
> Hi Manivannan,
> 
> Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> wrote on Wed,
> 03 Feb 2021 17:11:31 +0530:
> 
> > On 3 February 2021 4:54:22 PM IST, Boris Brezillon <boris.brezillon@collabora.com> wrote:
> > >On Wed, 03 Feb 2021 16:22:42 +0530
> > >Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> wrote:
> > >  
> > >> On 3 February 2021 3:49:14 PM IST, Boris Brezillon  
> > ><boris.brezillon@collabora.com> wrote:  
> > >> >On Wed, 03 Feb 2021 15:42:02 +0530
> > >> >Manivannan Sadhasivam <manivannan.sadhasivam@linaro.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.   
> > >
> > >The qcom controller can handle several chips, each connected through a
> > >different CS (chip-select) line, right? I'm wondering if the firmware
> > >running in secure mode has the ability to block access for a specific
> > >CS line or if all CS lines have the same constraint. That will impact
> > >the way you describe it in your DT (in one case the secure-region
> > >property should be under the controller node, in the other case it
> > >should be under the NAND chip node).  
> > 
> > Right. I believe the implementation is common to all NAND chips so the property should be in the controller node. 
> 
> Looks weird: do you mean that each of the chips will have a secure area?

I way I said is, the "secure-region" property will be present in the controller
node and not in the NAND chip node since this is not related to the device
functionality.

But for referencing the NAND device, the property can have the phandle as below:

secure-region = <&nand0 0xffff>;

Thanks,
Mani

WARNING: multiple messages have this Message-ID (diff)
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: vigneshr@ti.com, richard@nod.at, linux-kernel@vger.kernel.org,
	bjorn.andersson@linaro.org,
	Boris Brezillon <boris.brezillon@collabora.com>,
	linux-mtd@lists.infradead.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: Do not check for bad block if bbt is unavailable
Date: Thu, 4 Feb 2021 14:22:21 +0530	[thread overview]
Message-ID: <20210204085221.GB8235@thinkpad> (raw)
In-Reply-To: <20210204091336.1406ca3b@xps13>

On Thu, Feb 04, 2021 at 09:13:36AM +0100, Miquel Raynal wrote:
> Hi Manivannan,
> 
> Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> wrote on Wed,
> 03 Feb 2021 17:11:31 +0530:
> 
> > On 3 February 2021 4:54:22 PM IST, Boris Brezillon <boris.brezillon@collabora.com> wrote:
> > >On Wed, 03 Feb 2021 16:22:42 +0530
> > >Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> wrote:
> > >  
> > >> On 3 February 2021 3:49:14 PM IST, Boris Brezillon  
> > ><boris.brezillon@collabora.com> wrote:  
> > >> >On Wed, 03 Feb 2021 15:42:02 +0530
> > >> >Manivannan Sadhasivam <manivannan.sadhasivam@linaro.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.   
> > >
> > >The qcom controller can handle several chips, each connected through a
> > >different CS (chip-select) line, right? I'm wondering if the firmware
> > >running in secure mode has the ability to block access for a specific
> > >CS line or if all CS lines have the same constraint. That will impact
> > >the way you describe it in your DT (in one case the secure-region
> > >property should be under the controller node, in the other case it
> > >should be under the NAND chip node).  
> > 
> > Right. I believe the implementation is common to all NAND chips so the property should be in the controller node. 
> 
> Looks weird: do you mean that each of the chips will have a secure area?

I way I said is, the "secure-region" property will be present in the controller
node and not in the NAND chip node since this is not related to the device
functionality.

But for referencing the NAND device, the property can have the phandle as below:

secure-region = <&nand0 0xffff>;

Thanks,
Mani

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2021-02-04  8:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30  3:54 [PATCH] mtd: rawnand: Do not check for bad block if bbt is unavailable Manivannan Sadhasivam
2021-01-30  3:54 ` Manivannan Sadhasivam
2021-02-01 14:18 ` Miquel Raynal
2021-02-01 14:18   ` Miquel Raynal
2021-02-02  4:16   ` Manivannan Sadhasivam
2021-02-02  4:16     ` Manivannan Sadhasivam
2021-02-02  8:14     ` Miquel Raynal
2021-02-02  8:14       ` Miquel Raynal
2021-02-03  9:58       ` Manivannan Sadhasivam
2021-02-03  9:58         ` Manivannan Sadhasivam
2021-02-03 10:05         ` Miquel Raynal
2021-02-03 10:05           ` Miquel Raynal
2021-02-03 10:12           ` Manivannan Sadhasivam
2021-02-03 10:12             ` Manivannan Sadhasivam
2021-02-03 10:19             ` Boris Brezillon
2021-02-03 10:19               ` Boris Brezillon
2021-02-03 10:52               ` Manivannan Sadhasivam
2021-02-03 10:52                 ` Manivannan Sadhasivam
2021-02-03 11:24                 ` Boris Brezillon
2021-02-03 11:24                   ` Boris Brezillon
2021-02-03 11:41                   ` Manivannan Sadhasivam
2021-02-03 11:41                     ` Manivannan Sadhasivam
2021-02-04  8:13                     ` Miquel Raynal
2021-02-04  8:13                       ` Miquel Raynal
2021-02-04  8:52                       ` Manivannan Sadhasivam [this message]
2021-02-04  8:52                         ` Manivannan Sadhasivam
2021-02-04  8:59                         ` Boris Brezillon
2021-02-04  8:59                           ` Boris Brezillon
2021-02-04  9:04                           ` Miquel Raynal
2021-02-04  9:04                             ` Miquel Raynal
2021-02-04  9:27                             ` Boris Brezillon
2021-02-04  9:27                               ` Boris Brezillon
2021-02-04  9:31                               ` Miquel Raynal
2021-02-04  9:31                                 ` Miquel Raynal
2021-02-04  8:59                         ` Miquel Raynal
2021-02-04  8:59                           ` Miquel Raynal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210204085221.GB8235@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=boris.brezillon@collabora.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.