public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: niravkumar.l.rabara@intel.com, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] ARM: dts: socfpga: remove syscon compatible string for sysmgr node
Date: Mon, 10 Feb 2025 18:06:46 -0600	[thread overview]
Message-ID: <d78ae428-6139-426b-bde9-e3ce5a4008ac@kernel.org> (raw)
In-Reply-To: <45276881-11de-47c9-aa9c-488df537a596@kernel.org>

On 2/10/25 16:29, Dinh Nguyen wrote:
> On 1/17/25 09:42, niravkumar.l.rabara@intel.com wrote:
>> From: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
>>
>> The SoCFPGA System Manager(sysmgr) dt bindings do not use the syscon
>> compitible, nor does the Linux system manager driver rely on it.
>> Remove "syscon" for Arria5, Arria10 and Cyclon5 sysmgr node and fixed
>> dtbs_check warnings like:
>>
>> socfpga_arria5_socdk.dtb: sysmgr@ffd08000: compatible: 'oneOf' 
>> conditional failed, one must be fixed:
>>     ['altr,sys-mgr', 'syscon'] is too long
>>     'altr,sys-mgr-s10' was expected
>>     'altr,sys-mgr' was expected
>>     from schema $id: 
>> http://devicetree.org/schemas/soc/altera/altr,sys-mgr.yaml#
>>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Closes: 
>> https://lore.kernel.org/oe-kbuild-all/202501102323.Xnte2yhi-lkp@intel.com/
>> Signed-off-by: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
>> ---
>>   arch/arm/boot/dts/intel/socfpga/socfpga.dtsi         | 2 +-
>>   arch/arm/boot/dts/intel/socfpga/socfpga_arria10.dtsi | 2 +-
>>   2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/intel/socfpga/socfpga.dtsi 
>> b/arch/arm/boot/dts/intel/socfpga/socfpga.dtsi
>> index 35be14150f41..f124fb72e260 100644
>> --- a/arch/arm/boot/dts/intel/socfpga/socfpga.dtsi
>> +++ b/arch/arm/boot/dts/intel/socfpga/socfpga.dtsi
>> @@ -853,7 +853,7 @@ spi1: spi@fff01000 {
>>           };
>>           sysmgr: sysmgr@ffd08000 {
>> -            compatible = "altr,sys-mgr", "syscon";
>> +            compatible = "altr,sys-mgr";
>>               reg = <0xffd08000 0x4000>;
>>           };
>> diff --git a/arch/arm/boot/dts/intel/socfpga/socfpga_arria10.dtsi 
>> b/arch/arm/boot/dts/intel/socfpga/socfpga_arria10.dtsi
>> index 6b6e77596ffa..015120fb4b02 100644
>> --- a/arch/arm/boot/dts/intel/socfpga/socfpga_arria10.dtsi
>> +++ b/arch/arm/boot/dts/intel/socfpga/socfpga_arria10.dtsi
>> @@ -792,7 +792,7 @@ scu: snoop-control-unit@ffffc000 {
>>           };
>>           sysmgr: sysmgr@ffd06000 {
>> -            compatible = "altr,sys-mgr", "syscon";
>> +            compatible = "altr,sys-mgr";
>>               reg = <0xffd06000 0x300>;
>>               cpu1-start-addr = <0xffd06230>;
>>           };
> 
> Did you test this patch on actual hardware? Unless something has changed 
> in the system manager driver, this will probably cause the system hang.
>

Actually, it will not fail to boot, but you will see SD/MMC fail if the 
bootloader did not set the clk-phase correctly, or you booted from 
another source not SD/MMC. The SD/MMC driver uses syscon to get access 
to the system manager to set it's clk-phase.

Dinh

Dinh


  reply	other threads:[~2025-02-11  0:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 15:42 [PATCH] ARM: dts: socfpga: remove syscon compatible string for sysmgr node niravkumar.l.rabara
2025-02-10 22:29 ` Dinh Nguyen
2025-02-11  0:06   ` Dinh Nguyen [this message]
2025-02-11  3:18     ` Rabara, Niravkumar L
2025-02-11  4:14       ` Dinh Nguyen
2025-02-11 12:18         ` Rabara, Niravkumar L
2025-02-11 12:24           ` Dinh Nguyen
2025-02-11 12:37             ` Rabara, Niravkumar L
2025-02-11 12:57               ` Dinh Nguyen
2025-02-11 13:48                 ` Rabara, Niravkumar L
2025-02-14 13:01                   ` Dinh Nguyen

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=d78ae428-6139-426b-bde9-e3ce5a4008ac@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.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