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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 34866C77B73 for ; Sat, 27 May 2023 08:21:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=XTWKYqOCqsD7yFCMXErQjTiSd9Ci6TqeiiIZfYb9uzY=; b=tatOzdvuzVnhrX /ocoxHFuvBwepU6mM3PMvF6ScnQLyGc/K5yUo3j9DsJuaTADVWeXI5RrDd+7gxBFCkxPrbRZrAIRt rn98CxYg8jPl3LIQVlnz5ajJaXnuBc+Ot41DmFCFG6VrvSrwnNVaMrgu6g099SchC0xeZXCcqNgzE rHPibi/WwBjIzMiE2J4lcEy2uyOJWcGEHXA73ffHPE9N8ktHEyspQvhq6qskj6vrv/O9x9y0xgnxc GyAc+WrFqluR3ivlgDponYW6a1/UyXdoFeXG4cdrKtRtxJrYEhEIoj36pLXooCncPM6jhkZf69VCr rtF+jLxJf/ygIlHmtTsg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1q2pAR-005Dey-2f; Sat, 27 May 2023 08:20:51 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1q2pAP-005DeW-1b for linux-arm-kernel@lists.infradead.org; Sat, 27 May 2023 08:20:50 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id DC8706182E; Sat, 27 May 2023 08:20:48 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 83405C433EF; Sat, 27 May 2023 08:20:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1685175648; bh=yGXj/vsNJ1iEb/Lh6DCbMWxe66a+oLeNV5+w6Nt9qBY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=QSFUnZ2ez8FO3kEJiW2O9kPCmVgiSOIfnoR0/8zUmeqm1S+ExtQAfXBEyyGegtF8z TpQkTEC7qMZ5fSiERMMHr0MhI0CmHAPkmrBJI4xsmyjLPINvc9fWkZgjtEWB7HqvC4 Dh6w05YT0vmryoth/mDOvQyfJr72F7QnailqV9wo3X5T1OWq1IARgw8QUvtSD4bjvi hO+BaQK1hjPFJjxWLvCHyoFpGZfgZ+tcLQJN9bS9+ZfZRoCsA+uUMyUGu0Svnkg8gH b2OPcmQdiZ0tJXi5cAQduy8JckbXk4L+WS/IHNTvQszYIh0tRqHAd0JoRtRnLu9zHy K1jtTyxOE7FvA== Date: Sat, 27 May 2023 16:20:37 +0800 From: Shawn Guo To: Rasmus Villemoes Cc: "Peng Fan (OSS)" , s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Peng Fan Subject: Re: [PATCH V3] soc: imx: support i.MX93 soc device Message-ID: <20230527082037.GB528183@dragon> References: <20230515063730.2042715-1-peng.fan@oss.nxp.com> <33d57180-aa13-4178-86e1-c4cf6ef29a6e@prevas.dk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <33d57180-aa13-4178-86e1-c4cf6ef29a6e@prevas.dk> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230527_012049_594417_4EE9183F X-CRM114-Status: GOOD ( 20.22 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, May 24, 2023 at 03:30:01PM +0200, Rasmus Villemoes wrote: > On 15/05/2023 08.37, Peng Fan (OSS) wrote: > > From: Peng Fan > > > > i.MX93 Device Unique ID(UID) is in eFuse that could be read through > > OCOTP Fuse Shadow Block. i.MX93 UID is 128 bits long, so introduce > > soc_uid_high to indicate the higher 64bits. > > So apparently, the imx8mp also has 128 bits, at least according to the > reference manual, which mentions a "UNIQUE_ID[127:64]" at offset 0xe00 - > 0xe10 (i.e. bank 40, words 0 and 1). > > However, no further mention of these upper bits can be found anywhere in > the RM, or in linux or u-boot, mainline or downstream NXP. Furthermore, > quick experiments on both an imx8mp-evk and a custom imx8mp board > reveals that those words are not locked down (they do seem to have some > contents from the factory, but I can still set more bits in them). > > Could someone from NXP please explain what exactly bank 40, words 0 and > 1, on imx8mp are for? What do their initial value mean, why are they not > locked down, and why does the RM indicate that they should be part of a > unique_id? > > Also, assuming that the RM is just wrong (wouldn't be the first time; > the description of the lower 64 bits is also wonky in its own special > way), an obvious follow-up question is: Are the currently exposed > (lower) 64 bits unique among all imx8mp SOCs, i.e. does those 64 bits by > themselves actually work as a uid? Rasmus, Are you fine with the patch itself? Or do you expect more clarification in the commit log? Shawn _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel