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.8 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 D25A5C4338F for ; Fri, 30 Jul 2021 19:02:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AB4D460F4B for ; Fri, 30 Jul 2021 19:02:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230386AbhG3TC3 (ORCPT ); Fri, 30 Jul 2021 15:02:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55988 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230094AbhG3TC3 (ORCPT ); Fri, 30 Jul 2021 15:02:29 -0400 Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6641EC0613D3 for ; Fri, 30 Jul 2021 12:02:24 -0700 (PDT) Received: by mail-vk1-xa30.google.com with SMTP id i26so2227167vkk.2 for ; Fri, 30 Jul 2021 12:02:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gBCAezsRz+diDpubea9ipqu5sk3T7ijBYsLpPq9JW6g=; b=bDgWF2lqGMUdyCyKt7IN7yXqW3h+wIKUz+MPEaJhXXpzBEp0DfQjh9CuOEjG0CzTM/ d6go/2disbc51wRYj5T56dCFF7xi2Rz1b2FVK3dHv6J18v1pdUDD/alM4dyrmFzkPCVA pP2PTVAS15KrTJIylWJrNUaLIw9s/j/JfrkmfrXlXajpC+0My7997AyW3R5J/44mKOOD nrdt1iHUwHO5PLk/3S8/L/SSLcWT+jC4zfOY46O7rmUAcjmKFHEE6P0UkaKf0pB+CJ9J X9SBMLKBTsJ+2Oq0jxxtMYwnzVaEmgz0h/cJoTjfTTFS3JhqVDJAxAVuUCMp6LLFiBD1 mfDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gBCAezsRz+diDpubea9ipqu5sk3T7ijBYsLpPq9JW6g=; b=auXCu5SMz3kim38aiv/j/H1BKOHoVKqEQbPwLmkYO2I2VilwkpZxaWLqQgV4a/bV/Q MlrkAMCx43kcY8XTPMvUIXk8X9/f1iLqemUXFED+ssXMYl2TMmFg5StsnLcSRhn47FJK ypJhZv6ioVEXHsOiKDwBXHgyQgCL3lg46oC0LOOA6MzMyi+9HPUKJqko2MBMUSlNaasL LmLNn9UaEYJDWJgfW49yrU/dxQvMagnqygn49/65PnRsUhmYfM6asfJStQbbinSbc2gM vj3Nu+DQnYz7hq0JgMfUNpi3bHktbDR2Tm2uoIHX+ibcJqpLvhY6LYAAYHjVM/gVTRxd th/w== X-Gm-Message-State: AOAM531mODLJ7EJIaEyuxXMxN5Hygar7JDvzV9koGEBzpoFELPGA9VVi BDTg80XKCyU2pa9WwvBF2qanWslkVINOp7Y1hYYILA== X-Google-Smtp-Source: ABdhPJy6d7W9hl2/7EtbdW42ci7f/PLQYOiCiB8PwC/au40+bBBTWt2EtWiXxIl/RIdt37Nw/MAlL2jVYoYJ1eEgjXE= X-Received: by 2002:a1f:3651:: with SMTP id d78mr3095853vka.0.1627671743462; Fri, 30 Jul 2021 12:02:23 -0700 (PDT) MIME-Version: 1.0 References: <20210730144922.29111-1-semen.protsenko@linaro.org> <5e35b0a7-13aa-3c62-ca49-14af2fcb2a08@canonical.com> In-Reply-To: From: Sam Protsenko Date: Fri, 30 Jul 2021 22:02:12 +0300 Message-ID: Subject: Re: [PATCH 00/12] Add minimal support for Exynos850 SoC To: Krzysztof Kozlowski Cc: Sylwester Nawrocki , Chanwoo Choi , Linus Walleij , Tomasz Figa , Rob Herring , Stephen Boyd , Michael Turquette , Jiri Slaby , Greg Kroah-Hartman , Charles Keepax , Ryu Euiyoul , Tom Gall , Sumit Semwal , John Stultz , Amit Pundir , devicetree , linux-arm Mailing List , linux-clk , "open list:GPIO SUBSYSTEM" , Linux Kernel Mailing List , Linux Samsung SOC , "open list:SERIAL DRIVERS" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org Hi Krzysztof, On Fri, 30 Jul 2021 at 20:21, Krzysztof Kozlowski wrote: > > On 30/07/2021 17:18, Krzysztof Kozlowski wrote: > > On 30/07/2021 16:49, Sam Protsenko wrote: > >> This patch series adds initial platform support for Samsung Exynos850 > >> SoC [1]. With this patchset it's possible to run the kernel with BusyBox > >> rootfs as a RAM disk. More advanced platform support (like MMC driver > >> additions) will be added later. The idea is to keep the first submission > >> minimal to ease the review, and then build up on top of that. > >> > >> [1] https://www.samsung.com/semiconductor/minisite/exynos/products/mobileprocessor/exynos-850/ > >> > > > > Great work! > > Thanks, Krzysztof! And thank you for reviewing the whole series. > > What's the SoC revision number (should be accessible via > > /sys/bus/soc/devices/soc0/)? Recent wrap in numbering of Exynos chips > > might bring confusion... # cat /sys/devices/soc0/revision 0 > > Judging by vendor's sources it is quite confusing. It looks mostly like > Exynos3830 but in few other cases it uses Exynos9 compatibles (Exynos9, > Exynos9820). Only in few places there is Exynos850. Marketing department > made it so confusing... The revision embedded in SoC would be very > interesting. > As I understand, this SoC is called Exynos850 everywhere now. Exynos3830 is its old name, not used anymore. As you noticed from patch #2, it shares some definitions with Exynos9 SoC, so I guess some software is similar for both architectures. Not sure about hardware though, never worked with Exynos9 CPUs. Anyway, I asked Samsung representatives about naming, and it seems like we should stick to "Exynos850" name, even in code. > Anyway, judging by current versioning, there is a risk Samsung will come > with a new chipset name conflicting with existing ones. It already > overflowed. > > It's even worse with a thingy called "Exynos9 auto" which hides > numbering even more. > > > Best regards, > Krzysztof 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=-4.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,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 B0893C4338F for ; Fri, 30 Jul 2021 19:04:20 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 7751060EFF for ; Fri, 30 Jul 2021 19:04:20 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 7751060EFF Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linaro.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org 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=tfduB+zkDELPplqUo8U8v5JfdbHWoPhycFiCyHMleX4=; b=V7mtyYL5N55c6S q0ZrHj75/yAUOiPGNFXATLnFVxKZbz5Fb54viVk5yQ4i+Gq5ggxubEpBkl03gej/ZNCQ9Ip6Y93KP siEziuHvQTzNK6NYJD2SMYWa0AbjBxxXCKqQQ/Wzi4fG5xjq6NouGhDOUxVskR2Rim5qfnNbadi8J 9MLNFg4ZxNrczGEFF5s/Q0XtjSIW+gTLgjiwm7HAszQDFC+Ny4rZk7dMN5xjEOjVZwcDqMLYQt4na TZhft29IEtD5QaiO86Ez6soAhI5gt1scm1YOQl06S9g0tR/bP/2cXrqpn6GJyZ8p7imFR+3UHDtUm WfzGAFG3k6ZrwHnL99lQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1m9Xm8-00A0bK-G4; Fri, 30 Jul 2021 19:02:28 +0000 Received: from mail-vk1-xa2e.google.com ([2607:f8b0:4864:20::a2e]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1m9Xm4-00A0aW-TS for linux-arm-kernel@lists.infradead.org; Fri, 30 Jul 2021 19:02:26 +0000 Received: by mail-vk1-xa2e.google.com with SMTP id r2so2212650vkl.11 for ; Fri, 30 Jul 2021 12:02:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gBCAezsRz+diDpubea9ipqu5sk3T7ijBYsLpPq9JW6g=; b=bDgWF2lqGMUdyCyKt7IN7yXqW3h+wIKUz+MPEaJhXXpzBEp0DfQjh9CuOEjG0CzTM/ d6go/2disbc51wRYj5T56dCFF7xi2Rz1b2FVK3dHv6J18v1pdUDD/alM4dyrmFzkPCVA pP2PTVAS15KrTJIylWJrNUaLIw9s/j/JfrkmfrXlXajpC+0My7997AyW3R5J/44mKOOD nrdt1iHUwHO5PLk/3S8/L/SSLcWT+jC4zfOY46O7rmUAcjmKFHEE6P0UkaKf0pB+CJ9J X9SBMLKBTsJ+2Oq0jxxtMYwnzVaEmgz0h/cJoTjfTTFS3JhqVDJAxAVuUCMp6LLFiBD1 mfDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gBCAezsRz+diDpubea9ipqu5sk3T7ijBYsLpPq9JW6g=; b=bjKmbpdmxF7xXDXCuEmUdkbxoqaCvUOAGBZXIDm1AY4/wcl/7lgne61rXTNwShHxjJ xe4zslA3nqrMVp+AfmAhYp+3jfO4a6rVfeD/cP3hL4wJVX3TpPwkiDfOmHqWbwHEKlgk aGdyHyKQbhqK3Q4cAalZ8ijYdUNOKpQ7Ia/lBWB3kPDOmrPVFURMg4tIGQuz/y+Qhpkb CzWO0l4OoHHyF5A8gq/RNRxAtLDmmTNT4AEglzziFrplTYuoRp78xh/wQgc9ABC4v00l oEaX25OFNbwL6RXYdbhhrJDiCogvWZCETGuHKr/bYyKjGb/neLfCh6ToB4L8Wi621uVL dqTg== X-Gm-Message-State: AOAM5313LKaLGDMBL1lchDEUoYB2037RgBtA1dlrbsuWAmF/7CXRvG24 IprjbbTtXKjqQZi8QCS2XGRK8wbE2ImOlok8WAyCFA== X-Google-Smtp-Source: ABdhPJy6d7W9hl2/7EtbdW42ci7f/PLQYOiCiB8PwC/au40+bBBTWt2EtWiXxIl/RIdt37Nw/MAlL2jVYoYJ1eEgjXE= X-Received: by 2002:a1f:3651:: with SMTP id d78mr3095853vka.0.1627671743462; Fri, 30 Jul 2021 12:02:23 -0700 (PDT) MIME-Version: 1.0 References: <20210730144922.29111-1-semen.protsenko@linaro.org> <5e35b0a7-13aa-3c62-ca49-14af2fcb2a08@canonical.com> In-Reply-To: From: Sam Protsenko Date: Fri, 30 Jul 2021 22:02:12 +0300 Message-ID: Subject: Re: [PATCH 00/12] Add minimal support for Exynos850 SoC To: Krzysztof Kozlowski Cc: Sylwester Nawrocki , Chanwoo Choi , Linus Walleij , Tomasz Figa , Rob Herring , Stephen Boyd , Michael Turquette , Jiri Slaby , Greg Kroah-Hartman , Charles Keepax , Ryu Euiyoul , Tom Gall , Sumit Semwal , John Stultz , Amit Pundir , devicetree , linux-arm Mailing List , linux-clk , "open list:GPIO SUBSYSTEM" , Linux Kernel Mailing List , Linux Samsung SOC , "open list:SERIAL DRIVERS" X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210730_120225_027067_8485C09D X-CRM114-Status: GOOD ( 24.44 ) 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 Hi Krzysztof, On Fri, 30 Jul 2021 at 20:21, Krzysztof Kozlowski wrote: > > On 30/07/2021 17:18, Krzysztof Kozlowski wrote: > > On 30/07/2021 16:49, Sam Protsenko wrote: > >> This patch series adds initial platform support for Samsung Exynos850 > >> SoC [1]. With this patchset it's possible to run the kernel with BusyBox > >> rootfs as a RAM disk. More advanced platform support (like MMC driver > >> additions) will be added later. The idea is to keep the first submission > >> minimal to ease the review, and then build up on top of that. > >> > >> [1] https://www.samsung.com/semiconductor/minisite/exynos/products/mobileprocessor/exynos-850/ > >> > > > > Great work! > > Thanks, Krzysztof! And thank you for reviewing the whole series. > > What's the SoC revision number (should be accessible via > > /sys/bus/soc/devices/soc0/)? Recent wrap in numbering of Exynos chips > > might bring confusion... # cat /sys/devices/soc0/revision 0 > > Judging by vendor's sources it is quite confusing. It looks mostly like > Exynos3830 but in few other cases it uses Exynos9 compatibles (Exynos9, > Exynos9820). Only in few places there is Exynos850. Marketing department > made it so confusing... The revision embedded in SoC would be very > interesting. > As I understand, this SoC is called Exynos850 everywhere now. Exynos3830 is its old name, not used anymore. As you noticed from patch #2, it shares some definitions with Exynos9 SoC, so I guess some software is similar for both architectures. Not sure about hardware though, never worked with Exynos9 CPUs. Anyway, I asked Samsung representatives about naming, and it seems like we should stick to "Exynos850" name, even in code. > Anyway, judging by current versioning, there is a risk Samsung will come > with a new chipset name conflicting with existing ones. It already > overflowed. > > It's even worse with a thingy called "Exynos9 auto" which hides > numbering even more. > > > Best regards, > Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel