All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Steffen Pengel <spengel@de.adit-jv.com>,
	Eugeniu Rosca <erosca@de.adit-jv.com>,
	Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [PATCH 2/2] arm64: dts: renesas: r8a77961: ulcb-kf: Initial device tree
Date: Thu, 29 Oct 2020 17:32:13 +0100	[thread overview]
Message-ID: <20201029163213.GA12422@lxhi-065.adit-jv.com> (raw)
In-Reply-To: <CAMuHMdX5pCtR-LMbuSJQvDNyVOwcipt7zZOF3c3J-d-Bq98NQg@mail.gmail.com>

Hi Geert,

On Thu, Oct 29, 2020 at 03:09:10PM +0100, Geert Uytterhoeven wrote:
> On Thu, Oct 29, 2020 at 2:38 PM Eugeniu Rosca <erosca@de.adit-jv.com> wrote:
> > Create a dedicated DTB for M3-ES3.0 + ULCB + Kingfisher combo.
> > Inspire from the pre-existing ULCB-KF device trees:
> >
> > $ ls -1 arch/arm64/boot/dts/renesas/*ulcb-kf.dts
> > arch/arm64/boot/dts/renesas/r8a77950-ulcb-kf.dts
> > arch/arm64/boot/dts/renesas/r8a77951-ulcb-kf.dts
> > arch/arm64/boot/dts/renesas/r8a77960-ulcb-kf.dts
> > arch/arm64/boot/dts/renesas/r8a77965-ulcb-kf.dts
> >
> > Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>
> 
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> i.e. will queue in renesas-devel for v5.11.

Thank you for the prompt review!

> > +       compatible = "shimafuji,kingfisher", "renesas,m3ulcb",
> > +                    "renesas,r8a77961";
> 
> Can you please send a patch to add this combo to
> Documentation/devicetree/bindings/arm/renesas.yaml?

I would happily do so if you resolve below concerns.

Since the inception of the Kingfisher extension board description in
v4.15-rc1 commit 5418a900412699 ("arm: shmobile: Document Kingfisher
board DT bindings"), nobody attempted describing the SoC+ULCB+KF
combinations in spite of four of such DT configurations being actively
used and maintained, i.e. r8a779{50,51,60,65}-ulcb-kf.

So, if we start documenting the r8a77961-ulcb-kf combo as a board, this
raises below questions:

  => should the missing 4 SoC+ULCB+KF instances be documented as well?
  => should a new compatible string be created for each such HW combo,
     e.g. "renesas,<soc>-ulcb-kf"?

I feel none of the above is really needed, based on the patterns
established in Documentation/devicetree/bindings/arm/renesas.yaml,
but I might be wrong. Thoughts/suggestions appreciated.

IMHO one thing which is certainly worth clarifying and fixing is the
KF revision currently documented in renesas.yaml, i.e. M03.

Shimafuji released at least M04, M05 and M06 revisions of KF (nicely
compared at https://elinux.org/R-Car/Boards/Kingfisher#Change_point).

The question is, does the community intend to support M03 through M06
(in which case all of them might need an entry in the documentation) or
anything which is earlier than M06 has to be considered deprecated (in
which case renesas.yaml would need a simple s/M03/M06/ update)?

-- 
Best regards,
Eugeniu Rosca

  reply	other threads:[~2020-10-29 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 13:37 [PATCH 1/2] arm64: dts: renesas: r8a77961: Add CAN{0,1} placeholder nodes Eugeniu Rosca
2020-10-29 13:37 ` [PATCH 2/2] arm64: dts: renesas: r8a77961: ulcb-kf: Initial device tree Eugeniu Rosca
2020-10-29 14:09   ` Geert Uytterhoeven
2020-10-29 16:32     ` Eugeniu Rosca [this message]
2020-10-29 18:23       ` Geert Uytterhoeven
2020-10-30  9:07         ` Eugeniu Rosca
2020-10-30  9:14           ` Geert Uytterhoeven
2020-10-29 14:09 ` [PATCH 1/2] arm64: dts: renesas: r8a77961: Add CAN{0,1} placeholder nodes Geert Uytterhoeven

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=20201029163213.GA12422@lxhi-065.adit-jv.com \
    --to=erosca@de.adit-jv.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=roscaeugeniu@gmail.com \
    --cc=spengel@de.adit-jv.com \
    /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.