From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] ARM: keystone: add PM bus support for clock management
Date: Fri, 30 Aug 2013 12:25:36 -0400 [thread overview]
Message-ID: <5220C780.2060301@ti.com> (raw)
In-Reply-To: <87k3j3p2xx.fsf@linaro.org>
On Friday 30 August 2013 12:18 PM, Kevin Hilman wrote:
> Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
>
>> Add runtime PM core support to Keystone SOCs by using the pm_clk
>> infrastructure of the PM core. Patch is based on Kevin's pm_domain
>> work on DaVinci SOCs.
>>
>> Keystone SOC doesn't have depedency to enable clocks in early
>> in the boot and hence the clock and PM bus initialisation is done
>> at subsys_init() level.
>>
>> Cc: Kevin Hilman <khilman@linaro.org>
>>
>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> ---
>> drivers/bus/Makefile | 2 ++
>> drivers/bus/keystone_pm_bus.c | 70 +++++++++++++++++++++++++++++++++++++++++
>
> Maybe I missed some earlier discussion on this, but why drivers/bus?
>
> I called the davinci stuff 'bus' initially because it piggy-backed the
> platform_bus, but now that we have pm_domains, it's using that, and is
> unrelated the bus.
>
> Therefore, as with davinci, I suspect this belongs in mach-keystone.
>
There is not much keystone specific code and hence thought it doesn't
have to be part of mach-keystone/*. drivers/bus/* I picked out of hat ;-)
thinking it is much of PM bus code. I couldn't find a better place than
that. Any other better place you can suggest ??
> [...]
>
>> diff --git a/drivers/bus/keystone_pm_bus.c b/drivers/bus/keystone_pm_bus.c
>> new file mode 100644
>> index 0000000..6cc56f1
>> --- /dev/null
>> +++ b/drivers/bus/keystone_pm_bus.c
>> @@ -0,0 +1,70 @@
>> +/*
>> + * PM Bus driver for Keystone2 devices
>> + *
>> + * Copyright 2013 Texas Instruments, Inc.
>> + * Santosh Shilimkar <santosh.shillimkar@ti.com>
>> + *
>> + * Based on Kevins work on DAVINCI SOCs
>> + * Kevin Hilman <khilman@ti.com>
>
> Dead email address (as you know) ;) You can just leave off the email,
> or use khilman at kernel.org as one that shouldn't change.
>
Sorry I will fix that. Will use "khilman at kernel.org".
Regards,
Santosh
next prev parent reply other threads:[~2013-08-30 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 23:36 [PATCH v2 0/4] ARM: keystone: clock tree and PM bus support Santosh Shilimkar
2013-08-29 23:36 ` [PATCH v2 1/4] ARM: dts: keystone: Add clock tree data to devicetree Santosh Shilimkar
2013-08-29 23:36 ` [PATCH v2 2/4] ARM: dts: keystone: Add clock phandle to UART nodes Santosh Shilimkar
2013-08-29 23:36 ` [PATCH v2 3/4] ARM: keystone: Enable clock drivers Santosh Shilimkar
2013-08-29 23:36 ` [PATCH v2 4/4] ARM: keystone: add PM bus support for clock management Santosh Shilimkar
2013-08-30 16:18 ` Kevin Hilman
2013-08-30 16:25 ` Santosh Shilimkar [this message]
2013-10-11 0:15 ` Santosh Shilimkar
2013-10-14 17:32 ` Kevin Hilman
2013-10-14 18:00 ` Santosh Shilimkar
2013-10-14 18:18 ` Kevin Hilman
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=5220C780.2060301@ti.com \
--to=santosh.shilimkar@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.