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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C8C33C43219 for ; Thu, 13 Jan 2022 18:54:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237683AbiAMSyJ (ORCPT ); Thu, 13 Jan 2022 13:54:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40336 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232071AbiAMSyI (ORCPT ); Thu, 13 Jan 2022 13:54:08 -0500 Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DDF54C061574 for ; Thu, 13 Jan 2022 10:54:07 -0800 (PST) Received: by mail-pg1-x531.google.com with SMTP id c5so652109pgk.12 for ; Thu, 13 Jan 2022 10:54:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lixom-net.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tb5858QqXIcL5etsmWCS0ZKhHGEgdWFwctSsz78MvDI=; b=UK7Pq02IigfJ4UwrZ8hJfii4Xs3neqjQIZcCnn8iEJ2HaSzAsOFfNWUOvyqHby6xZ3 RPlt+Q9ETiZ57YNEA2lks/Dmj+Yk5qVw6hReh/CyXQxkUhA9iluXR8+lFYLBQ6QHkhM/ n2ilJTcMm9FfoIvY9Pc/SVqd5ihJfZNoRu56K6O5UOOWWjHBbiczhjlaF92FQkLDeZZm Na/p4eIaTEnhyy5sMOVTJTMbbIUFAHYkfchs8yApFNnFluEjW71UU0DvNSBgg1u1x70O rdrXoDDPa4vNGbC08xoLC6Fkxa2SJR0HokkgcJz1d/qarYXgH+CmInrAtTcqudfn2bNH TnYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tb5858QqXIcL5etsmWCS0ZKhHGEgdWFwctSsz78MvDI=; b=iQR3bIdTHw8/sRJapyvhOXqq0GcuIZ5NMKKBkZURAPQEJ+W0VDPbTt45YqDVj6+XCm HclOXLJrMY1w6WrQlDqpZyiKuz1p4MeWhFeYEtDD/gM6O1DyQNYOzctv8rtl4BiN9PBv R+FNlzBsROsecjEUJWTldihOGHtg0z/5dIlvqGZ2eyR1v8bI5RJQgPfDvNFVfmLFiOMh vN3p+67tTsrKLkhvnbGVGVOFKANwG8G2crN9SO7iPUJfabX/77EuKtTPjgWK4Pv76Tvm AJEa/X0auFsr9EBNh7Etse+cTdACNTW80pWac7cWYFL8vRf1uCdB1P0xXQJ2n52q6Srr pgsg== X-Gm-Message-State: AOAM533veibBmfTvZnylIoYbsJgn75bYs3taF3bDfOk2I+W5zmWwOSCS RxCmUucqqNXlMNzgEi1yxbjKNOxQrS9Mk/VjJyilNA== X-Google-Smtp-Source: ABdhPJzXlahtnsFy6IBae/4XXtwKfp3ieNHsHEWW/ixmJdS+WTYxk6qaqsRZoeKRiQr50fLtEznw6+6eMB/iQsmKuX4= X-Received: by 2002:a05:6a00:16c7:b0:4a5:d9c1:89da with SMTP id l7-20020a056a0016c700b004a5d9c189damr5491085pfc.34.1642100047311; Thu, 13 Jan 2022 10:54:07 -0800 (PST) MIME-Version: 1.0 References: <20220113121143.22280-1-alim.akhtar@samsung.com> In-Reply-To: From: Olof Johansson Date: Thu, 13 Jan 2022 10:53:55 -0800 Message-ID: Subject: Re: [PATCH 00/23] Add support for Tesla Full Self-Driving (FSD) SoC To: Krzysztof Kozlowski Cc: Alim Akhtar , Linux ARM Mailing List , Linux Kernel Mailing List , SoC Team , linux-clk , DTML , LinusW , Catalin Marinas , Rob Herring , Sylwester Nawrocki , "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" , Pankaj Dubey Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 13, 2022 at 4:32 AM Krzysztof Kozlowski wrote: > > On 13/01/2022 13:11, Alim Akhtar wrote: > > This patch set adds basic support for the Tesla Full Self-Driving (FSD) > > SoC. This SoC contains three clusters of four Cortex-A72 CPUs, > > as well as several IPs. > > > > Patches 1 to 8 provide support for the clock controller > > (which is designed similarly to Exynos SoCs). > > > > The remaining changes provide pinmux support, initial device tree support, > > and SPI, ADC, and MCT IP functionality. > > Does FSD have some version number? The FDS, especially in compatibles, > looks quite generic, so what will happen if a newer SoC comes later? You > would have: > - tesla,fsd-pinctrl > - tesla,fsd-xxxx-pinctrl (where xxxx could be some new version) > > This will be extra confusing, because fsd-pinctrl looks like the generic > one, while it is specific... The public sources from Tesla on github uses "turbo,trav" here, but that's also not a versioned name. The platform itself (hw3/hw31 -- 3.1 I presume?) has numbering, but that's system and not SoC: https://github.com/teslamotors/linux/tree/tesla-4.14-hw3/arch/arm64/boot/dts/turbo It would be easy to do "fsd2" for naming/numbering if needed for future versions, for example. I'm not so worried about this, especially if there's no corresponding internal version numbering that this would map naturally to. -Olof 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 5C92DC433EF for ; Thu, 13 Jan 2022 18:55:28 +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:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=557dg3SxexOvC5wyxWMYN+v328ExFFVs30gAo8kgosM=; b=MRLeT2eriugrbQ XAYHQ5WAa+wXhMbKCVB39tY35/9KQ1jwTC+vyS+CScBU1v01ENH7zbKXJgIaC/0lhCh5e+adBsfPQ 2NWW/qP1hz/CHaRQRH3PZ/ig4LfYci0RWy4hsQXWI+ctNvTFerKk+e0Q6CEencQ8XgGq6ZlMa4+cK mDO8CJad44PH3Hma5ZRmHh0fN0yLkvT8nRXaTzpPWuzgPNTb53kDcR210CtiJYkVISfD+ksMogVDy wuVtDm/eUJEWLLeKr2oDTsdL9UZYYXRlQCJp2rJBBnqQfQisJF4aJdvHv5YTxrQJqcG53zxbzeMXk ttt+mb7hmAybwLBMo7YQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1n85Ei-006vJh-RI; Thu, 13 Jan 2022 18:54:12 +0000 Received: from mail-pg1-x52a.google.com ([2607:f8b0:4864:20::52a]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1n85Ef-006vId-Ba for linux-arm-kernel@lists.infradead.org; Thu, 13 Jan 2022 18:54:10 +0000 Received: by mail-pg1-x52a.google.com with SMTP id x20so654545pgk.1 for ; Thu, 13 Jan 2022 10:54:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lixom-net.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tb5858QqXIcL5etsmWCS0ZKhHGEgdWFwctSsz78MvDI=; b=UK7Pq02IigfJ4UwrZ8hJfii4Xs3neqjQIZcCnn8iEJ2HaSzAsOFfNWUOvyqHby6xZ3 RPlt+Q9ETiZ57YNEA2lks/Dmj+Yk5qVw6hReh/CyXQxkUhA9iluXR8+lFYLBQ6QHkhM/ n2ilJTcMm9FfoIvY9Pc/SVqd5ihJfZNoRu56K6O5UOOWWjHBbiczhjlaF92FQkLDeZZm Na/p4eIaTEnhyy5sMOVTJTMbbIUFAHYkfchs8yApFNnFluEjW71UU0DvNSBgg1u1x70O rdrXoDDPa4vNGbC08xoLC6Fkxa2SJR0HokkgcJz1d/qarYXgH+CmInrAtTcqudfn2bNH TnYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tb5858QqXIcL5etsmWCS0ZKhHGEgdWFwctSsz78MvDI=; b=md6O6k2h9nyzHHXHPjAYUgYEUF1LLPClCUnN1rcHRoahK1rHfoy/t5d5F8TmSdA598 kfdxU2p1VOOm90wfQAC2ozm3z0uSAOr3Njoc4mcMx/+rT/E/uQfzPwV5VlfJcc6/CgyC Ita7CYAv4KZ7kKg7GB5J111mXhA+jKSZ0mp9gF0BwGwQOmZTj0KsHx3lMARiG+VSt4dR qUNqIUxkswWgAGEQiKk+aqr19v8csak9aas1LsJZlnVuqoZXUoJZAWHXyT0rU5HdFwCO mXkUgGtZ3tvrgxmU7PbtM+lKaT9NhiwsbpV2Dh0018n0DX5ID3P5hnYc62YWZN+DK2Kk Sd6g== X-Gm-Message-State: AOAM5321bmsavXWiX76vT8gGj9JvUA2k/muz75pXotx56ZAs08m8k9za waV8lWO0NZ4ZHjunMQamRMqGqWhykHWZcYfWYlhRPA== X-Google-Smtp-Source: ABdhPJzXlahtnsFy6IBae/4XXtwKfp3ieNHsHEWW/ixmJdS+WTYxk6qaqsRZoeKRiQr50fLtEznw6+6eMB/iQsmKuX4= X-Received: by 2002:a05:6a00:16c7:b0:4a5:d9c1:89da with SMTP id l7-20020a056a0016c700b004a5d9c189damr5491085pfc.34.1642100047311; Thu, 13 Jan 2022 10:54:07 -0800 (PST) MIME-Version: 1.0 References: <20220113121143.22280-1-alim.akhtar@samsung.com> In-Reply-To: From: Olof Johansson Date: Thu, 13 Jan 2022 10:53:55 -0800 Message-ID: Subject: Re: [PATCH 00/23] Add support for Tesla Full Self-Driving (FSD) SoC To: Krzysztof Kozlowski Cc: Alim Akhtar , Linux ARM Mailing List , Linux Kernel Mailing List , SoC Team , linux-clk , DTML , LinusW , Catalin Marinas , Rob Herring , Sylwester Nawrocki , "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" , Pankaj Dubey X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220113_105409_502968_CFA6A684 X-CRM114-Status: GOOD ( 16.86 ) 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 Thu, Jan 13, 2022 at 4:32 AM Krzysztof Kozlowski wrote: > > On 13/01/2022 13:11, Alim Akhtar wrote: > > This patch set adds basic support for the Tesla Full Self-Driving (FSD) > > SoC. This SoC contains three clusters of four Cortex-A72 CPUs, > > as well as several IPs. > > > > Patches 1 to 8 provide support for the clock controller > > (which is designed similarly to Exynos SoCs). > > > > The remaining changes provide pinmux support, initial device tree support, > > and SPI, ADC, and MCT IP functionality. > > Does FSD have some version number? The FDS, especially in compatibles, > looks quite generic, so what will happen if a newer SoC comes later? You > would have: > - tesla,fsd-pinctrl > - tesla,fsd-xxxx-pinctrl (where xxxx could be some new version) > > This will be extra confusing, because fsd-pinctrl looks like the generic > one, while it is specific... The public sources from Tesla on github uses "turbo,trav" here, but that's also not a versioned name. The platform itself (hw3/hw31 -- 3.1 I presume?) has numbering, but that's system and not SoC: https://github.com/teslamotors/linux/tree/tesla-4.14-hw3/arch/arm64/boot/dts/turbo It would be easy to do "fsd2" for naming/numbering if needed for future versions, for example. I'm not so worried about this, especially if there's no corresponding internal version numbering that this would map naturally to. -Olof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel