Message ID | 20231016101608.993921-1-n-francis@ti.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:612c:2908:b0:403:3b70:6f57 with SMTP id ib8csp3357303vqb; Mon, 16 Oct 2023 03:17:25 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHAjkQm75gAkqAAV6IPap6eszfEzMSrXohzczbzofoMxMkXfrtTe/eARebXh0w/2sqQ3fQ/ X-Received: by 2002:a05:6a00:2b8a:b0:6bc:67ca:671d with SMTP id dv10-20020a056a002b8a00b006bc67ca671dmr5792391pfb.1.1697451444861; Mon, 16 Oct 2023 03:17:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1697451444; cv=none; d=google.com; s=arc-20160816; b=X9UKxo6KtYH/cgkMfMfDTjDCDTcsmf39zwkDtyvRFRKWCIj6UZReEP5jrdwHNTroNF gaoHQWNqiamzeIqMTkwt9y8b31CrCbkH/ekuxH7GR16JrC9EvTglUQ3zF9Vu6wrDfCHk ZwaUO6qgelzNhkyncC4TSx9ATgENawq+3GsasW2A2BLAIoS0d2Rqblm14JmCmrDfhuFA kzT5WnNQ7w/NKpdyn3kt/DMeF4DTtgIKDERtdNZYOJpxYdNgntGu1VYuCwxmEl8TF7Ph 1luI8fej62G9pXLkXmxuNzopgxZS3Rh4uhR1CHSdXkTE9Rly0FjkTtC0bYxEkImH4blP aUCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=8Y44B5L9t+poTzbMACP4tWpaMfdbqEnIKJldTWMn6pA=; fh=zXIzpqU6fkcvkKYOWPETYAc8kHdGN5li0oSb9j2GXFE=; b=KdOTBUWcFyXCJ1zbpXF6wjXnzZkE2iiAalIIqqw+7PdO89Q1zM2K2dJ/WScIKcjIsw AWLsGhPUBO6hQF0vCdsONE6mMJz6egd7bQpJdtG6r7DTT2V8FRtAXlDlF6RYDHwg4hx0 6I9K0AGL5SmPxUETm1HhfcMvZG5WtqFUvmb8VELdPraiqKqrUARP+2xh2MQ3kpuIR1Nw qEzgXKtVn3H+tKJC1TmdhMrQPo9KbiKKi+a3OWsyqUL1OhmlRuuAEczM5KSW9QQb6n4Q 3hdVm1SjLgijgMOl8843uPX+OpSByOV5HlRJkBHXeisGhguQr/wyydFGzT29j23a4vVT ECFg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=vThcx4UX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from lipwig.vger.email (lipwig.vger.email. [2620:137:e000::3:3]) by mx.google.com with ESMTPS id cb6-20020a056a02070600b005b4600b5738si4151055pgb.261.2023.10.16.03.17.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 Oct 2023 03:17:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=vThcx4UX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id DCE94804C211; Mon, 16 Oct 2023 03:17:20 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at lipwig.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232969AbjJPKRG (ORCPT <rfc822;hjfbswb@gmail.com> + 18 others); Mon, 16 Oct 2023 06:17:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55966 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233223AbjJPKQo (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 16 Oct 2023 06:16:44 -0400 Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 852861BD for <linux-kernel@vger.kernel.org>; Mon, 16 Oct 2023 03:16:21 -0700 (PDT) Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 39GAGCCn093567; Mon, 16 Oct 2023 05:16:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1697451372; bh=8Y44B5L9t+poTzbMACP4tWpaMfdbqEnIKJldTWMn6pA=; h=From:To:CC:Subject:Date; b=vThcx4UXvVjCKck/glEF9/4kIfTuCsUf/YtCYMb37CuPpiusNNrS8mndIii946AtS S4JE0r9RJHK1NB2igT0tTJTnPZVUDEFqsdnrd+O60Z+318Awz6eyBBhuAENameJi6v V/+vfoIo7mYGmltHHBhIcO67LOwm/QDEF9tYUQys= Received: from DFLE104.ent.ti.com (dfle104.ent.ti.com [10.64.6.25]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 39GAGCAW020250 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 16 Oct 2023 05:16:12 -0500 Received: from DFLE103.ent.ti.com (10.64.6.24) by DFLE104.ent.ti.com (10.64.6.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Mon, 16 Oct 2023 05:16:11 -0500 Received: from lelv0327.itg.ti.com (10.180.67.183) by DFLE103.ent.ti.com (10.64.6.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Mon, 16 Oct 2023 05:16:12 -0500 Received: from a0497641-HP-Z2-Tower-G9-Workstation-Desktop-PC.dhcp.ti.com (ileaxei01-snat.itg.ti.com [10.180.69.5]) by lelv0327.itg.ti.com (8.15.2/8.15.2) with ESMTP id 39GAG90f033447; Mon, 16 Oct 2023 05:16:10 -0500 From: Neha Malcom Francis <n-francis@ti.com> To: <nm@ti.com>, <ssantosh@kernel.org>, <t-konduru@ti.com> CC: <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <n-francis@ti.com>, <u-kumar1@ti.com> Subject: [PATCH v3 0/3] Revamp k3-socinfo driver Date: Mon, 16 Oct 2023 15:46:05 +0530 Message-ID: <20231016101608.993921-1-n-francis@ti.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lipwig.vger.email Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Mon, 16 Oct 2023 03:17:20 -0700 (PDT) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1779906846188193828 X-GMAIL-MSGID: 1779906846188193828 |
Series | Revamp k3-socinfo driver | |
Message
Neha Malcom Francis
Oct. 16, 2023, 10:16 a.m. UTC
k3-socinfo driver doesn't account for difference series of silicon revisions instead of the typical 1.0, 2.0 etc case. This exception is currently already seen in J721E. This series aims to modify the driver to account for those exceptions as well as clean things up a bit. Changes since v2: - Nishanth: - update commit message - move from double Signed-off-by to Co-developed-by - make j721e_rev_string_map[] a const char - drop k3_rev_string_map[] and continue using old "variant++" logic for the typical cases - appropriate error handling with no overrides distinguishing between ENODEV and ENOMEM - add patch for error handling initial cleanup - reorder patches Changes since v1: - Nishanth: - undo churning of family attribute - remove unnecessary code relocation - add Thejasvi to Signed-off-by as we are now similar to the initial attempt [1] - separate out typo fixes to another patch (2/2) Boot log: https://gist.github.com/nehamalcom/ff9375dcde681dd78712ee8473b24a50 (See relevant k3-socinfo dev_info print on line 276) v2: https://lore.kernel.org/lkml/20230915064650.2287638-1-n-francis@ti.com/T/ v1: https://lore.kernel.org/linux-arm-kernel/20230914074426.1901226-1-n-francis@ti.com/T/ [1] https://lore.kernel.org/all/20230607080349.26671-1-t-konduru@ti.com/ Neha Malcom Francis (3): soc: ti k3-socinfo: Fix typo soc: ti: k3-socinfo: Avoid overriding ret soc: ti: k3-socinfo: Revamp driver to accommodate different rev structs drivers/soc/ti/k3-socinfo.c | 76 +++++++++++++++++++++++++++---------- 1 file changed, 57 insertions(+), 19 deletions(-)
Comments
Hi Neha Malcom Francis, On Mon, 16 Oct 2023 15:46:05 +0530, Neha Malcom Francis wrote: > k3-socinfo driver doesn't account for difference series of silicon > revisions instead of the typical 1.0, 2.0 etc case. This exception is > currently already seen in J721E. This series aims to modify the driver > to account for those exceptions as well as clean things up a bit. > > Changes since v2: > - Nishanth: > - update commit message > - move from double Signed-off-by to Co-developed-by > - make j721e_rev_string_map[] a const char > - drop k3_rev_string_map[] and continue using old > "variant++" logic for the typical cases > - appropriate error handling with no overrides > distinguishing between ENODEV and ENOMEM > - add patch for error handling initial cleanup > - reorder patches > > [...] I have applied the following to branch ti-drivers-soc-next on [1] with minor fixups. Thank you! [1/3] soc: ti k3-socinfo: Fix typo commit: 8dec342ead710dace27dc82096144bf7a1011827 [2/3] soc: ti: k3-socinfo: Avoid overriding ret commit: 3aeb0d3694e16b5066db82aa1152884f2e6aace0 [3/3] soc: ti: k3-socinfo: Revamp driver to accommodate different rev structs commit: 07e651db2d78eac4c41d7144eb5ea734af2328fc All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. [1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
Hi Neha Malcom Francis, On Mon, 16 Oct 2023 15:46:05 +0530, Neha Malcom Francis wrote: > k3-socinfo driver doesn't account for difference series of silicon > revisions instead of the typical 1.0, 2.0 etc case. This exception is > currently already seen in J721E. This series aims to modify the driver > to account for those exceptions as well as clean things up a bit. > > Changes since v2: > - Nishanth: > - update commit message > - move from double Signed-off-by to Co-developed-by > - make j721e_rev_string_map[] a const char > - drop k3_rev_string_map[] and continue using old > "variant++" logic for the typical cases > - appropriate error handling with no overrides > distinguishing between ENODEV and ENOMEM > - add patch for error handling initial cleanup > - reorder patches > > [...] I have applied the following to branch ti-drivers-soc-next on [1]. Thank you! [3/3] soc: ti: k3-socinfo: Revamp driver to accommodate different rev structs commit: 3ba080bf46e4a9039d0d41356f4a2515e00bf747 The networking dependency previously identified has been sorted out and available in linux-next[2] since next-20231206. So, this is a good time for us to merge the patch that I have been keeping held up. At least on my local scan, I don't see any other in-tree driver impacted by this. All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. [1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git [2] https://lore.kernel.org/all/20231201132033.29576-1-r-gunasekaran@ti.com/