From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/5] ARM: shmobile: Enable drivers/sh/pm_runtime.c on multi-platform
Date: Thu, 20 Mar 2014 12:24:23 +0000 [thread overview]
Message-ID: <532ADDF7.70601@codethink.co.uk> (raw)
In-Reply-To: <1395256010-12222-1-git-send-email-geert@linux-m68k.org>
On 20/03/14 13:19, Laurent Pinchart wrote:
> Hi Geert,
>
> On Thursday 20 March 2014 13:13:28 Geert Uytterhoeven wrote:
>> On Thu, Mar 20, 2014 at 1:01 PM, Laurent Pinchart wrote:
>>> On Thursday 20 March 2014 09:56:17 Ben Dooks wrote:
>>>> On 19/03/14 20:06, Geert Uytterhoeven wrote:
>>>>> This patchset enables the PM runtime code in drivers/sh/pm_runtime.c
>>>>> when running a multi-platform ARM kernel including support for
>>>>> shmobile. Before this code was only enabled for legacy shmobile
>>>>> kernels, leading to disabled clocks in multiplatform kernels, depending
>>>>> on implicit reset state or on the bootloader.
>>>>>
>>>>> [1/5] drivers: sh: pm_runtime does not need idle callback
>>>>> [2/5] sh: intc: Restrict INTC_USERIMASK to SH4A
>>>>
>>>> I thought there was already a of capable intc driver in the
>>>> irq drivers directory?
>>>
>>> I think Ben's point is that drivers/sh/intc might be completely unneeded
>>> for ARM.
>>
>> http://www.spinics.net/lists/linux-sh/msg30067.html
>>
>> "Furthermore, the core intc parts are used by sh7372/mackerel and
>> sh73a0/kzm9g (and arch/sh) only, so I'm gonna restrict it to
>> ARCH_SHMOBILE_LEGACY and SUPERH only."
>
> My bad, sorry. If it wasn't for sh7372 and sh73a0 being old SoCs that's
> probably something we should fix by moving the code to drivers/irqchip.
Something to look at later?
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-03-20 12:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 19:06 [PATCH 0/5] ARM: shmobile: Enable drivers/sh/pm_runtime.c on multi-platform Geert Uytterhoeven
2014-03-20 1:48 ` Laurent Pinchart
2014-03-20 8:56 ` Ben Dooks
2014-03-20 9:14 ` Geert Uytterhoeven
2014-03-20 9:35 ` Ben Dooks
2014-03-20 11:59 ` Laurent Pinchart
2014-03-20 12:13 ` Geert Uytterhoeven
2014-03-20 12:18 ` Geert Uytterhoeven
2014-03-20 12:19 ` Laurent Pinchart
2014-03-20 12:24 ` Ben Dooks [this message]
2014-04-14 5:10 ` Kuninori Morimoto
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=532ADDF7.70601@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-sh@vger.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;
as well as URLs for NNTP newsgroup(s).