All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petko Manolov <petko.manolov@konsulko.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	dinguyen@kernel.org
Subject: Re: [PATCH v2 1/1] ARM: dts: draeger: Add socfpga devicetree for Draeger's M48 board.
Date: Wed, 9 Sep 2026 13:07:09 +0300	[thread overview]
Message-ID: <20260909100709.GA20988@carbon.k.g> (raw)
In-Reply-To: <3dbe92ee-805f-496d-9a7d-94c837e674b5@kernel.org>

On 26-09-09 08:36:23, Krzysztof Kozlowski wrote:
> On 08/09/2026 13:10, Petko Manolov wrote:
> > +
> > +	chosen {
> > +		bootargs = "earlyprintk";
> 
> That's not a mainline suitable argument, drop.

Well, i'm a bit confused.  These files in arch/arm/boot/dts/intel/socfpga/

socfpga_arria5_socdk.dts
socfpga_cyclone5_de0_nano_soc.dts
socfpga_cyclone5_vining_fpga.dts
socfpga_arria10_socdk.dtsi
socfpga_cyclone5_socdk.dts
socfpga_cyclone5_chameleon96.dts
socfpga_cyclone5_socrates.dts
socfpga_cyclone5_sodia.dts
socfpga_cyclone5_sockit.dts

all have:

        chosen {
                bootargs = "earlyprintk";
                stdout-path = "serial0:115200n8";
        };

Is this some sort of legacy that isn't accepted in modern days or is it
something else?


		Petko

  parent reply	other threads:[~2026-09-09 10:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 11:09 [PATCH v2 0/1] ARM: dts: draeger: Add socfpga devicetree for Draeger's M48 board Petko Manolov
2026-09-08 11:10 ` [PATCH v2 1/1] " Petko Manolov
2026-09-08 11:17   ` sashiko-bot
2026-09-09  6:36   ` Krzysztof Kozlowski
2026-09-09  6:50     ` Petko Manolov
2026-09-09  6:52       ` Krzysztof Kozlowski
2026-09-09 10:07     ` Petko Manolov [this message]
2026-09-09 10:14       ` Krzysztof Kozlowski
2026-09-09 11:16         ` Petko Manolov

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=20260909100709.GA20988@carbon.k.g \
    --to=petko.manolov@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.