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 31FC4C433F5 for ; Sun, 2 Oct 2022 14:36:32 +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:In-Reply-To:MIME-Version:References: 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=p2gmv4NMcpXDqgGVpyQdsC3lvjCGRHukL0feJr56xCE=; b=y3IEvxLmsVIMlz LKb+7RS4uBv1TpVZnN6oIP5JDE+S/neXqMoDpsFWkpHWhBn2kYW7rHth5U5roXLOPANZ0hjHwqZgR SuynEpLzFN9sLL0prhDWz497JIDA0MTAL4yCgS8GpCIEYq/fspiANXxLKyejQN7VyUTU9YfSBO94h U/WvN5lPe+WICW465Ew3XOO3ZfextDw4wfIiqLrP6vWIpm+2i3YLZ53WYHjbHFSzs08flFEeOXv0M VX+g9mwZU1Un01p9ntIKUjy2npPMgfHR9UBRdIcOdk4B8P2pbcwkiZFeMZeM6v2MPJsCVsP57wl5F RoUMt2jf2F5Hk1T3CtNw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1of03p-001TkH-Pq; Sun, 02 Oct 2022 14:35:17 +0000 Received: from mail-ej1-x636.google.com ([2a00:1450:4864:20::636]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1of03l-001Tjw-KD for linux-arm-kernel@lists.infradead.org; Sun, 02 Oct 2022 14:35:16 +0000 Received: by mail-ej1-x636.google.com with SMTP id f1so128662ejw.7 for ; Sun, 02 Oct 2022 07:35:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=resnulli-us.20210112.gappssmtp.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=Enk2dM0C4eT6Sv++JaTkLKJvaPD74u7cEzApvj+1W9w=; b=tJvPZNDGMXxdVhP+xXUiILb9tv2wOEEPL9h3R4M+qXumk4AJp0vOVT3Fc5ivK4TLVs wsOWaorVAq4lo9UcT9vahp7bhduHu9s2IJ2Ue+fatRgZpaPq3cJX/z1XqBMWyNkxFZQB QoqJyGfenEXK+U7BlguuSHykznIkDEO2SaZOpwTtA72EEeHDQQhLdZs0MH+9AeqzP8C+ Snev139AAjH1IqHDjjIu/11J1+WFeU2OVmceyRBIFXCip2Ks+tjOxik8Jx23a6MX4Ime M3IAboU61/ya+KnmTB5nrzFlCnjUaKXHjPI6s2ZQvEOtGOa7S39T+Ij2+7yz7zrQgJcS 9X1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=Enk2dM0C4eT6Sv++JaTkLKJvaPD74u7cEzApvj+1W9w=; b=zGRYxNnVM1+jgoctTNoUuYfTurQH9k0SNd4UAH+EQvqb3KR46cw9+5BvKpiZpdMrsw juP9lrLLx1Fk9aK3zW9oKP6v7/lSCDqvRvsBqMVnBrKjk6O3KFgGBqk8CiA44fjWInrx vgu5bwfF9YAGXZi+bymM8QZM9eFGj/rN6i/E3YAVwj5KYWpm6RT2U/f4RdHZJsNGkCtD SRVlcRBMcMSkFOIeEVF7UbuId4QYbLjbL1F6HCwR8ZdYARbP5jfjRERk8MesaTlDb4HW NHHthcVwYulSqZsc4CraHTkI9HPzKXqV/JI+bPR9/FymFS8eTlBdKVsbrAg8UCZsxRZ0 PVGw== X-Gm-Message-State: ACrzQf2UPSRIDVVTxi6qaJ0QqhWWczJ000wdEEiBanaSUNxHD032sJJJ Aglzz3dF0Zdly3NvMNEKkpFP+A== X-Google-Smtp-Source: AMsMyM6WR+UYVyxhw409NtcQaCJWZJN825wSFlNCOYFdO1PIkGwwOexQzN6SpBokEJnfNdDjn5UA8Q== X-Received: by 2002:a17:906:9bca:b0:78a:49c4:4110 with SMTP id de10-20020a1709069bca00b0078a49c44110mr3111900ejc.345.1664721310182; Sun, 02 Oct 2022 07:35:10 -0700 (PDT) Received: from localhost (host-213-179-129-39.customer.m-online.net. [213.179.129.39]) by smtp.gmail.com with ESMTPSA id j5-20020aa7de85000000b004542e65337asm5447072edv.51.2022.10.02.07.35.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 02 Oct 2022 07:35:08 -0700 (PDT) Date: Sun, 2 Oct 2022 16:35:07 +0200 From: Jiri Pirko To: Jakub Kicinski 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: References: <20220626192444.29321-1-vfedorenko@novek.ru> <6b80b6c8-29fd-4c2a-e963-1f273d866f12@novek.ru> <20220930073312.23685d5d@kernel.org> <20221001071827.202fe4c1@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20221001071827.202fe4c1@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221002_073513_905430_871F6AE9 X-CRM114-Status: GOOD ( 18.62 ) 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 Sat, Oct 01, 2022 at 04:18:27PM CEST, kuba@kernel.org wrote: >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? There were good reasons why to use netlink, many of those. I find it redundant to list them here. >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. Sure, what what are the odds. > >> 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. Yeah, but still. For sysfs, you don't need any app. Just saying. > >> 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 :/ No problem. I don't mind one bit, don't get me wrong :) I just pointed out alternative. > >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. I don't know anything about any politics. I don't care about it at all to be honest. You know me :) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel