From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Rabara, Niravkumar L" <niravkumar.l.rabara@intel.com>,
Dinh Nguyen <dinguyen@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: lkp <lkp@intel.com>
Subject: Re: [PATCH] arm64: dts: socfpga: stratix10_swvp: remove invalid sysmgr properties
Date: Fri, 10 Jan 2025 13:56:31 +0100 [thread overview]
Message-ID: <a4f38646-df2b-4f58-afc6-399e58b29c9f@kernel.org> (raw)
In-Reply-To: <BL3PR11MB6532C0F5634AC46C04B78733A21C2@BL3PR11MB6532.namprd11.prod.outlook.com>
On 10/01/2025 13:39, Rabara, Niravkumar L wrote:
>>> &sysmgr {
>>> reg = <0xffd12000 0x1000>;
>>> - interrupts = <0x0 0x10 0x4>;
>>
>> Is this correct? Some background would be useful.
>
> stratix10_swvp.dts is for legacy Stratix10 SW Virtual Platform.
> The socfpga system manager dt binding does not include "interrupt" property
> and the existing socfpga board files does not use it for sysmgr.
> (e.g. Cyclon5/Arria10/stratix10/Agilex)
>
> Socfpga system manager drivers (altera-sysmgr.c/socfpga.c) also does not use
> interrupt property.
> The stratix10_swvp.dts has this property since beginning(unused) but
> dtbs_check warning only appeared recently when I convert system manger binding
> from txt to yaml.
All this I deduced from the change, but it still not answer about hardware.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-10 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 11:26 niravkumar.l.rabara
2025-01-10 11:36 ` Krzysztof Kozlowski
2025-01-10 12:39 ` Rabara, Niravkumar L
2025-01-10 12:56 ` Krzysztof Kozlowski [this message]
2025-01-11 5:47 ` Rabara, Niravkumar L
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=a4f38646-df2b-4f58-afc6-399e58b29c9f@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=niravkumar.l.rabara@intel.com \
--cc=robh@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®