linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] ARM: shmobile: sh73a0/kzm9g: Complete multiplatform support
Date: Tue, 13 Jan 2015 10:08:20 +0000	[thread overview]
Message-ID: <CAMuHMdVbuM3oR1KQDzAodp_Y-aWFncPRn48-F9HmrVkGDS36RQ@mail.gmail.com> (raw)
In-Reply-To: <20150113020818.GB21265@verge.net.au>

Hi Simon,

On Tue, Jan 13, 2015 at 3:08 AM, Simon Horman <horms@verge.net.au> wrote:
> On Fri, Jan 09, 2015 at 02:24:26PM +0100, Geert Uytterhoeven wrote:
>>       Hi Simon, Magnus,
>>
>> This patch series completes the migration from kzm9g-reference (legacy
>> DT based) to kzm9g-multiplatform (ARM multiplatform DT based with
>> common clock framework).
>>
>>   - The first two patches fix Ethernet on kzm9g, by adding a Bus State
>>     Controller node, as introduced in "[PATCH v3 0/4] drivers: bus:
>>     Add Simple Power-Managed Bus", and moving the Ethernet node to it,
>>   - The third path enables kzm9g support in shmobile_defconfig,
>>   - The fourth patch removes all kzm9g-reference support, now the
>>     sh73a0 generic multiplatform case has the same feature set
>>     (better, it provides 16 MiB more RAM!).
>>
>> Thanks for applying!
>
> It seems to me that at the first two patches require the patchset
> referenced above in order to work. For that reason I am holding off

Yes it does.

> on applying this series. I am quite happy to negotiate merging
> some or all of this series earlier than later :)

Hence please merge both the dependency and this series.

  1. Both sh73a0/kzm9g-multiplatform and r8a73a4/ape6evm-multiplatform
      depend on "[PATCH v3 0/4] drivers: bus: Add Simple Power-Managed Bus",
  2. DT PM domain for sh73a0 and r8a73a4 depends on
      sh73a0/kzm9g-multiplatform and r8a73a4/ape6evm-multiplatform,
  3. CONFIG_CPU_IDLE=y hangs on sh73a0 without an early timer.
       - On kzm9g-multiplatform this can be fixed by adding an
         arm,cortex-a9-twd-timer node, but that breaks kzm9g-reference as
         the TWD driver requires CCF when instantiated from DT,
       - Fixing this on kzm9g-reference requires setting
         ".init_time = sh73a0_earlytimer_init", and also instantiating the GIC
         from C board code, as the TWD platform device uses an hardcoded
         interrupt number.
         It seems simpler to let kzm9g-reference die, so this problem goes
         away.

Thanks for your consideration!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@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:[~2015-01-13 10:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 13:08 [PATCH 0/4] ARM: shmobile: sh73a0/kzm9g: Introduce multiplatform support Geert Uytterhoeven
2015-01-09 13:08 ` [PATCH 1/4] ARM: shmobile: sh73a0: Introduce generic setup callback Geert Uytterhoeven
2015-01-09 13:08 ` [PATCH 2/4] ARM: shmobile: sh73a0: Add Multiplatform support Geert Uytterhoeven
2015-01-09 13:08 ` [PATCH 3/4] ARM: shmobile: kzm9g dts: Sync with kzm9g-reference dts Geert Uytterhoeven
2015-01-09 13:08 ` [PATCH 4/4] ARM: shmobile: kzm9g: Build DTS for Multiplatform Geert Uytterhoeven
2015-01-09 13:24 ` [PATCH 0/4] ARM: shmobile: sh73a0/kzm9g: Complete multiplatform support Geert Uytterhoeven
2015-01-13  2:08   ` Simon Horman
2015-01-13 10:08     ` Geert Uytterhoeven [this message]
2015-01-14  4:08       ` Simon Horman
2015-01-14 10:03         ` Geert Uytterhoeven
2015-01-14 23:34           ` Simon Horman
2015-01-13  2:08 ` [PATCH 0/4] ARM: shmobile: sh73a0/kzm9g: Introduce " Simon Horman
2015-01-22  2:48   ` Simon Horman
2015-01-22  2:50     ` Simon Horman
2015-01-23  4:22       ` Simon Horman
2015-01-23  9:56         ` 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=CAMuHMdVbuM3oR1KQDzAodp_Y-aWFncPRn48-F9HmrVkGDS36RQ@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).