<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/staging/android/Kconfig, branch v3.4.30</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/staging/android/Kconfig?h=v3.4.30</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/staging/android/Kconfig?h=v3.4.30'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-04-10T16:48:29Z</updated>
<entry>
<title>android: make persistent_ram based drivers depend on HAVE_MEMBLOCK</title>
<updated>2012-04-10T16:48:29Z</updated>
<author>
<name>Colin Cross</name>
<email>ccross@android.com</email>
</author>
<published>2012-03-21T17:18:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=099f5d01a6f73712e17552679aa724e021809a6e'/>
<id>urn:sha1:099f5d01a6f73712e17552679aa724e021809a6e</id>
<content type='text'>
m68k doesn't have memblock_reserve, which causes a build failure
with allmodconfig.  Make PERSISTENT_RAM and RAM_CONSOLE depend on
HAVE_MEMBLOCK.

Reported-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Reported-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Signed-off-by: Colin Cross &lt;ccross@android.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: android: persistent_ram: refactor ecc support</title>
<updated>2012-03-08T17:36:08Z</updated>
<author>
<name>Colin Cross</name>
<email>ccross@android.com</email>
</author>
<published>2012-03-08T01:34:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9cc05ad97c5728aaf4db94490daf41f8958b5aee'/>
<id>urn:sha1:9cc05ad97c5728aaf4db94490daf41f8958b5aee</id>
<content type='text'>
Remove CONFIG_ANDROID_RAM_CONSOLE_ERROR_CORRECTION and related
 #ifdefs.  Also allow persistent ram zones without ecc enabled.
For some use cases, like the data portion of the upcoming
persistent_vars patches, or a persistent ftrace ringbuffer,
ecc on every update is too expensive.

CC: Greg KH &lt;gregkh@linuxfoundation.org&gt;
CC: Android Kernel Team &lt;kernel-team@android.com&gt;
Signed-off-by: Colin Cross &lt;ccross@android.com&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: android: ram_console: split out persistent ram</title>
<updated>2012-03-08T17:36:08Z</updated>
<author>
<name>Colin Cross</name>
<email>ccross@android.com</email>
</author>
<published>2012-03-08T01:34:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c672528aec4a1cf6f3df7a6022e6823a20b20f8e'/>
<id>urn:sha1:c672528aec4a1cf6f3df7a6022e6823a20b20f8e</id>
<content type='text'>
Split ram_console into two halves.

persistent_ram is a set of apis that handle a block of memory
that does not get erased across a reboot.  It provides functions
to fill it as a single buffer or a ring buffer, and to extract
the old data after a reboot.  It handles ecc on the data to
correct bit errors introduced during reboot.

ram_console is now a small wrapper around persistent_ram that
feeds console data into the ringbuffer, and exports the old
data to /proc/last_kmsg after a reboot.

[jstultz: Moved persistent_ram.h to staging dir]
CC: Greg KH &lt;gregkh@linuxfoundation.org&gt;
CC: Android Kernel Team &lt;kernel-team@android.com&gt;
Signed-off-by: Colin Cross &lt;ccross@android.com&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: android: ram_console: drop verbose ram_console support</title>
<updated>2012-03-08T02:32:40Z</updated>
<author>
<name>Colin Cross</name>
<email>ccross@android.com</email>
</author>
<published>2012-03-08T01:34:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c5ee1211f249b0897f715aba4647c1f494509cab'/>
<id>urn:sha1:c5ee1211f249b0897f715aba4647c1f494509cab</id>
<content type='text'>
Equivalent functionality can be obtained with loglevel=15

CC: Android Kernel Team &lt;kernel-team@android.com&gt;
Signed-off-by: Colin Cross &lt;ccross@android.com&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: android: ram_console: drop early buffer support</title>
<updated>2012-03-08T02:32:40Z</updated>
<author>
<name>Colin Cross</name>
<email>ccross@android.com</email>
</author>
<published>2012-03-08T01:34:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8294e2362fa1ce8a172a32ae8607d35563e8b043'/>
<id>urn:sha1:8294e2362fa1ce8a172a32ae8607d35563e8b043</id>
<content type='text'>
Early ramconsole is not very useful, an early crash will prevent
getting the logged data out on the next boot, and CONFIG_DEBUG_LL=y
will get the same information.  Drop it to simplify a future
refactoring.

