<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/include/linux/mmc/sh_mmcif.h, branch linux-3.2.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.2.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.2.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2011-10-26T20:32:09Z</updated>
<entry>
<title>mmc: sh_mmcif: simplify platform data</title>
<updated>2011-10-26T20:32:09Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2011-08-30T16:26:39Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=714c4a6e3a0f730834ec8a8bc83b2a6da33f54dc'/>
<id>urn:sha1:714c4a6e3a0f730834ec8a8bc83b2a6da33f54dc</id>
<content type='text'>
Provide platforms with a simplified way to specify MMCIF DMA slave IDs in
a way, similar to SDHI and other sh_dma clients.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: Standardize header file inclusion checks.</title>
<updated>2011-07-20T21:20:48Z</updated>
<author>
<name>Robert P. J. Day</name>
<email>rpjday@crashcourse.ca</email>
</author>
<published>2011-05-27T20:04:03Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=100e918610b7487fa18db97b3879cd8d1fdd5974'/>
<id>urn:sha1:100e918610b7487fa18db97b3879cd8d1fdd5974</id>
<content type='text'>
Standardize the checks for multiple MMC header file inclusion,
including adding comments to terminating #endif's, and fixing
one incorrect comment.

Signed-off-by: Robert P. J. Day &lt;rpjday@crashcourse.ca&gt;
Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;
</content>
</entry>
<entry>
<title>mmc: Add MMC_PROGRESS_*</title>
<updated>2011-03-24T16:24:57Z</updated>
<author>
<name>Simon Horman</name>
<email>horms@verge.net.au</email>
</author>
<published>2011-03-24T07:04:38Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=9d9659b6c0ebf7dde65ebada4c67980818245913'/>
<id>urn:sha1:9d9659b6c0ebf7dde65ebada4c67980818245913</id>
<content type='text'>
This is my second attempt to make this enum generally available.
The first attempt added MMCIF_PROGRESS_* to include/linux/mmc/sh_mmcif.h.
However this is not sufficiently generic as the enum will be
used by SDHI boot code.

Signed-off-by: Simon Horman &lt;horms@verge.net.au&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>mmc: sh_mmcif: Convert to __raw_xxx() I/O accessors.</title>
<updated>2011-01-14T06:57:47Z</updated>
<author>
<name>Paul Mundt</name>
<email>lethal@linux-sh.org</email>
</author>
<published>2011-01-14T06:57:47Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=bba958783b1b4cb0a9420f4e11082467132a334c'/>
<id>urn:sha1:bba958783b1b4cb0a9420f4e11082467132a334c</id>
<content type='text'>
When using the I/O accessors in raw mode from the boot stubs we don't
want to bother with any of the complexity associated with readl/writel
and friends. Furthermore, utilization within the context of the host
driver itself is all performed on an ioremapped window, so using the
__raw variants there doesn't pose any problem either.

If and when barriers need to be added in the future, these will need to
be explicitly written out, but this is so far not a concern for any of
the affected CPUs in question.

This fixes up the link error introduced by the ARM tree via its barrier
refactoring:

	arch/arm/boot/compressed/mmcif-sh7372.o: In function `mmcif_loader':
	mmcif-sh7372.c:(.text+0x9e8): undefined reference to `outer_cache

Following the change in:

	http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6275/1

Reported-by: Simon Horman &lt;horms@verge.net.au&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>Merge branches 'sh/memchunk' and 'common/mmcif' into sh-latest</title>
<updated>2011-01-11T04:05:15Z</updated>
<author>
<name>Paul Mundt</name>
<email>lethal@linux-sh.org</email>
</author>
<published>2011-01-11T04:05:15Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=89e9fd32c6f4ed58cd6f6e3c3cf5b536a3f36100'/>
<id>urn:sha1:89e9fd32c6f4ed58cd6f6e3c3cf5b536a3f36100</id>
<content type='text'>
</content>
</entry>
<entry>
<title>mmc, sh: Remove sh_mmcif_boot_slurp()</title>
<updated>2010-12-08T07:24:28Z</updated>
<author>
<name>Simon Horman</name>
<email>horms@verge.net.au</email>
</author>
<published>2010-12-06T00:12:45Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=54b384634f7083bcacf9a9ed2e6f4c3d0a246e49'/>
<id>urn:sha1:54b384634f7083bcacf9a9ed2e6f4c3d0a246e49</id>
<content type='text'>
As the only caller of sh_mmcif_boot_do_read() is
sh_mmcif_boot_slurp() the configuration portion of
sh_mmcif_boot_slurp() can be merged into sh_mmcif_boot_do_read().

Once this is done sh_mmcif_boot_slurp() is only a call
to sh_mmcif_boot_do_read() with platform specific information -
the offset that images are stored on MMC. So make the
sh_mmcif_boot_do_read() call directly from platform code
and remove sh_mmcif_boot_slurp() altogether.

Cc: Magnus Damm &lt;magnus.damm@gmail.com&gt;
Signed-off-by: Simon Horman &lt;horms@verge.net.au&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>mmc, sh: Move MMCIF_PROGRESS_* into sh_mmcif.h</title>
<updated>2010-12-08T07:24:21Z</updated>
<author>
<name>Simon Horman</name>
<email>horms@verge.net.au</email>
</author>
<published>2010-12-06T00:12:44Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=9f843706bb87837b823228467f4f83973fd110e9'/>
<id>urn:sha1:9f843706bb87837b823228467f4f83973fd110e9</id>
<content type='text'>
Allow MMCIF_PROGRESS_* to be shared.

Cc: Magnus Damm &lt;magnus.damm@gmail.com&gt;
Signed-off-by: Simon Horman &lt;horms@verge.net.au&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'common/mmcif' into rmobile/mmcif</title>
<updated>2010-11-30T05:42:55Z</updated>
<author>
<name>Paul Mundt</name>
<email>lethal@linux-sh.org</email>
</author>
<published>2010-11-30T05:42:55Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d8e7943d821d8ee7f48ff38f6f7c509297c88402'/>
<id>urn:sha1:d8e7943d821d8ee7f48ff38f6f7c509297c88402</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sh, mmc: Use defines when setting CE_CLK_CTRL</title>
<updated>2010-11-29T03:54:55Z</updated>
<author>
<name>Simon Horman</name>
<email>horms@verge.net.au</email>
</author>
<published>2010-11-27T00:11:55Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=22efa0fee32d9e7f6f6fbc396a872b5708d86048'/>
<id>urn:sha1:22efa0fee32d9e7f6f6fbc396a872b5708d86048</id>
<content type='text'>
The 16-19th bits of CE_CLK_CTRL set the
MMC clock frequency.

Cc: Yusuke Goda &lt;yusuke.goda.sx@renesas.com&gt;
Cc: Magnus Damm &lt;magnus.damm@gmail.com&gt;
Signed-off-by: Simon Horman &lt;horms@verge.net.au&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>mmc, sh: Correct value for reset</title>
<updated>2010-11-29T03:54:50Z</updated>
<author>
<name>Simon Horman</name>
<email>horms@verge.net.au</email>
</author>
<published>2010-11-26T23:02:58Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=1ae0affedce1d3e401991fbe7f2674753f0a7641'/>
<id>urn:sha1:1ae0affedce1d3e401991fbe7f2674753f0a7641</id>
<content type='text'>
This resolves a regression that I introduced in
"mmc, sh: Move constants to sh_mmcif.h". Having
examined the manual and tested the code on an AP4EVB board
it seems that the correct sequence is.

1) Write 1 to bit 31 and zeros to all other bits
2) Write zero to all bits

Cc: Yusuke Goda &lt;yusuke.goda.sx@renesas.com&gt;
Cc: Magnus Damm &lt;magnus.damm@gmail.com&gt;
Signed-off-by: Simon Horman &lt;horms@verge.net.au&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
</feed>
