This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Fri Jun 14 11:13:28 2024 >From mailfetcher Tue May 30 19:26:59 2023 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on pi4 X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_PASS,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 Authentication-Results: pi4.bmw12.nl; dmarc=pass (p=quarantine dis=none) header.from=sberdevices.ru Authentication-Results: pi4.bmw12.nl; dkim=pass (Good 2048 bit rsa-sha256 signature) header.d=sberdevices.ru header.a=rsa-sha256 Authentication-Results: pi4.bmw12.nl; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=2620:137:e000::1:20; helo=out1.vger.email; envelope-from=linux-kernel-owner@vger.kernel.org; receiver=) Received: from secure.jasper.es [188.166.10.231] by 1dc7d414a5be with IMAP (fetchmail-6.3.26) for (single-drop); Tue, 30 May 2023 19:26:59 +0200 (CEST) Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by pi4.bmw12.nl (Postfix) with ESMTP id 9C08D3F08B for ; Tue, 30 May 2023 19:26:53 +0200 (CEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232411AbjE3R0s (ORCPT ); Tue, 30 May 2023 13:26:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50670 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233407AbjE3R0b (ORCPT ); Tue, 30 May 2023 13 Received: from mx.sberdevices.ru (mx.sberdevices.ru [45.89.227.171]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B1C121BE; Tue, 30 May 2023 10:26:04 -0700 (PDT) Received: from s-lin-edge02.sberdevices.ru (localhost [127.0.0.1]) by mx.sberdevices.ru (Postfix) with ESMTP id E65975FD3D; Tue, 30 May 2023 20:24:52 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sberdevices.ru; s=mail; t=1685467492; bh=JC8G26p8JpCl7R7J4UNd1bRwiBp1AYCe1zqAjiOHqcE=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type; b=EC/RIpEzM9aXwUf91T3IpewYvolXKQk+9/r3 Received: from S-MS-EXCH01.sberdevices.ru (S-MS-EXCH01.sberdevices.ru [172.16.1.4]) by mx.sberdevices.ru (Postfix) with ESMTP; Tue, 30 May 2023 20:24:52 +0300 (MSK) Date: Tue, 30 May 2023 20:24:46 +0300 From: Dmitry Rokosov To: Jerome Brunet Cc: , , , , , , , , References: <20230517133309.9874-1-ddrokosov@sberdevices.ru><1jilc94x0d.fsf@starbuckisacylon.baylibre.com><20230530164933.m42ojv357atxd4gc@CAB-WSD-L081021> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20230530164933.m42ojv357atxd4gc@CAB-WSD-L081021> User-Agent: NeoMutt/20220415 X-Originating-IP: [172.16.1.6] X-ClientProxiedBy: S-MS-EXCH01.sberdevices.ru (172.16.1.4) To S-MS-EXCH01.sberdevices.ru (172.16.1.4) X-KSMG-Rule-ID: 4 X-KSMG-Message-Action: clean X-KSMG-AntiSpam-Status: not scanned, disabled by settings X-KSMG-AntiSpam-Interceptor-Info: not scanned X-KSMG-AntiPhishing: not scanned, disabled by settings X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 1.1.2.30, bases: 2023/05/30 11:20:00 #21377521 X-KSMG-AntiVirus-Status: Clean, skipped Precedence: bulk List-Id: X-Mailing-List: linux-kernel@vger.kernel.org Jerome, On Tue, May 30, 2023 at 07:49:33PM +0300, Dmitry Rokosov wrote: > Jerome, > > On Tue, May 30, 2023 at 06:14:01PM +0200, Jerome Brunet wrote: > > On Wed 17 May 2023 at 16:33, Dmitry Rokosov wrote: > > > > > A1 SoC has four clock controllers on the board: PLL, Peripherals, CPU, > > > and Audio. The audio clock controller is different from others, but the > > > rest are very similar from a functional and regmap point of view. > > > This patch series add support for Amlogic A1 PLL and Peripherals clock > > > drivers. > > > It blocks all A1 peripherals mainline support and a couple of patch series, > > > which were already reviewed and acked, but weren't merged due to pending > > > clock controller drivers series, e.g. > > > https://lore.kernel.org/all/20230418111612.19479-1-ddrokosov@sberdevices.ru/ > > > > > > TODO: CPU and Audio clock controllers are not included in this patch > > > series, it will be sent later. The following clks from these controllers > > > are not supported for now: > > > * Audio clks - vad, mclk_vad, mclk_d, resample_a, locker_in, mclk_b, > > > pdmdclk, pdmsysclk, eqdrc, spdifin, mclk_a, audio2_toaudiotop, > > > audio2_tovad, audio2_toddr_vad, audio2_tdmin_vad, audio2_pdm, > > > audio2_ddr_arb, audio_audiolocker, audio_eqdrc, audio_resamplea, > > > audio_spdifin, audio_toddrb, audio_toddra, audio_frddrb, audio_frddra, > > > audio_tdmoutb, audio_tdmouta, audio_loopbacka, audio_tdminlb, > > > audio_tdminb, audio_tdmina, audio_ddr_arb, mclk_c > > > > > > * CPU clks: cpu_fixed_source_sel0, cpu_fixed_source_div0, > > > cpu_fixed_source_sel1, cpu_fixed_source_div1, cpu_clk > > > > > > Validation: > > > * to double check all clk flags run below helper script: > > > pushd /sys/kernel/debug/clk > > > for f in *; do > > > if [[ -f "$f/clk_flags" ]]; then > > > flags="$(cat $f/clk_flags | awk '{$1=$1};1' | sed ':a;N;$!ba;s/\n/ | /g')" > > > echo -e "$f: $flags" > > > fi > > > done > > > popd > > > > > > * to trace current clks state use '/sys/kernel/debug/clk/clk_dump' node > > > with jq post-processing: > > > $ cat /sys/kernel/debug/clk/clk_dump | jq '.' > clk_dump.json > > > > > > * to debug clk rate propagation, compile kernel with the following > > > definition: > > > $ sed -i "s/undef CLOCK_ALLOW_WRITE_DEBUGFS/define CLOCK_ALLOW_WRITE_DEBUGFS/g" drivers/clk/clk.c > > > after that, clk_rate debug node for each clock will be available for > > > write operation > > > > > > > Applied, Thx > > Thank you very much! > > I noticed that you have applied version 15 of the patch. If I understand > correctly, this is because CLK_SET_RATE_NO_REPARENT for all RTC children > is preferred from your perspective. I agree with this decision. However, > version 16 includes a small refactoring patch that corrects a > misstyping by changing all sys_* related dividers and gates to > read-only operations, since they are set up from BootROM. Should I > submit this patch separately at a later time? > > Also could you please clarify the official process for handling these > patches? Currently, I don't see them in the linux-amlogic for-next > branches. Is there a separate repository for clock changes? I believe > the next repository is a fork of the clock framework, but unfortunately, > I cannot seem to locate it on git.kernel.org... Apologies for the > potentially simple questions... I came across your development tree on GitHub, and I noticed that you've applied the latest v16 version. Apologies for the noise! https://github.com/BayLibre/clk-meson/commit/84af914404dbc01f388c440cac72428784b8a161#diff-9e8258bc44803391f868de351058eef033cf3828d52801e1711f786501bc5911 -- Thank you, Dmitry   :      ,   ,   .     ,       , , ,  ,    ,         ,  .       , ,           . CONFIDENTIALITY NOTICE: This email and any files attached to it are confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.