[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABTCjFAO=iLauq37M7LOXOmrgAnPxh210bcoujUsL4zEC3634A@mail.gmail.com>
Date: Mon, 15 Sep 2025 18:46:22 +0300
From: Dzmitry Sankouski <dsankouski@...il.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: Chanwoo Choi <cw00.choi@...sung.com>, Krzysztof Kozlowski <krzk@...nel.org>, Lee Jones <lee@...nel.org>,
Rob Herring <robh@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: max77705: add interrupt-controller node
пн, 15 сент. 2025 г. в 10:49, Konrad Dybcio <konrad.dybcio@....qualcomm.com>:
>
> > + The driver implements an interrupt controller for the sub devices.
> > + The interrupt number mapping is as follows
> > + 0 - charger
> > + 1 - topsys
> > + 2 - fuelgauge
> > + 3 - usb type-c management block.
>
> The MFD driver registers one more interrupt, and these don't seem
> to be what you say here:
>
> static const struct regmap_irq max77705_topsys_irqs[] = {
> { .mask = MAX77705_SYSTEM_IRQ_BSTEN_INT, },
> { .mask = MAX77705_SYSTEM_IRQ_SYSUVLO_INT, },
> { .mask = MAX77705_SYSTEM_IRQ_SYSOVLO_INT, },
> { .mask = MAX77705_SYSTEM_IRQ_TSHDN_INT, },
> { .mask = MAX77705_SYSTEM_IRQ_TM_INT, },
> };
MAX77705_SYSTEM_IRQ_TM_INT(and others you mentioned) is a part of 'topsys' irqs,
which is kinda MFD own irqs. They are unused at the moment.
See also [max77705 rework interrupt patches](https://lkml.org/lkml/2025/8/31/27)
--
Best regards and thanks for review,
Dzmitry
Powered by blists - more mailing lists