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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BEA0AC6379F for ; Tue, 10 Jan 2023 08:15:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237748AbjAJIP3 (ORCPT ); Tue, 10 Jan 2023 03:15:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47290 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237825AbjAJIPX (ORCPT ); Tue, 10 Jan 2023 03:15:23 -0500 Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 05A8864CC for ; Tue, 10 Jan 2023 00:15:23 -0800 (PST) Received: by mail-yb1-xb29.google.com with SMTP id 194so8768047ybf.8 for ; Tue, 10 Jan 2023 00:15:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9pgLTdpvWw2skhjb4T56kILYZt+xH34j9kjUZ75HWSc=; b=VSOCSfl0vMa7Mgocmkd7GP5+VwBzlOHM8BHouJaEMVZy3NMpSZsrM66VuN2U5DNwfi OB00YI1nkp3DXd7dQqDwYZEM7eRCYImt9K8fbrCGDrCykZDarqlo3flzn+WEhxrJcfxU 7Ia1K4ut7ELQX6fW34m0gCNp7+1LbCpab9YAflvGZVXBZ9f2JLL1VPwEhj8rkkYZBkZT hGW9UDkYPWKX8ZAsI4HUbZZXkW/hQmUMyThJt+ixQ3xBv5BmkO0DRs3sZtY40jlqnLr4 eBhaKwtO3f1ZLDyr2stdrm6lcIlz3asTEVh6bI1LXn0+75sR38AHE/nOOW8+ExMBJOeS Q0uQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9pgLTdpvWw2skhjb4T56kILYZt+xH34j9kjUZ75HWSc=; b=uGYsmDjOWw6bTmGXqHpbCafKtTFMwfyuxYaap1QeBw3pYDtJ4G44+NaSLi09eqBOA7 JjtW29eigvjuhcLeIavfZkdAo/1140m94W6Ki0Cjx4v5pBY+NCybuAeRZXj3a/4UvnjW nfThzXLO5W651CLzxcHVwVjfs/LyxhwFNKyrq04IqzHEZE+Gazv73qW4f27vASwL6EcG mckXjCUy88IZ/yr7QXwKr9EAaXOhyU/eJq8xUyedTUlvnMAUq63bVaaHX8XGH5RoCzMn DnFWdy5vJk9H6suu2DjQcUGNwyeszpcSAgf0myxuueB0ra63pPVVP+K/rs4nubqVnCpV F4hw== X-Gm-Message-State: AFqh2kqxO7a5rX9Qdp6NKWUWv5r/sASecgwx6XexaCC0ojgTletD7kI1 OG4xRLr9k0CZJa7XgqHqTPKuyBEnLwVqWX0Q2Ifu8Q== X-Google-Smtp-Source: AMrXdXu72/6OnGsmGp9R8TxFpMf1pphZYj6NyaqD4j9V8BNchawfB676VHxYCeEsZkuxmSi+HAVFn+QGRomSFSGqO5A= X-Received: by 2002:a25:8e8e:0:b0:6fa:a54e:9276 with SMTP id q14-20020a258e8e000000b006faa54e9276mr5388853ybl.460.1673338522267; Tue, 10 Jan 2023 00:15:22 -0800 (PST) MIME-Version: 1.0 References: <20221215213206.56666-1-biju.das.jz@bp.renesas.com> In-Reply-To: From: Linus Walleij Date: Tue, 10 Jan 2023 09:15:11 +0100 Message-ID: Subject: Re: [PATCH v5 0/9] Add RZ/G2L POEG support To: Biju Das Cc: Drew Fustini , Andy Shevchenko , Rob Herring , Krzysztof Kozlowski , Geert Uytterhoeven , Thierry Reding , =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , "linux-renesas-soc@vger.kernel.org" , "linux-gpio@vger.kernel.org" , "devicetree@vger.kernel.org" , Chris Paterson , Biju Das , Prabhakar Mahadev Lad Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Mon, Jan 9, 2023 at 4:10 PM Biju Das wrote: > > What's wrong with using the debugfs approach Drew implemented in commit > > 6199f6becc869d30ca9394ca0f7a484bf9d598eb > > "pinctrl: pinmux: Add pinmux-select debugfs file" > > ? > > I am not sure, we supposed to use debugfs for production environment?? It depends what is meant by "production environment". If you mean a controlled environment "one-off" such as a factory line, a specific installation for a specific purpose such as a water purifier, that is very custom and hacked together for that one usecase. It will have other hacks too, so then Beagle is using debugfs in "production" if that is what you mean by "production", i.e. used to produce something. This is the same "production" use cases as used by i.e. the GPIO character device. If you mean that you are producing 6 million laptops where userspace is going to hammer this constantly, then no. In that case a real sysfs knob and ABI contract is needed. Usually vendors know which usecase their hardware is intended for, there is in my experience no unknown target audience, so which one is it in your case? > > such as a list of stuff to be exported as sysfs switches. > > Can you please elaborate? Or Point me to an example for this? Not sure what to say about that, you will have to invent something I'm afraid, good examples are in Documentation/ABI. Yours, Linus Walleij