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 10074C4332F for ; Fri, 9 Dec 2022 00:41:10 +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=MAmAOoqnI6VS9FR7FKajf1X3G0D8owLjAZC28y0T6wI=; b=TXK+fjxGccxGmz uw7jdmmP8BYc1frEBbBmKJ9XI1hKu4xiU4Sv4SREwT24czOFnGqSl81l5C8pwQTccavwv6eT7Sln8 ZahAU+5aEyIUVz4BL4/PLMLAhqKRmxERlCDPzWHfHy0x2wvGzIfxYAvV5XcRm2Q6RnEW3eOpMhh3w YCgmfgXh+EOn6ot6YQYA+CFEReuJLi0WzMMMNT2/4CXfVkxKhTRnaGAeW7Ayd0HmWtcny9DyA+GnR 3UyJmdmsn13u9UP8/9sLcgD9O++nJKjrCZo4I9ZQDm2CuIKlZaJD8Gmn/8NWvasUBx1Ux/PPy9SHF g4ZZ21Xwe7S8F3eBhgng==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3RQi-00Gj7S-UR; Fri, 09 Dec 2022 00:39:57 +0000 Received: from ams.source.kernel.org ([2604:1380:4601:e00::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1p3RQf-00GivP-3p for linux-arm-kernel@lists.infradead.org; Fri, 09 Dec 2022 00:39:54 +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 ams.source.kernel.org (Postfix) with ESMTPS id A798FB826B7; Fri, 9 Dec 2022 00:39:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 170FEC433EF; Fri, 9 Dec 2022 00:39:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670546390; bh=mu+QBJKsBbOEPe3vwUNFXgdSpmtahH0lZ/7jz8cGUtg=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=c+V1MIkJQ1+4wlqIwSgEgYrDMdSdTDElGCQrQSGaMfd8N1WrHjLLmyPXFFCf1qwSo xkHkbo6twikXnSyq9XeGiKD+hyrClpNIinTbcKvzhrNAewOA9WfIBGvoeZ4ySg/dyU aSMOQ8QcGb6d3cw74rZ3kM0NJca2rLD1Vvkx86vBO7o1JWzX0QTS0hBE1KvIkrEbc6 b6EtWISwZX8Vrymlkg1t+MVsZPzxRG6CVbYf9ef6YeTMUGbfLMpcG3YItGOUeAITcp cAt7c3LWhuUx2Y9svTaoNkYP+pjgjIVk478tH+DimuqEn0CS44iTgu2GZ2sRda19ge y6ZeR7cmNnifg== Date: Thu, 8 Dec 2022 16:39:49 -0800 From: Jakub Kicinski To: Jiri Pirko Cc: netdev.dump@gmail.com, "'Kubalewski, Arkadiusz'" , 'Vadim Fedorenko' , 'Jonathan Lemon' , 'Paolo Abeni' , netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org Subject: Re: [RFC PATCH v4 0/4] Create common DPLL/clock configuration API Message-ID: <20221208163949.3833fe7b@kernel.org> In-Reply-To: References: <20221129213724.10119-1-vfedorenko@novek.ru> <20221206184740.28cb7627@kernel.org> <10bb01d90a45$77189060$6549b120$@gmail.com> <20221207152157.6185b52b@kernel.org> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221208_163953_336594_9A9201D0 X-CRM114-Status: GOOD ( 17.28 ) 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, 8 Dec 2022 12:28:51 +0100 Jiri Pirko wrote: > >I think we discussed using serial numbers. > > Can you remind it? Do you mean serial number of pin? Serial number of the ASIC, board or device. Something will have a serno, append to that your pin id of choice - et voila! > >Are you saying within the driver it's somehow easier? The driver state > >is mostly per bus device, so I don't see how. > > You can have some shared data for multiple instances in the driver code, > why not? The question is whether it's easier. Easier to ensure quality of n implementations in random drivers. Or one implementation in the core, with a lot of clever people paying attention and reviewing the code. > >> There are many problems with that approach, and the submitted patch is not > >> explaining any of them. E.g. it contains the dpll_muxed_pin_register but no > >> free > >> counterpart + no flows. > > > >SMOC. > > Care to spell this out. I guess you didn't mean "South Middlesex > Opportunity Council" :D Simple matter of coding. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel