<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/arm/include/asm/mach, branch linux-2.6.30.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.30.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.30.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2009-03-12T19:25:02Z</updated>
<entry>
<title>[ARM] 5422/1: ARM: MMU: add a Non-cacheable Normal executable memory type</title>
<updated>2009-03-12T19:25:02Z</updated>
<author>
<name>Paul Walmsley</name>
</author>
<published>2009-03-12T19:11:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e4707dd3e9d0cb57597b6568a5e51fea5d6fca41'/>
<id>urn:sha1:e4707dd3e9d0cb57597b6568a5e51fea5d6fca41</id>
<content type='text'>
This patch adds a Non-cacheable Normal ARM executable memory type,
MT_MEMORY_NONCACHED.

On OMAP3, this is used for rapid dynamic voltage/frequency scaling in
the VDD2 voltage domain. OMAP3's SDRAM controller (SDRC) is in the
VDD2 voltage domain, and its clock frequency must change along with
voltage. The SDRC clock change code cannot run from SDRAM itself,
since SDRAM accesses are paused during the clock change. So the
current implementation of the DVFS code executes from OMAP on-chip
SRAM, aka "OCM RAM."

If the OCM RAM pages are marked as Cacheable, the ARM cache controller
will attempt to flush dirty cache lines to the SDRC, so it can fill
those lines with OCM RAM instruction code. The problem is that the
SDRC is paused during DVFS, and so any SDRAM access causes the ARM MPU
subsystem to hang.

TI's original solution to this problem was to mark the OCM RAM
sections as Strongly Ordered memory, thus preventing caching. This is
overkill: since the memory is marked as non-bufferable, OCM RAM writes
become needlessly slow. The idea of "Strongly Ordered SRAM" is also
conceptually disturbing. Previous LAKML list discussion is here:

http://www.spinics.net/lists/arm-kernel/msg54312.html

This memory type MT_MEMORY_NONCACHED is used for OCM RAM by a future
patch.

Cc: Richard Woodruff &lt;r-woodruff2@ti.com&gt;
Signed-off-by: Paul Walmsley &lt;paul@pwsan.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>Merge branch 'dma' into devel</title>
<updated>2009-02-21T21:42:50Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2009-02-21T21:42:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=22b61a11fd4e6d7a48d694ce350331bebc0394ed'/>
<id>urn:sha1:22b61a11fd4e6d7a48d694ce350331bebc0394ed</id>
<content type='text'>
Conflicts:

	arch/arm/plat-mxc/dma-mx1-mx2.c
</content>
</entry>
<entry>
<title>[ARM] dma: move IOMD and floppy DMA structures to RiscPC DMA code</title>
<updated>2009-02-21T21:36:22Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2009-02-21T21:36:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=308d333ad6cc12e39adaed22dc10bac48e17742a'/>
<id>urn:sha1:308d333ad6cc12e39adaed22dc10bac48e17742a</id>
<content type='text'>
There's no point these being in a generic include file when they're
only used in arch/arm/mach-rpc/dma.c.

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>PCI: arm: use generic INTx swizzle from PCI core</title>
<updated>2009-01-07T19:13:13Z</updated>
<author>
<name>Bjorn Helgaas</name>
</author>
<published>2008-12-17T04:37:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=06df69932add8108f599ef26fcdf36c4f8125e50'/>
<id>urn:sha1:06df69932add8108f599ef26fcdf36c4f8125e50</id>
<content type='text'>
Use the generic pci_common_swizzle() instead of arch-specific code.

Signed-off-by: Bjorn Helgaas &lt;bjorn.helgaas@hp.com&gt;
Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
</content>
</entry>
<entry>
<title>[ARM] dma: remove dmamode_t typedef</title>
<updated>2009-01-02T12:34:55Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2009-01-02T12:34:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f0ffc816250a8cc28e6824326e2d58333e058eca'/>
<id>urn:sha1:f0ffc816250a8cc28e6824326e2d58333e058eca</id>
<content type='text'>
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] dma: constify dma controller name and dma ops</title>
<updated>2008-12-11T14:52:42Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2008-12-11T14:50:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8c56afcbea22e472d3bfa8ddf06f23cd6bc56826'/>
<id>urn:sha1:8c56afcbea22e472d3bfa8ddf06f23cd6bc56826</id>
<content type='text'>
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] dma: move RiscPC specific DMA data out of dma_struct</title>
<updated>2008-12-11T14:35:57Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2008-12-08T17:35:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ad9dd94c384f7ee37b798a9349b8c42da8fa99ab'/>
<id>urn:sha1:ad9dd94c384f7ee37b798a9349b8c42da8fa99ab</id>
<content type='text'>
Separate the RiscPC specific (IOMD and floppy FIQ) data out of the core
DMA structure by making the IOMD and floppy DMA supersets.

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] dma: rejig DMA initialization</title>
<updated>2008-12-11T14:32:43Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2008-12-08T16:33:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2f757f2ab7411cf0e2779012d8cda0cbf2f80d26'/>
<id>urn:sha1:2f757f2ab7411cf0e2779012d8cda0cbf2f80d26</id>
<content type='text'>
Rather than having the central DMA multiplexer call the architecture
specific DMA initialization function, have each architecture DMA
initialization function use core_initcall(), and register each DMA
channel separately with the multiplexer.

This removes the array of dma structures in the central multiplexer,
replacing it with an array of pointers instead; this is more flexible
since it allows the drivers to wrap the DMA structure (eventually
allowing us to transition non-ISA DMA drivers away.)

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] dma: remove dmach_t typedef</title>
<updated>2008-12-08T15:58:50Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2008-12-08T15:58:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1df8130278c4543555fea697e5714fbac300b899'/>
<id>urn:sha1:1df8130278c4543555fea697e5714fbac300b899</id>
<content type='text'>
Remove a pointless integer typedef.

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] iop: iop3xx needs registers mapped uncached+unbuffered</title>
<updated>2008-11-09T11:18:36Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2008-11-09T11:18:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ebb4c65869db7213280ad9c510637683939b5ff8'/>
<id>urn:sha1:ebb4c65869db7213280ad9c510637683939b5ff8</id>
<content type='text'>
Mikael Pettersson reported:

   The 2.6.28-rc kernels fail to detect PCI device 0000:00:01.0
   (the first ethernet port) on my Thecus n2100 XScale box.

   There is however still a strange "ghost" device that gets partially
   detected in 2.6.28-rc2 vanilla.

The IOP321 manual says:

  The user designates the memory region containing the OCCDR as
  non-cacheable and non-bufferable from the IntelR XScaleTM core.
  This guarantees that all load/stores to the OCCDR are only of
  DWORD quantities.

Ensure that the OCCDR is so mapped.

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
</feed>