CC: Android Kernel Team &lt;kernel-team@android.com&gt;
Signed-off-by: Colin Cross &lt;ccross@android.com&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'staging-3.3-rc3' into staging-next</title>
<updated>2012-02-10T18:58:25Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2012-02-10T18:58:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b91867f2ee5c84b550f95ce54c91b180f70f48cb'/>
<id>urn:sha1:b91867f2ee5c84b550f95ce54c91b180f70f48cb</id>
<content type='text'>
This was done to resolve some merge issues with the following files that
had changed in both branches:
	drivers/staging/rtl8712/rtl871x_sta_mgt.c
	drivers/staging/tidspbridge/rmgr/drv_interface.c
	drivers/staging/zcache/zcache-main.c

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: android-alarm: Support old drivers via preprocessor aliasing</title>
<updated>2012-02-10T18:08:01Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2012-02-09T22:24:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2157f896774ace6e98c851878f8089fb861502e2'/>
<id>urn:sha1:2157f896774ace6e98c851878f8089fb861502e2</id>
<content type='text'>
Older out of tree drivers that were desgined to the Android Alarm
in-kernel API may not build due to the namespace collision fixed in
an earlier patch. Per Arve's suggestion, this patch provides
preprocessor macros that allow older drivers to build.

CC: Arve Hjønnevåg &lt;arve@android.com&gt;
CC: Android Kernel Team &lt;kernel-team@android.com&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: android-alarm: Disable Android alarm driver by default</title>
<updated>2012-02-10T18:08:00Z</updated>
<author>
<name>Praneeth Kumar Bajjuri</name>
<email>a0132704@ti.com</email>
</author>
<published>2012-02-09T22:24:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=58a38ff3b12ebd103e3ca2c5dea3292ffbfd0f02'/>
<id>urn:sha1:58a38ff3b12ebd103e3ca2c5dea3292ffbfd0f02</id>
<content type='text'>
Do not enable Android alarm driver by default

CC: Arve Hjønnevåg &lt;arve@android.com&gt;
CC: Android Kernel Team &lt;kernel-team@android.com&gt;
CC: Praneeth Bajjuri &lt;praneeth@ti.com&gt;
Change-Id: Iff8f7a65c4eceecfd084074937c72824697b5e7f
Signed-off-by: Praneeth Bajjuri &lt;praneeth@ti.com&gt;
[jstultz: tweaked commit subject &amp; msg]
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: android-alarm: Reenable android alarm driver</title>
<updated>2012-02-10T18:06:43Z</updated>
<author>
<name>John Stultz</name>
<email>john.stultz@linaro.org</email>
</author>
<published>2012-02-09T22:24:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fe8d2727ffa65bcb516b4947bec1c546841e7d25'/>
<id>urn:sha1:fe8d2727ffa65bcb516b4947bec1c546841e7d25</id>
<content type='text'>
Now that it builds, re-enable android alarm driver in
the makefile and kconfig

CC: Arve Hjønnevåg &lt;arve@android.com&gt;
CC: Android Kernel Team &lt;kernel-team@android.com&gt;
Signed-off-by: John Stultz &lt;john.stultz@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: android/ram_console: Don't build on arches w/o ioremap</title>
<updated>2012-02-08T22:14:15Z</updated>
<author>
<name>Anton Vorontsov</name>
<email>anton.vorontsov@linaro.org</email>
</author>
<published>2012-02-07T05:13:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=203209ef77e4d5f0ee729557b09770bce0c2d251'/>
<id>urn:sha1:203209ef77e4d5f0ee729557b09770bce0c2d251</id>
<content type='text'>
This patch fixes UML build:

    CC      drivers/staging/android/ram_console.o
  drivers/staging/android/ram_console.c: In function
  'ram_console_driver_probe':
  drivers/staging/android/ram_console.c:358:2: error: implicit declaration
  of function 'ioremap' [-Werror=implicit-function-declaration]
  cc1: some warnings being treated as errors
  make[3]: *** [drivers/staging/android/ram_console.o] Error 1

Signed-off-by: Anton Vorontsov &lt;anton.vorontsov@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
