mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julien Massot <julien.massot@collabora.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski	 <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	kernel@collabora.com,  linux-renesas-soc@vger.kernel.org,
	devicetree@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] arm64: renesas: add initial support for MYIR Remi Pi
Date: Fri, 07 Feb 2025 08:16:33 +0100	[thread overview]
Message-ID: <950770a2406dd9ac3163e677c6d887d06df5b8c6.camel@collabora.com> (raw)
In-Reply-To: <CAMuHMdXAS6pnNcT=A7i9La22tbDXYf7EKqbJzHuK2ze2gf6cgg@mail.gmail.com>

Hi Geert, Krzysztof,

> On Fri, 31 Jan 2025 at 10:58, Julien Massot <julien.massot@collabora.com> wrote:
> > Add basic support for the MYIR Remi Pi (based on r9a07g044l2):
> >  - UART
> >  - i2c
> >  - emmc
> >  - USB host
> >  - HDMI output
> >  - Ethernet
> > 
> > Signed-off-by: Julien Massot <julien.massot@collabora.com>
> 
> Thanks for the update!
> 
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/renesas/r9a07g044l2-remi-pi.dts
> > @@ -0,0 +1,351 @@
> 
> > +/ {
> > +       model = "MYIR Tech Limited Remi Pi MYB-YG2LX-REMI";
> > +       compatible = "myir,remi-pi", "renesas,r9a07g044l2", "renesas,r9a07g044";
> > +
> > +       aliases {
> > +               ethernet0 = &eth0;
> > +               ethernet1 = &eth1;
> > +
> > +               i2c0 = &i2c0;
> > +               i2c1 = &i2c1;
> > +               i2c2 = &i2c2;
> > +               i2c3 = &i2c3;
> > +
> > +               mmc0 = &sdhi0;
> > +
> > +               serial0 = &scif0;
> > +               serial3 = &scif3;
> 
> Wasn't the plan to drop scif3, so it can be used by an RTOS running
> on the Cortex-A33 core?
Sorry, indeed I forgot scif3 removal. I don't see a reason to borrow the
Cortex-A33 scif.

> 
> > +               serial4 = &scif4;
> > +       };
> > +
> > +       chosen {
> > +               stdout-path = "serial0:115200n8";
> > +       };
> > +
> > +       memory@48000000 {
> > +               device_type = "memory";
> > +               /* first 128MB is reserved for secure area. */
> > +               reg = <0x0 0x48000000 0x0 0x38000000>;
> > +       };
> > +
> > +       reg_5p0v: regulator-5p0v {
> 
> > +       reg_3p3v: regulator-3p3v {
> 
> > +       reg_1p8v: regulator-1p8v {
> 
> > +       reg_1p1v: regulator-vdd-core {
> 
> > +       hdmi-out {
> 
> More sorting work to do...
> 
> Ok, I will keep in mind for the next time.
> 
> 
> > +};
> 
> > +       sdhi0_pins: sd0 {
> > +               sd0_data {
> > +                       pins = "SD0_DATA0", "SD0_DATA1", "SD0_DATA2", "SD0_DATA3",
> > +                              "SD0_DATA4", "SD0_DATA5", "SD0_DATA6", "SD0_DATA7";
> > +                       power-source = <1800>;
> > +               };
> > +
> > +               sd0_ctrl {
> 
> Here, too. Plus the underscores reported by Krzysztof.
Ok, no underscore in node names, even for the pins definition.

> 
> > +                       pins = "SD0_CLK", "SD0_CMD";
> > +                       power-source = <1800>;
> > +               };
> > +
> > +               sd0_rst {
> > +                       pins = "SD0_RST#";
> > +                       power-source = <1800>;
> > +               };
> > +       };
> 
> I fixed the style issues locally, so if you can confirm or deny the removal
> of scif3, I can fix that while applying.
Confirmed, we should not enable scif3.


Thanks
-- 
Julien

  reply	other threads:[~2025-02-07  7:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31  9:57 [PATCH v3 0/2] Add basic " Julien Massot
2025-01-31  9:57 ` [PATCH v3 1/2] dt-bindings: soc: renesas: Document MYIR Remi Pi board Julien Massot
2025-02-07  8:45   ` Geert Uytterhoeven
2025-01-31  9:58 ` [PATCH v3 2/2] arm64: renesas: add initial support for MYIR Remi Pi Julien Massot
2025-01-31 10:22   ` Krzysztof Kozlowski
2025-02-06 11:16   ` Geert Uytterhoeven
2025-02-07  7:16     ` Julien Massot [this message]
2025-02-07  8:45       ` 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=950770a2406dd9ac3163e677c6d887d06df5b8c6.camel@collabora.com \
    --to=julien.massot@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=kernel@collabora.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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®