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 E2F32C282E7 for ; Fri, 12 Aug 2022 18:53:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238995AbiHLSxY (ORCPT ); Fri, 12 Aug 2022 14:53:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54784 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238931AbiHLSxX (ORCPT ); Fri, 12 Aug 2022 14:53:23 -0400 Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5AADF2AC4D for ; Fri, 12 Aug 2022 11:53:21 -0700 (PDT) Received: by mail-lf1-x131.google.com with SMTP id c17so2478373lfb.3 for ; Fri, 12 Aug 2022 11:53:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=H2hFHauRZ+2L1/8Jn5Q0JcmOqrApxd8gqlCGFKCdAM4=; b=PBfBUmCCqcFOkJncUdtapjWauTPUiKTDxV8oZ1lYEW8xc3KN7Gru9WcRttJJrZKU1v puewIC/RAT4riMzrbYZNMmChbVUy0NVo4m3lT43eIzZTcMVjUMT0/X5alIayZosShy4a A2DBnUKi2Oa3ha/9X7/FiezFCFP3q9i/vcYoE/Mi3Y4AdJPYaYItnAvzdaooEn9rDIZN 7pAj20HghfJsz2LY4CVKj1QhkKHqoUmLnisWbFU4dQIds7kZm8k1S6Yg29dGSpwT2wDf ivyfgtn7IX0vPdhw51VB0i1Mn8hENHdS9HJxKH7sP6kJG94PPgGibl4u+FRAAJc+Wg71 YtFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=H2hFHauRZ+2L1/8Jn5Q0JcmOqrApxd8gqlCGFKCdAM4=; b=4TmiGnF/MuUMMMSRFjkuoMSuDml9j/PlLT0ONISL0t4XpDew/flhRKdjYV7WX4QBA5 BV06UVwE6WI7+Fn7JDYdps+ay1YaoEROSzH7l2gRfLzR0EjxWCmKmzD1MWZ0P4VRGW+h 1FrEDM+Wdzrvy2y/KX5ULyhRsINhx63G6s+Tj+2CZqkOy530gbMYYPFiX7dAkT1khwKD 6ZaABHi4ODm1YzkVbDxUgp+ZE95nvvR/YVzr+RqYQdo25sPTwxQoFUSvdu71XSGOGTuQ 6ZFoCxs6NbJclT9jlDxm0HZkqFkoJEVZsJJrt8LvIMG+Rjs4fxNwooogs3H/2rskVA2z OGSQ== X-Gm-Message-State: ACgBeo1qcomFsfGetjHiVttPJw5eUC4VNeuCObufq8RLUueXUXGiUIMy PSlS/Byf90Kmq7ypq0ECTUOi4g== X-Google-Smtp-Source: AA6agR6ZIpyoLa852PCDDPN1ueyFqhPzbfJsN8zaQTOoB7GiCdBw7o8HRvVEUWrz3UjuDNBYcfEFlw== X-Received: by 2002:ac2:4d18:0:b0:48b:4a2d:a378 with SMTP id r24-20020ac24d18000000b0048b4a2da378mr1611866lfi.304.1660330399661; Fri, 12 Aug 2022 11:53:19 -0700 (PDT) Received: from [192.168.1.39] ([83.146.140.105]) by smtp.gmail.com with ESMTPSA id u9-20020ac251c9000000b0048b003c4bf7sm298508lfm.169.2022.08.12.11.53.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 12 Aug 2022 11:53:19 -0700 (PDT) Message-ID: Date: Fri, 12 Aug 2022 21:53:15 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Subject: Re: [PATCH 1/2] dt-bindings: power: supply: Add Richtek RT9471 battery charger Content-Language: en-US To: ChiYuan Huang Cc: Rob Herring , Krzysztof Kozlowski , Sebastian Reichel , =?UTF-8?B?5ri45a2Q6aao?= , cy_huang , alinayu829@gmail.com, Linux PM , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , lkml References: <1660225318-4063-1-git-send-email-u0084500@gmail.com> <1660225318-4063-2-git-send-email-u0084500@gmail.com> <3cae9d60-4012-1dfd-abd9-4d0b9379e6bb@linaro.org> <40261b95-637a-1304-2e06-8c8ff7fc377b@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 12/08/2022 19:05, ChiYuan Huang wrote: >> It's the same usage like as TI charger. >>>> >>>> For charger driver, does it mean legacy IRQ handler is more preferred? >>> >>> Who is the consumer of these interrupts? Can you show the DTS with the >>> interrupt consumer? >>> > Sorry, I forget to reply this question. > Some battery driver may need to know the 'full', 'recharge' , 'ieoc' status. > The usage will be like as below > > battery { > interrupts-extended = <&rt9471_chg 2 0>, <&rt9471_chg 3 0>, &(rt9471_chg 5 0>; > interrupt-names = "chg-done", "chg-recharge", "chg-ieoc"; > }; > > Some gauge HW needs this information to enhance the battery capacity accuracy. Other supply stack pieces do it via supplies (supplied to/from in include/linux/power_supply.h) and reporting power_supply_changed(). With such explanation, your device is an interrupt source, but it is not an interrupt controller. If your device is interrupt controller, it means someone routes the interrupt line to your device. Physical line. Best regards, Krzysztof