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 phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3C4A7C433F5 for ; Wed, 11 May 2022 16:44:30 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 1776A8432E; Wed, 11 May 2022 18:44:28 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="OiusNln6"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 7B1448431E; Wed, 11 May 2022 18:44:26 +0200 (CEST) Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 5B9A18432E for ; Wed, 11 May 2022 18:44:22 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=seanga2@gmail.com Received: by mail-qt1-x834.google.com with SMTP id g3so1154053qtb.7 for ; Wed, 11 May 2022 09:44:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=mR3v+XOMHDXL4v/SJZtfJ+YpdcF+fj8rNIeihTl174o=; b=OiusNln6NUMRqqmGCbKkTiUrDHTemhTUI7k6G3s2+uhdiiAcAI7po8BU8o6gyO7hM0 hEi5QbIFRLn4CEmq3mrIDhIpSuqxdQ0m3XK9seU7w66hekvvvLkWwM6n/bH2s52SRXa2 6dtOUArPc/K64H2G/keMPwh/ZksGfQBLVxgREPO57Z3WoO9NjDFZFbj0RbKjFzrlrPXJ qiMARVMhipCZ3ruYL9Mje/qT3kj7h2rhIsHeZ8Xd7rwrbW/tJ0jnlbq1tJWFrNISdA44 EEMe0vL+e+E91x1IIbF8ZAenCkaQuojZpKDNYbp8e1I46JXOrmm89a0IQ87TYX/qfdrk w/0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=mR3v+XOMHDXL4v/SJZtfJ+YpdcF+fj8rNIeihTl174o=; b=vDolRYGCGCUgk1VIE7SBIhPS0fTJbSOP9Wi2Kie8RfQcTfkpe6pmp3q9HTT15K2svH U/vpOEmkoKCe+jPiZUGyTgxGr77LAniwPXkTT9N526nrzza7WwxgIlNqDANcWPAMNcAg 9VmF2dDd2/AB3di/3ZdiMaCj/QXgh/AmLIFVDs/ub0LGQR/ZbBT58WCA2+GbJ6gujcwH rrnVy7Zv4YHvl4UTYF386SC2ylacGcuIKLnGwlZcKHCT+lL90XhpVkAqSB0EFEIh0aRe Lyfi4LCwDdk2a0v595quBn6mjJvzp0+LCrJd2jA4Heuaz63rH+sOxjLANngiXre7qmbR 73VQ== X-Gm-Message-State: AOAM531fEmbw6GE0EoWt9NROGbNyrd9wZGu45g6M1oCxzyF9cs0NYvju JognQ6MvZ5Vn54I6zRlwoAs= X-Google-Smtp-Source: ABdhPJwwW9t8KBw/LCBafa1B2hzh6K4XRlgA4Xrcb95p2jw1/iTixaQfDXgb7QZ88V0wIo+AuHc/vg== X-Received: by 2002:ac8:5a86:0:b0:2f3:c9f8:3807 with SMTP id c6-20020ac85a86000000b002f3c9f83807mr23339768qtc.552.1652287461206; Wed, 11 May 2022 09:44:21 -0700 (PDT) Received: from [192.168.1.201] (pool-108-18-248-138.washdc.fios.verizon.net. [108.18.248.138]) by smtp.googlemail.com with ESMTPSA id h7-20020a05620a10a700b0069fc13ce23csm1424280qkk.109.2022.05.11.09.44.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 11 May 2022 09:44:20 -0700 (PDT) Subject: Re: [PATCH 0/4] stm32mp: add minimal RCC support for STM32MP13 To: Patrick Delaunay , u-boot@lists.denx.de Cc: Gabriel FERNANDEZ , Lukasz Majewski , Patrice Chotard , Tom Rini , U-Boot STM32 References: <20220510075114.1238086-1-patrick.delaunay@foss.st.com> From: Sean Anderson Message-ID: <41b170c1-99ba-18ac-4a94-01c90f67b97c@gmail.com> Date: Wed, 11 May 2022 12:44:20 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <20220510075114.1238086-1-patrick.delaunay@foss.st.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.5 at phobos.denx.de X-Virus-Status: Clean Hi Patrick, On 5/10/22 3:51 AM, Patrick Delaunay wrote: > > Add a minimal support for STM32MP13 RCC, the reset and clock controller > - update of the RCC MISC driver to bind the correct clock and reset driver > - reset driver, same than STM32MP15x = drivers/reset/stm32-reset.c > - clock driver, add a empty driver for STM32MP13x = > drivers/clk/stm32/clk-stm32mp13.c > - Add RCC node in SOC device tree with u-boot,dm-pre-reloc property > > This serie is only a preliminary step for STM32MP13 clock and reset support > in U-Boot, based on Linux kernel binding introduced by [1] and it prepares > the next device tree alignment with Linux kernel. > > The functional STMP13 clock driver based on CCF and on SCMI clocks > provided by OP-TEE and the clock and reset references in SOC device tree > will be pushed when the associated patches in [1] will be accepted. > > [1] Introduction of STM32MP13 RCC driver (Reset Clock Controller) > https://lore.kernel.org/linux-arm-kernel/20220316131000.9874-1-gabriel.fernandez@foss.st.com/ I'm not really sure what the purpose of this series is. Can you elaborate a bit on why we need a dummy clock driver? Why don't you just add the binding to the device tree without the associated driver? --Sean