mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Shengyu <wiagn233@outlook.com>
To: Conor Dooley <conor@kernel.org>
Cc: Qu Shengyu <wiagn233@outlook.com>,
	"ganboing@gmail.com" <ganboing@gmail.com>,
	"kernel@esmil.dk" <kernel@esmil.dk>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org"
	<krzysztof.kozlowski+dt@linaro.org>,
	"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
	"palmer@dabbelt.com" <palmer@dabbelt.com>,
	"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
	"lee@kernel.org" <lee@kernel.org>,
	"andre.przywara@arm.com" <andre.przywara@arm.com>,
	"jernej.skrabec@gmail.com" <jernej.skrabec@gmail.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v1] riscv: dts: starfive: Remove PMIC interrupt info for Visionfive 2 board
Date: Tue, 5 Mar 2024 23:24:10 +0000	[thread overview]
Message-ID: <TY3P286MB2611ACAF9F648ACA2BE157FE98222@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20240305-macarena-fiber-f2460d371150@spud>

Hi Conor,

Thanks for reply. I’m sorry for this, but my distro’s dt-schema
is too old to run dtbs-check. Will fix in next version.

Best regards

> 在 2024年3月6日,03:41,Conor Dooley <conor@kernel.org> 写道:
> 
> On Wed, Mar 06, 2024 at 01:11:50AM +0800, Shengyu Qu wrote:
>> Since commit b2cb2ae22278f1918f7526b89760ee00b4a81393 ("mfd: axp20x:
>> Generalise handling without interrupt"), interrupt info part for the
>> AXP15060 PMIC is not needed anymore for Statfive Visionfive 2 board.
>> And this would cause kernel to try to enable interrupt line 0, which is
>> not expected. So delete this part from device tree.
> 
> interrupt-controller/#interrupt-cells are required properties, you can't
> delete them. If you ran dtbs_check you'd see that it complains about
> this patch.
> 
> If you just remove the interrupts property, what happens?
> 
>> Cc: stable@vger.kernel.org
>> Fixes: b2cb2ae22278 ("mfd: axp20x: Generalise handling without interrupt")
> 
> This Fixes tag cannot be right, a dts patch cannot fix a driver. The dts
> patch that incorrectly said this used interrupt 0 is what should be in the
> Fixes tag.
> 
> Thanks,
> Conor.
> 
>> Reported-by: Bo Gan <ganboing@gmail.com>
> 
> Closes: https://lore.kernel.org/linux-riscv/c8b6e960-2459-130f-e4e4-7c9c2ebaa6d3@gmail.com/
> 
>> Signed-off-by: Shengyu Qu <wiagn233@outlook.com>
>> ---
>> arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi | 3 ---
>> 1 file changed, 3 deletions(-)
>> 
>> diff --git a/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi b/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi
>> index b89e9791efa7..6bebabe3fa37 100644
>> --- a/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi
>> +++ b/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi
>> @@ -189,9 +189,6 @@ &i2c5 {
>>    axp15060: pmic@36 {
>>        compatible = "x-powers,axp15060";
>>        reg = <0x36>;
>> -        interrupts = <0>;
>> -        interrupt-controller;
>> -        #interrupt-cells = <1>;
>> 
>>        regulators {
>>            vcc_3v3: dcdc1 {
>> --
>> 2.39.2
>> 

      reply	other threads:[~2024-03-05 23:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 17:11 Shengyu Qu
2024-03-05 19:41 ` Conor Dooley
2024-03-05 23:24   ` Qu Shengyu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=TY3P286MB2611ACAF9F648ACA2BE157FE98222@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM \
    --to=wiagn233@outlook.com \
    --cc=andre.przywara@arm.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ganboing@gmail.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=kernel@esmil.dk \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®