From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id C2A7A81FA5 for ; Tue, 31 Jan 2017 03:44:53 -0800 (PST) Received: by mail-wm0-x22d.google.com with SMTP id r141so75419462wmg.1 for ; Tue, 31 Jan 2017 03:44:53 -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:user-agent; bh=HG4MUNy64r4xEigfp/VScnVj7rW3/4pQQy9IjXeOu3U=; b=ZJcX+HL2hVOhyEZXvPwPrwa3GVB+PHEGv9hkqI5RUV3Ctq2+UP4LZ9+Qc234MC2wrn JkyvTTsmUl7XCMX/dga86TC+joY5mleEob+G72VkwtWhw1XC7X0zbSNhs/J0Gt4U1MnD dJLJVLVhXT0bh69X9N9ybClOWAcPhp8BwD5Pg= 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:user-agent; bh=HG4MUNy64r4xEigfp/VScnVj7rW3/4pQQy9IjXeOu3U=; b=OIs5zmgBuyaAMKq///naMSAsRkR7Vujbb/A+wvPfhZFtav7VxPlI/a0BEjNm0+mHzY UyQ3lk0uFrpAFcG6Iy8jLgus7egwwaQQG4kr36nsuPHn72yYX0x6VaaWleGpBss/tj9g PhEKDjVucKabJQlxnTlUnPhPnc24lA3qKvrFpG69dKiPUrGT2TdZj4aIQ1pvEr3tm3Fj 8BgM7MzV0/7kytuwnhuFo1CZ4AC4XdZG+GxbjHu5IGMIyvqehs85Gx1kn5c5SP6laHLR m8aLNRJdCYZd8+5motRQ+ud3yH1CNHnzclRuvygIuBZn/ZcYZVz3g4ziXwL1wt3fDC7c rxkQ== X-Gm-Message-State: AIkVDXL4Rqpv9lXQfhkuDEznmtFweA3dUYmw8bwAExfhvdYEO8fjRP9MlKA5MK5lC64C3nOt X-Received: by 10.223.163.154 with SMTP id l26mr27190658wrb.35.1485863091976; Tue, 31 Jan 2017 03:44:51 -0800 (PST) Received: from bivouac.eciton.net (bivouac.eciton.net. [2a00:1098:0:86:1000:23:0:2]) by smtp.gmail.com with ESMTPSA id s17sm27937054wrc.6.2017.01.31.03.44.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 03:44:51 -0800 (PST) Date: Tue, 31 Jan 2017 11:44:49 +0000 From: Leif Lindholm To: Ryan Harkin Cc: Bhupesh Sharma , "edk2-devel@lists.01.org" , Ard Biesheuvel Message-ID: <20170131114449.GA25883@bivouac.eciton.net> References: <1484912445-23625-1-git-send-email-bhupesh.linux@gmail.com> <20170126143633.GY25883@bivouac.eciton.net> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [PATCH V3 1/1] ArmPlatformPkg/TZASC: Allow specifying subregions to be disabled X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2017 11:44:54 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jan 31, 2017 at 09:48:11AM +0000, Ryan Harkin wrote: > On 26 January 2017 at 14:36, Leif Lindholm wrote: > > On Fri, Jan 20, 2017 at 05:10:45PM +0530, Bhupesh Sharma wrote: > >> ARM TZASC-380 IP provides a mechanism to split memory regions being > >> protected via it into eight equal-sized sub-regions. A bit-setting > >> allows the corresponding subregion to be disabled. > >> > >> Several NXP/FSL SoCs support the TZASC-380 IP block and allow > >> the DDR connected via the TZASC to be partitioned into regions > >> having different security settings and also allow subregions > >> to be disabled. > >> > >> This patch enables this support and can be used for SoCs which > >> support such a partition of DDR regions. > >> > >> Details of the 'subregion_disable' register can be viewed here: > >> http://infocenter.arm.com/help/topic/com.arm.doc.ddi0431c/CHDIGDCI.html > >> > >> Cc: Leif Lindholm > >> Cc: Ard Biesheuvel > >> Contributed-under: TianoCore Contribution Agreement 1.0 > >> Signed-off-by: Bhupesh Sharma > >> [bhupesh.linux@gmail.com : Added my gmail ID as the NXP one is no longer valid] > >> Signed-off-by: Bhupesh Sharma > > > > Thanks for the cleanup. > > I may actually delete that CTA9x4 lib once your platform gets in... > > > Probably a good idea. I suspect it's not used or tested any more, > unless QEMU is using it? It's unused. And if we do ever resurrect the CTA9 port, it'll be using ARM Trusted Firmware, so this code will still be irrelevant. / Leif