linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support
Date: Fri, 27 May 2016 08:39:38 +0200	[thread overview]
Message-ID: <CAMuHMdVU+FNsQ7uLN82MiGEak5WYqd_ypJ=MLB8U419ZCiG6ow@mail.gmail.com> (raw)
In-Reply-To: <20160527004256.GD14269@verge.net.au>

On Fri, May 27, 2016 at 2:42 AM, Simon Horman <horms@verge.net.au> wrote:
>   Probably there are some central aspects of cpus that are shared
>   between the r8a7795 and r8a7796. And I think that your patch captures
>   that. But I also think that there will be non-shared aspects and
>   perhaps the complexity of splitting the cpus node between per-SoC
>   and common dtsi files isn't worth it.

R8a7795 and r8a7796 have different numbers of CPU cores, and different
maximum frequencies, thus needing different operating-point properties.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2016-05-27  6:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24  1:54 [PATCH v3 0/3] arm64: Add Renesas R8A7796 SoC support Simon Horman
2016-05-24  1:54 ` [PATCH v3 1/3] arm64: dts: r8a7796: " Simon Horman
2016-05-24  5:30   ` Dirk Behme
2016-05-25  0:48     ` Simon Horman
2016-05-25  5:10       ` Dirk Behme
2016-05-25  7:32         ` Dirk Behme
2016-05-26  7:03           ` Geert Uytterhoeven
2016-05-26  7:32             ` Dirk Behme
2016-05-26  8:05               ` Geert Uytterhoeven
2016-05-26  8:11                 ` Dirk Behme
2016-05-26  2:28         ` Simon Horman
2016-05-26  7:14           ` Dirk Behme
2016-05-27  0:42             ` Simon Horman
2016-05-27  6:39               ` Geert Uytterhoeven [this message]
2016-05-27  7:32               ` Dirk Behme
2016-06-29  8:15                 ` Dirk Behme
2016-07-20 23:51                   ` Simon Horman
2016-07-21  5:20                     ` Dirk Behme
2016-07-22  1:47                       ` Simon Horman
2016-05-25  7:38   ` Dirk Behme
2016-05-26  2:31     ` Simon Horman
2016-05-24  1:54 ` [PATCH v3 2/3] arm64: dts: salvator-x: add Salvator-X board on R8A7796 SoC Simon Horman
2016-05-24  1:54 ` [PATCH v3 3/3] arm64: defconfig: enable Renesas " Simon Horman
2016-06-06  1:33 ` [PATCH v3 0/3] arm64: Add Renesas R8A7796 SoC support Simon Horman
2016-06-06  1:52   ` Simon Horman
2016-06-24  3:05     ` Simon Horman

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='CAMuHMdVU+FNsQ7uLN82MiGEak5WYqd_ypJ=MLB8U419ZCiG6ow@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).