devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v4 2/4] ARM: shmobile: add r8a7793 minimal SoC device tree
Date: Tue, 2 Jun 2015 09:27:48 +0900	[thread overview]
Message-ID: <20150602002747.GA4781@verge.net.au> (raw)
In-Reply-To: <CAO3366wm=LvYntDYBwh9AY-jpfmBF57cJhfY2A=yAk13kHg3oQ@mail.gmail.com>

On Mon, Jun 01, 2015 at 11:45:45AM +0200, Ulrich Hecht wrote:
> On Mon, Jun 1, 2015 at 11:37 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > Hi Ulrich,
> >
> > On Thu, May 28, 2015 at 5:15 PM, Ulrich Hecht
> > <ulrich.hecht+renesas@gmail.com> wrote:
> >> Minimal r8a7793 device tree including one CPU core, interrupt controllers,
> >> timers, two serial ports, and the Ethernet controller, plus the required
> >> clock descriptions.
> >
> >> --- /dev/null
> >> +++ b/arch/arm/boot/dts/r8a7793.dtsi
> >> @@ -0,0 +1,368 @@
> >
> >> +       cpus {
> >> +               #address-cells = <1>;
> >> +               #size-cells = <0>;
> >> +
> >> +               cpu0: cpu@0 {
> >> +                       device_type = "cpu";
> >> +                       compatible = "arm,cortex-a15";
> >> +                       enable-method = "renesas,r8a7793";
> >
> > I don't think we need the enable-method in a minimal tree, do we?
> 
> Nope.

Could you respin without the enable-method?

I see there is also a minor Makefile change pending for the last patch of
the series. With that and the above in place I think we should be very
close.

> >> +       clocks {
> [...]
> >> +       };
> >
> > I don't see the rationele behind keeping some mstp clocks, and others not,
> > for a miminal dtsi.
> 
> Some clocks are required by the minimal set of devices, and I did not
> want to take apart individual MSTPs because IMO it's error-prone and
> does not provide any real benefit.

My feeling is that while it would be ideal to trim things down it
this is reasonable not to do so to avoid breaking what is left.

I lean towards taking the MSTP clocks as is.

  reply	other threads:[~2015-06-02  0:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1432826157-6414-1-git-send-email-ulrich.hecht+renesas@gmail.com>
2015-05-28 15:15 ` [PATCH v4 2/4] ARM: shmobile: add r8a7793 minimal SoC device tree Ulrich Hecht
2015-06-01  9:37   ` Geert Uytterhoeven
2015-06-01  9:45     ` Ulrich Hecht
2015-06-02  0:27       ` Simon Horman [this message]
2015-05-28 15:15 ` [PATCH v4 3/4] ARM: shmobile: r8a7793: add minimal Gose board " Ulrich Hecht
     [not found]   ` <1432826157-6414-4-git-send-email-ulrich.hecht+renesas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-01  9:39     ` 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=20150602002747.GA4781@verge.net.au \
    --to=horms@verge.net.au \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=ulrich.hecht+renesas@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).