Devicetree
 help / color / mirror / Atom feed
From: "Nazle Asmade, Muhammad Nazim Amirul" <muhammad.nazim.amirul.nazle.asmade@altera.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "dinguyen@kernel.org" <dinguyen@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: socfpga: agilex7-gen2: Add initial device tree
Date: Wed, 24 Jun 2026 11:22:42 +0000	[thread overview]
Message-ID: <568e8d6c-c3a7-4e2b-9bde-3999e5043426@altera.com> (raw)
In-Reply-To: <fa79f704-6c04-4052-9625-d371976c14f7@kernel.org>

On 24/6/2026 6:26 pm, Krzysztof Kozlowski wrote:
> On 24/06/2026 12:17, Nazle Asmade, Muhammad Nazim Amirul wrote:
>>> SoC without any interface, serial or storage or network, is close to
>>> useless one.
>>>
>>> I don't see a point in having it in mainline. Serial is usually ABSOLUTE
>>> minimum.
>>>
>>> Best regards,
>>> Krzysztof
>>>
>> Hi Krzysztof,
>>
>> Thank you for the review and fast response!
>>
>> I ran both dt_binding_check and dtbs_check (with CHECK_DTBS=y) locally —
>> both passed without errors. Could you clarify which specific test you
>> believe is failing?
> 
> I would expect simple-bus schema warning or W=1, because node is placed
> outside of soc@, but maybe there is no such.
 > >>
>> Regarding "MMIO goes to MMIO" — are you referring to the GIC
> 
> Comments are placed in very specific and intentional place. Please read
> guides how mailing list in-line review works before posting patches.
Apologies on this matter.>
>> (interrupt-controller@7000000) being placed at the root level instead of
>> under the soc bus node?
>>
>> Regarding the serial console — the platform clock driver is not yet
>> upstream, so the UART depends on clkmgr. Would adding the UART with
>> clock-frequency be acceptable as an interim solution?
> 
> Add complete working serial. Why can't you use fixed placeholder clock?
> There are probably multiple ways to solve it, not necessary
> clock-frequency and I do not even remember if clock-frequency is allowed.
Will add a UART node with a fixed-clock placeholder>
> But if you cannot bring serial, then my comment stays valid: this is
> unusable upstream thus is not ready to be posted and merged.
> 
> Best regards,
> Krzysztof
Sorry I had to reply again to this thread due to not including all 
recipient just now. Also one thing to mention, this patch actually a V1 
version and latest should be v2 but it is just a device renaming change 
on the latest one so the comment still valid. Will send out v3 once it 
is ready! Thanks Krzysztof!

BR,
Nazim


      reply	other threads:[~2026-06-24 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 11:17 [PATCH 0/2] arm64: dts: socfpga: agilex7-gen2: Add initial device tree support muhammad.nazim.amirul.nazle.asmade
2026-06-23 11:17 ` [PATCH 1/2] dt-bindings: arm: altera: Add Agilex7 Gen2 SoCFPGA compatible strings muhammad.nazim.amirul.nazle.asmade
2026-06-24  7:55   ` Krzysztof Kozlowski
2026-06-23 11:17 ` [PATCH 2/2] arm64: dts: socfpga: agilex7-gen2: Add initial device tree muhammad.nazim.amirul.nazle.asmade
2026-06-23 11:28   ` sashiko-bot
2026-06-24  7:57   ` Krzysztof Kozlowski
2026-06-24 10:17     ` Nazle Asmade, Muhammad Nazim Amirul
2026-06-24 10:26       ` Krzysztof Kozlowski
2026-06-24 11:22         ` Nazle Asmade, Muhammad Nazim Amirul [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=568e8d6c-c3a7-4e2b-9bde-3999e5043426@altera.com \
    --to=muhammad.nazim.amirul.nazle.asmade@altera.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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