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 6D56BC43334 for ; Fri, 24 Jun 2022 17:56:42 +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:MIME-Version:References:In-Reply-To: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=CbISlPHXr90ZbEMw7h0F8t8gXC9EZNE0UTOi0iJcUfw=; b=pR9PU3zWv/8mAX ISdzzJFYpICJ8uTHXPvIHY9MYvoeGvXnE/d0shAxvzSzQy8ZLWcqpP/WqfJsQliLJHEyNv7EsIvGc Qp86Haz3h1v2pLHjKv2ZEIGBzn+B3JZeKzMo0NGNkhAruh9aqDArhFejx6zlWUXielxWFHCXCKul+ c1UYAxttw+4X/gq+vmQkI33GRegoC28t73Ttzk2pa05yXlxDo4jV8meO/igxIQRPAbt4gM0+t8wBv B6tdtha6yDBm97k1ivVbDBGrinV3xOoD/RtavXagMBye12zE29R/U8RYOTgrmNGaBbCdhO/Y6duBi cUbtDjl/5eL/k5UbFluw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o4nWt-003Mvb-7l; Fri, 24 Jun 2022 17:55:39 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o4nWq-003MuO-93 for linux-arm-kernel@lists.infradead.org; Fri, 24 Jun 2022 17:55:37 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 7700A61F0B; Fri, 24 Jun 2022 17:55:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 97F67C34114; Fri, 24 Jun 2022 17:55:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1656093331; bh=ifbQWrSacxUg2H6ShAtyaoldstP4yu0ExIla1qMp8+A=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Z254G4QIEyIBoNKv9dQBEtArmGVblyDCBp5RdgIhZobV2Wt3Cr8rqu4pQvTxdlNbE hjneVy6tAq2P/KG8/lhQ9gZMwlTo/VhEOuet8QKbz6W2nGZleD6rT6NxeVikB85JfM CS5/I/uXa6GQdbz0kj5hixsb1PUERksTr2MAMYcpM5ZCy9GMhns0TEzB4IuZ3x0kSE dXt2GeLJJXpVZSznB51j5tLvAsaP155Sjns73v+uKSJLRDkHdrVqevMtpFRfKgwZAv 6XwLEZZBD2XeXf1RaL0ou7XM/Cz86MAGQwRoL+G2032SId2PoARzI3X51OSyOGi71h Qc7MPlwVIwyDA== Date: Fri, 24 Jun 2022 10:55:22 -0700 From: Jakub Kicinski To: Florian Fainelli Cc: Vadim Fedorenko , Vadim Fedorenko , Aya Levin , Arkadiusz Kubalewski , netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org Subject: Re: [RFC PATCH v1 0/3] Create common DPLL/clock configuration API Message-ID: <20220624105522.1961b4d3@kernel.org> In-Reply-To: <3d2970c7-f785-edf7-2936-807cf21ec65e@gmail.com> References: <20220623005717.31040-1-vfedorenko@novek.ru> <3d2970c7-f785-edf7-2936-807cf21ec65e@gmail.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220624_105536_406736_7B862289 X-CRM114-Status: GOOD ( 14.68 ) 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 Fri, 24 Jun 2022 10:20:44 -0700 Florian Fainelli wrote: > On 6/22/22 17:57, Vadim Fedorenko wrote: > > Implement common API for clock/DPLL configuration and status reporting. > > The API utilises netlink interface as transport for commands and event > > notifications. This API aim to extend current pin configuration and > > make it flexible and easy to cover special configurations. > > Any reasons why you are not copying the Linux common clock framework > maintainers and not seeking to get your code included under drivers/clk/ > where it would seem like a more natural place for it? > > Is netlink really a necessary configuration interface for those devices? Sorry, likely my fault. Vadim asked me who to CC and I suggested to just hit linux-arm-kernel assuming it's the best place for chance encounters with embedded folks. An assumption based on no real data or experience. Regarding the clock framework I think I brought that suggestion up in the mega thread when Maciej M proposed the SyncE support and putting all the PLL info directly in rtnetlink. There wasn't much support, and perhaps that's fair, clock generation vs runtime DPLL config for time source purposes are different use cases. With that longish excuse out of the way, CCing linux-clk now, here's the lore link to the thread: https://lore.kernel.org/r/20220623005717.31040-2-vfedorenko@novek.ru/ _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel