omap sram, omap4 control module and es2.0 support
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 of 14 patches 0 repliesNew
4 of 14 patches are in this archive. The cover letter announces 14.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/14 | ARM: mmu: Setup MT_MEMORY and MT_MEMORY_NONCACHED L1 entries | +0 | 0 replies | |
| 2/14 | omap: Map only available sram memory | +0 | 6 replies | |
| 2/14 | omap: Map only available sram memory | +0 | 0 replies | |
| 2/14 | omap: Map only available sram memory | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 00/14] omap sram, omap4 control module and es2.0 support
Quoted 20 lines · Shilimkar, Santosh
-----Original Message-----
Quoted 7 lines
From: Paul Walmsley [mailto:paul at pwsan.com]
Sent: Friday, September 17, 2010 11:21 PM
To: Shilimkar, Santosh
Cc: linux-omap at vger.kernel.org; linux-arm-kernel at lists.infradead.org
Subject: Re: [PATCH 00/14] omap sram, omap4 control module and es2.0 supportQuoted 9 lines
Hello Santosh
Quoted 2 lines · Santosh Shilimkar
This is consolidated patch series targetted for 2.6.37 merge window. All of these patches have been already posted/reviewed on the list.
Patch 6 is missing, could you please look into why?
Mostly because of size of the patch, You can pick this from the below git link
Quoted 6 lines
Quoted 4 lines
Also, please split all of the SCM changes out into a separate series/branch since they will be going in through my tree. Am reviewing those now.
Ok done. I have split the series and kept scm changes on 'omap4_scm_2.6.37' head and rest on 'omap_for_2.6.37'
Santosh, the "Setup MT_MEMORY and MT_MEMORY_NONCACHED L1 entries" should get tested in the arm tree to avoid nasty surprises. Please do the following split:
1. A series for Russell to pull
ARM: mmu: Setup MT_MEMORY and MT_MEMORY_NONCACHED L1 entries
omap: Map only available sram memory
davinci: map sram using MT_MEMORY_NONCACHED instead of MT_DEVICE
You can add my Acked-by: Tony Lindgren <[email protected]> to the "Map only available sram memory" patch.
2. A series for me to pull
omap4: sram: Fix start address
omap4: Update id.c and cpu.h for es2.0
omap4: l2x0: Fix init parameter for es2.0
omap4: Panda: Add DEBUG_LL support
omap4: Fix bootup crash observed with higher CPU clocks
3. A series for Paul to pull (already in omap4_scm_2.6.37)
omap4: control: Add ctrl_pad_base to omap_globals
omap4: control: Add accessor api's for pad control module
omap4: control: Add the register definition headers
omap4: control: Fix the control module register accesses
Please base them either on v2.6.35 or v2.6.36-rc5.
Regards,
Tony