Received: by 2002:a05:6358:111d:b0:dc:6189:e246 with SMTP id f29csp376633rwi; Wed, 2 Nov 2022 13:02:42 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5JWBdYJe+jxNhx63ApNQv66a/bNOKhiOqQLv7dr69YnhsUdLegPDLwMXWdT3JN4XAlAYxl X-Received: by 2002:a17:902:f303:b0:186:a478:3b3b with SMTP id c3-20020a170902f30300b00186a4783b3bmr26945005ple.73.1667419362499; Wed, 02 Nov 2022 13:02:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1667419362; cv=none; d=google.com; s=arc-20160816; b=maIcTEiw27p4xRnjJZu/P0nrDYmyKulIQ3CJtNYbuLfuRSANoGnXKu1qHu4otSCPGR r8QhhQl4nyQD2lvgeV6g54qE226tc1p3h2iFd4WMjo83YkOwoEwlltWykUXb4mdN0ndg 3erZj0M/lGlvRJcqSUrzruN08C1unzHNlIC2TGNo/IxX//4eNRagmlvRvOQyqi25fuwK 1Uu6M5qsDBJY3U1TYvripVE8uunvOTn3XQwYHDofHp2guTNpL8xEJYjyHa96KF0cWMxq QpM30cE8JCkHYdcBPnRq1QutehTqfwdOHzcTQvp5UrxyOlCTCyEbB0fORXCRbbPqkEjb Xz4A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=gCpZxPzJd+1sBX5l1tHkcyVdhruMt/YD9lsoFJVW2hI=; b=YoTjK1nUotooDkB1GdA+5VSh7//36ZB6dryYYHTb470p+7n9uj88F8lxo/AC+cPiHW c/g3qIUNjUrGIW3rLiUQPqGFU8m/PZw9pTNr5/WwH1qJZpfmSeSjRVvwGMQY2bHLzG0L MG16ziAQm/3LwDkoWtkjaY8IRL4BVZ5V8F1XUyiTcQw4IyDhgi1RSozMpLqzOcn3A7Y3 0NOoHfp5aA8BxUpVusokjUWkNUaw6PquCOYzMiQ9UW1tUjyFHVWBfFiSutlghLJrchXT esCgLRI5EGbYl9aL5+NkeEfSMUaYqZFhSMYOg9jhTRd/84oWHyCcYih0uU8mUEaoUoDh XrsQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=bvxGXj7U; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c11-20020a62f84b000000b0056bca56b096si18292125pfm.321.2022.11.02.13.02.27; Wed, 02 Nov 2022 13:02:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=bvxGXj7U; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231331AbiKBSTl (ORCPT + 98 others); Wed, 2 Nov 2022 14:19:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45136 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231289AbiKBSTj (ORCPT ); Wed, 2 Nov 2022 14:19:39 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6BB372F016; Wed, 2 Nov 2022 11:19:38 -0700 (PDT) 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 28106B82429; Wed, 2 Nov 2022 18:19:37 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id AA534C43145; Wed, 2 Nov 2022 18:19:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1667413175; bh=ByC8WrBr65R1FHnYm1bG2iBmanhGcnHFrTlrNhwgv9I=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=bvxGXj7UcpjIlwlOO3Si5m4Boq+XXLd0gL/TvGFf/LtJd7Ph0QNwzv13RXPo4nFKr ux+mAfYvQZ/T7HQuv3qWrU6rgoxXhUGtiadfAHIr0Y0BDKg+V4qPJOa6zg6Y0nURWT mc5Jz/XC/APTUiCVdkfMmCpLeRNuhDQfnHmM9TLEj/6AmuLeyd3OUIfnVHqaMWDTPV 2EWLYW0AsKCy/tlIw/R7B1zrLIpup7xuibv+D33vs48IO+QFfuSvcFSPSPR1IS0fi+ GwQEK83D1BZu+duczaPKs5sLPZQXDq42lajbd7jhwg46rDbfVReAVp54hweOjkdMbS z4C0cnzwlZRHQ== Received: by mail-lf1-f49.google.com with SMTP id g7so29602180lfv.5; Wed, 02 Nov 2022 11:19:35 -0700 (PDT) X-Gm-Message-State: ACrzQf26isgZVdhYIpzg83U+PK+DGwyS0WoY1zDDPSoGrQChapRDA75Y uF87BPsvwBYIUygWi0mYOEiYK79q5Q4SSmBZAw== X-Received: by 2002:a19:5048:0:b0:4b1:3856:e422 with SMTP id z8-20020a195048000000b004b13856e422mr2174132lfj.368.1667413173675; Wed, 02 Nov 2022 11:19:33 -0700 (PDT) MIME-Version: 1.0 References: <20221101095156.30591-1-billy_tsai@aspeedtech.com> <20221101095156.30591-2-billy_tsai@aspeedtech.com> <20221101184033.GA1879756-robh@kernel.org> In-Reply-To: From: Rob Herring Date: Wed, 2 Nov 2022 13:19:24 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [v2 1/3] dt-bindings: Add bindings for aspeed pwm-tach. To: Billy Tsai Cc: "jdelvare@suse.com" , "linux@roeck-us.net" , "joel@jms.id.au" , "andrew@aj.id.au" , "lee.jones@linaro.org" , "thierry.reding@gmail.com" , "u.kleine-koenig@pengutronix.de" , "p.zabel@pengutronix.de" , "linux-hwmon@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-aspeed@lists.ozlabs.org" , "linux-kernel@vger.kernel.org" , "linux-pwm@vger.kernel.org" , BMC-SW , "garnermic@meta.com" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-8.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 1, 2022 at 10:21 PM Billy Tsai wrote: > > Hi Rob, > > On 2022/11/2, 2:40 AM, "Rob Herring" wrote: > > > On Tue, Nov 01, 2022 at 05:51:54PM +0800, Billy Tsai wrote: > > > This patch adds device binding for aspeed pwm-tach device which is a > > > multi-function device include pwm and tach function and pwm/tach device > > > bindings which should be the child-node of pwm-tach device. > > > > > > Signed-off-by: Billy Tsai > > > --- > > > .../bindings/hwmon/aspeed,ast2600-tach.yaml | 48 ++++++++++++ > > > .../bindings/mfd/aspeed,ast2600-pwm-tach.yaml | 76 +++++++++++++++++++ > > > .../bindings/pwm/aspeed,ast2600-pwm.yaml | 64 ++++++++++++++++ > > > 3 files changed, 188 insertions(+) > > > create mode 100644 Documentation/devicetree/bindings/hwmon/aspeed,ast2600-tach.yaml > > > create mode 100644 Documentation/devicetree/bindings/mfd/aspeed,ast2600-pwm-tach.yaml > > > create mode 100644 Documentation/devicetree/bindings/pwm/aspeed,ast2600-pwm.yaml > > > I'm pretty sure I've said this before, but I'm not taking more fan > > controller bindings without comming up with a common binding. Please see > > this series[1] and help ensure it meets your needs. > > > Rob > > > [1] 20221013094838.1529153-2-Naresh.Solanki@9elements.com /">https://lore.kernel.org/all/20221013094838.1529153-2-Naresh.Solanki@9elements.com/ > > The link you provide doesn't meet my needs. This is fan binding. A PWM and Tach controller is for fans, no? As I said, contribute to it so that it does meet your needs. > As I told before > "This patch doesn't use to binding the fan control h/w. It is used to binding the two independent h/w blocks. > One is used to provide pwm output and another is used to monitor the speed of the input." > My patch is used to point out that the pwm and the tach is the different function and don't need to > bind together. You can not only combine them as the fan usage but also treat them as the individual module for > use. For example: the pwm can use to be the beeper (pwm-beeper.c), the tach can be used to monitor any device's speed. That all sounds like requirements that you have which you should ensure the fan binding can support. I've already said to use the PWM binding in the fan binding exactly for the purpose of hooking up the PWMs to other things. Whether the tach controller is useful for something other than fans, I don't know. Seems less likely. The max6639 also has a tach controller. So if other uses are possible for you, then it could be possible for any other h/w like the max6639. Rob