linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Keystone SOC updates for v3.13
Date: Thu, 10 Oct 2013 19:30:13 -0400	[thread overview]
Message-ID: <52573885.9010007@ti.com> (raw)
In-Reply-To: <87wqlkn4kn.fsf@linaro.org>

On Thursday 10 October 2013 06:28 PM, Kevin Hilman wrote:
> Hi Santosh,
> 
> Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
> 
>> Olof,
>>
>> Please pull below Keystone SOC updates for v3.13. As discussed on irc, the
>> pull request is build on top of v3.13-rc4 because of dependent commit
>> c2b9e974{dma/Kconfig: Make TI_EDMA select TI_PRIV_EDMA}. The pull request
>> carries Kconfig update patch {dma: Allow TI_EDMA selectable for ARCH_KEYSTONE}
>> with Vinod Koul's ack as per alignment on the mailing list[1]. The clock
>> driver support is already applied by Mike to his 3.13 clk-next [2]
>>
>> The following changes since commit ef887009524c3631d804a2587ec204c4ff61a5b8:
>>
>>   ARM: keystone: Enable I2C and SPI bus support (2013-10-08 15:37:41 -0400)
>>
>> are available in the git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/keystone-soc-for-arm-soc
>>
>> for you to fetch changes up to ef887009524c3631d804a2587ec204c4ff61a5b8:
>>
>>   ARM: keystone: Enable I2C and SPI bus support (2013-10-08 15:37:41 -0400)
>>
>> ----------------------------------------------------------------
>> SOC updates for Keystone II devices:
>>
>> - Clock tree support
>> - Clock management support using PM core
>> - Keystone config update for EMDA with ack from Vinod
>> - Enable SPI and I2C drivers
>>
>> ----------------------------------------------------------------
>>
>> Santosh Shilimkar (9):
>>   ARM: dts: keystone: Add clock tree data to devicetree
>>   ARM: dts: keystone: Add clock phandle to UART nodes
>>   ARM: keystone: Enable clock drivers
>>   ARM: keystone: add PM bus support for clock management
> 
> I still don't like this one.  Like I pointed out earlier[1], this
> doesn't really have anything to do with a bus, so it doesn't belong in
> drivers/bus (and the 'bus' naming throughout isn't right.)  IMO, it
> belongs in mach-keystone as the platform glue telling how the PM domains
> are hooked up on keystone.
> 
I did ask follow up question[2] back since I thought there is nothing
machine specific code in that. Thought you agreed to my argument.

> Please move it to mach-keystone, and s/pm_bus/pm_domain/ throughout
> since it has nothing to do with bus.  The 'bus' naming in davinci is
> leftover from the pre-pm_domain days when we were overriding functions
> of the platform_bus.
> 
But I respect your view and hence will send and updated pull request
with the above rename.

Regards,
Santosh

> 
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-August/196026.html
> 
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-August/196027.html

  reply	other threads:[~2013-10-10 23:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 21:29 [GIT PULL] Keystone SOC updates for v3.13 Santosh Shilimkar
2013-10-10 22:28 ` Kevin Hilman
2013-10-10 23:30   ` Santosh Shilimkar [this message]
2013-10-11 19:51     ` 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=52573885.9010007@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 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).