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] ARM: OMAP5: hwmod, prm/cm data files and updates for 3.10
Date: Wed, 3 Apr 2013 09:22:13 +0530	[thread overview]
Message-ID: <515BA76D.3000302@ti.com> (raw)
In-Reply-To: <20130401170539.GK10155@atomide.com>

Paul,

On Monday 01 April 2013 10:35 PM, Tony Lindgren wrote:
> * Santosh Shilimkar <santosh.shilimkar@ti.com> [130320 01:43]:
>> Tony,
>>
>> Here is the pull request for OMAP5 data file patches which are on list from
>> last merge window. As aligned on list, I have dropped clock data from the
>> series. That means for the boot, one clock data patch needs to be applied.
>> It is available on my git tree in 'out_of_tree/omap5_clk_data' branch.
>>
>> As discussed already on list, you will notice hwmod data loc has come down
>> from ~6000 lines to ~2000 lines becasue of removal of iospace, irq, dma data
>> as well as unused hwmods. Few hwmods for which dt conversion is pending are
>> not added as well but those would add max ~400 loc in future.
>>
>> The following changes since commit a937536b868b8369b98967929045f1df54234323:
>>
>>   Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
>>
>> are available in the git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux.git for_3.10/omap5_data_files
>>
>> for you to fetch changes up to 8a6a32e589a1a2a5a3fb8ebe8fc7426997bc6d89:
>>
>>   ARM: OMAP5: Enable build and frameowrk initialisations (2013-03-19 14:09:11 +0530)
> 
> Paul, do you have any comments on these?
> 
Ping.

> This branch should be queued separately because of the amount of
> LOC it adds. But as you may have other PRCM related patches then it's
> probably best that you queue it.
> 
Just to be clear, these are all data files patches which are auto-generated.

Thes patchset has already missed last couple of merge windows and its the
biggest bottleneck in getting OMAP5 booting from mainline. So I request
you to please have a look it quickly so that Tony can line that up for
3.10.

Thanks for help in advance !!

Regards,
Santosh

  reply	other threads:[~2013-04-03  3:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20  8:40 [GIT PULL] ARM: OMAP5: hwmod, prm/cm data files and updates for 3.10 Santosh Shilimkar
2013-04-01 17:05 ` Tony Lindgren
2013-04-03  3:52   ` Santosh Shilimkar [this message]
2013-04-03 19:42     ` Paul Walmsley
2013-04-04 11:12       ` Santosh Shilimkar
2013-04-04 16:52         ` Tony Lindgren
2013-04-04 16:57           ` Santosh Shilimkar
2013-04-05 16:50             ` Santosh Shilimkar
2013-04-05 17:10               ` Tony Lindgren
2013-04-09 18:03                 ` Hiremath, Vaibhav
2013-04-10 11:15               ` Hiremath, Vaibhav
2013-04-10 11:32                 ` Santosh Shilimkar
2013-04-15  5:06                   ` Hiremath, Vaibhav
2013-04-15  6:20                     ` Santosh Shilimkar
2013-04-18  4:49                       ` Hiremath, Vaibhav
2013-04-10 11:23               ` Hiremath, Vaibhav
2013-05-17  8:00               ` Santosh Shilimkar
2013-05-17 17:22                 ` Tony Lindgren
2013-05-29 16:41                   ` Santosh Shilimkar
2013-04-05 12:42         ` Tero Kristo
2013-04-03 20:09 ` Paul Walmsley
2013-04-04 10:34   ` Santosh Shilimkar

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=515BA76D.3000302@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).