From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 827B3C433E0 for ; Thu, 4 Feb 2021 08:53:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 394DF64D9D for ; Thu, 4 Feb 2021 08:53:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235146AbhBDIxN (ORCPT ); Thu, 4 Feb 2021 03:53:13 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38546 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234772AbhBDIxL (ORCPT ); Thu, 4 Feb 2021 03:53:11 -0500 Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B1F77C0613D6 for ; Thu, 4 Feb 2021 00:52:30 -0800 (PST) Received: by mail-pl1-x629.google.com with SMTP id x9so1398560plb.5 for ; Thu, 04 Feb 2021 00:52:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=3GYc3j0LV6uWWeY9tuYUCxyV+hFD6RVupRGibO/7f98=; b=LU9+t/+6TpnqCyJxyc5la5O0NK5DxLuzM20lcBxz3KoUXOFtQWBOhjAxqOnFVJkYmN Sos2ltry4CR1JQXRQW5+8O/RdCKzotTxq02FqCNEusjCkhWDIgiNuWiNTOBsXDn5o1vR XaA0PGHtDR4WoiQoE5DLS4UW4SuWqbyx4pb+n9vtPyibKFZE5sd8ElCXrM844vetV64M 2QPmwVpHzHQqNcIBl7mY7V5p9sfch8UDQogFW8VgSZVXCLey8IejjxIf9g8QIfKWIFqg he0p3DSGOjjmM4u37MBY6w1uk74723A0/+4ME9qwZ7Ga87YSz7ELn3dYqFoCxu5uU1Gd pXLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=3GYc3j0LV6uWWeY9tuYUCxyV+hFD6RVupRGibO/7f98=; b=rR8dvANhX4qhlBHA7lL1r7ifTyDBdjyfD6mCb2BCzusFPy0gntNyIjAWJk+cu/J+2x bLKm9rexx+Rhs/4x6rTMkGa2QWQ/GYf/nvxdKlY22K4cW+y0BujGOtnprgI0f7ZxfqTF 87GB9QaYHLZwq61fJMyb+bcq0AwI/uhI/YoksAr6dWQRlyKriOkQ+PFF8QBlWwXoL6Vp Y+k+Fo7XL71lu10LYrnvCNrvHXFmaKhHliCRlkFVtEAKIk/l0OlC8PM8o0Ff2ZU31okH Rh/7LcdkMbH7X+Tf4ZniyDTRrmVQvlJqjHebJifPhDDemXfbW8bJ4o8tAl4fijidbshv 5blg== X-Gm-Message-State: AOAM532SZrhNZwjdN1IqwMpMWF7lOQfs4DrKbZ37NqHjCsFV20J8D+/5 r0cZ/cxhhV3zXSE5+pm6667d X-Google-Smtp-Source: ABdhPJwFRfv+E9t3nw8/umSWCNIlyd5aUrs4h9KN7me07HwrpyiQgKNxbD0cp5qXBcb73+tmScx2xw== X-Received: by 2002:a17:90a:5a86:: with SMTP id n6mr7711124pji.65.1612428750089; Thu, 04 Feb 2021 00:52:30 -0800 (PST) Received: from thinkpad ([2409:4072:502:e1e4:2c42:3883:f540:5b9c]) by smtp.gmail.com with ESMTPSA id y26sm5604528pgk.42.2021.02.04.00.52.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 04 Feb 2021 00:52:29 -0800 (PST) Date: Thu, 4 Feb 2021 14:22:21 +0530 From: Manivannan Sadhasivam To: Miquel Raynal Cc: Boris Brezillon , 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 Message-ID: <20210204085221.GB8235@thinkpad> References: <20210202041614.GA840@work> <20210202091459.0c41a769@xps13> <20210203110522.12f2b326@xps13> <20210203111914.1c2f68f6@collabora.com> <8A2468D5-B435-4923-BA4F-7BF7CC0FF207@linaro.org> <20210203122422.6963b0ed@collabora.com> <20210204091336.1406ca3b@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210204091336.1406ca3b@xps13> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 04, 2021 at 09:13:36AM +0100, Miquel Raynal wrote: > Hi Manivannan, > > Manivannan Sadhasivam wrote on Wed, > 03 Feb 2021 17:11:31 +0530: > > > On 3 February 2021 4:54:22 PM IST, Boris Brezillon wrote: > > >On Wed, 03 Feb 2021 16:22:42 +0530 > > >Manivannan Sadhasivam wrote: > > > > > >> On 3 February 2021 3:49:14 PM IST, Boris Brezillon > > > wrote: > > >> >On Wed, 03 Feb 2021 15:42:02 +0530 > > >> >Manivannan Sadhasivam 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