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 D543DC433F5 for ; Sat, 1 Oct 2022 14:20:01 +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=peH98glRBF9hA4DIta38MpASXI5HywFWiQQ1SrLnYpU=; b=U03mcJKiWymAYj 4Z+9nGYv1u0qVZc5qn3RVIB7zGMSLib+YfzUHC1nARmu1slz/8zin0r9SITROgKqcl0U9mqh6A1tU vRO1H28e6azPd3L5ss90tM8MY3EtnYz4Vsd2Mbxmo6seT/4gdB5SEZWnDE5bm/zDZrSCapblvRgO2 XFR4YqPfTgZtElaOtbSS15sak0pO8o1QvRIAADa8/geLmcOfASM8qcXUgoS5c2we6v/WoLcqSBuYV +StDCQmMz9hlnretIvu4YPWTnVCN+qw4qmhtSk4lyYMPj2WHzHOCkqEu5HWrL1RPWM8Gu6M/oe8Rn 0wNp7qxPN0cIkbi4Fp9Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oedKE-00Ep1W-Ls; Sat, 01 Oct 2022 14:18:42 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oedKB-00Eoyc-8m for linux-arm-kernel@lists.infradead.org; Sat, 01 Oct 2022 14:18:40 +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 sin.source.kernel.org (Postfix) with ESMTPS id 9C3FFCE01BC; Sat, 1 Oct 2022 14:18:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 940EFC433D6; Sat, 1 Oct 2022 14:18:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1664633909; bh=CKkGHr+sdWpXHrqOxQ/cqxBF9+kksWpN2DsUF+exBS4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=gDiEogvtf5TTgvs8BmlxSclEAjVqM9fTiq+o5fcwKxVdeFAQ6Pfkui85Ed3eaqiQe RzMUCQ5iBSLhnk/g2ffGL/WO1kg4sLz0xBOmhAagicxCbn2dqjj1NHlkRyfPWPkvRi NsaR7jK6405n2TAWqYTy/isr6oyCzqdljbJTkR+DMO55hjncaznzXa7ryXaAoJKoN7 0JJz5a2bB5ByK1YE/LAPq4i6LpVNhSq1VJrhsQcHioZ/GWeMgJd4DFLA+FQ668GuRM Ww+iyYMmfJpONDVLmFHkqj3Eyo5eWxl5GkzmNgFCmhwTdpkFe5OneWzYYQvEdMZg7G dzPcAgXkK14Ag== Date: Sat, 1 Oct 2022 07:18:27 -0700 From: Jakub Kicinski To: Jiri Pirko Cc: Vadim Fedorenko , Arkadiusz Kubalewski , Jonathan Lemon , Vadim Fedorenko , Aya Levin , netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org, Gal Pressman Subject: Re: [RFC PATCH v2 0/3] Create common DPLL/clock configuration API Message-ID: <20221001071827.202fe4c1@kernel.org> In-Reply-To: References: <20220626192444.29321-1-vfedorenko@novek.ru> <6b80b6c8-29fd-4c2a-e963-1f273d866f12@novek.ru> <20220930073312.23685d5d@kernel.org> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221001_071839_518916_DBBD8CC7 X-CRM114-Status: GOOD ( 16.67 ) 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 Sat, 1 Oct 2022 07:47:24 +0200 Jiri Pirko wrote: > >> Sure, but more hw does not mean you can't use sysfs. Take netdev as an > >> example. The sysfs exposed for it is implemented net/core/net-sysfs.c > >> and is exposed for all netdev instances, no matter what the > >> driver/hardware is. > > > >Wait, *you* are suggesting someone uses sysfs instead of netlink? > > > >Could you say more because I feel like that's kicking the absolute. > > I don't understand why that would be a problem. Why did you do devlink over netlink then? The bus device is already there in sysfs. > What I'm trying to say > is, perhaps sysfs is a better API for this purpose. The API looks very > neat and there is no probabilito of huge grow. "this API is nice and small" said everyone about every new API ever, APIs grow. > Also, with sysfs, you > don't need userspace app to do basic work with the api. In this case, I > don't see why the app is needed. Yes, with the YAML specs you don't need a per-family APP. A generic app can support any family, just JSON in JSON out. DPLL-nl will come with a YAML spec. > These are 2 biggest arguments for sysfs in this case as I see it. 2 biggest arguments? Is "this API is small" one of the _biggest_ arguments you see? I don't think it's an argument at all. The OCP PTP driver started small and now its not small. And the files don't even follow sysfs rules. Trust me, we have some experience here :/ As I said to you in private I feel like there may be some political games being played here, so I'd like to urge you to focus on real issues. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel