[meego-commits] 6097: Changes to Trunk:Testing/kernel
Arjan van de Ven
arjan at linux.intel.com
Fri Jul 30 00:02:31 UTC 2010
Hi,
I have made the following changes to kernel in project Trunk:Testing. Please review and accept ASAP.
Thank You,
Arjan van de Ven
[This message was auto-generated]
---
Request #6097:
submit: devel:kernel/kernel(r104) -> Trunk:Testing/kernel
Message:
adding mrst sound driver, and likely fixing the aava touch screen
State: new 2010-07-29T11:55:28 arjan
Comment: None
changes files:
--------------
--- kernel.changes
+++ kernel.changes
@@ -0,0 +1,6 @@
+* Thu Jul 29 2010 Arjan van de Ven <arjan at linux.intel.com> - 2.6.35-rc6
+- update -ac patch
+ - audio drivers added
+ - various Medfield sensors added
+ - starting the lobotomy of abstraction layers that abstract abstraction layers
+
new:
----
linux-2.6.35-aava-firmware-workaround.patch
linux-2.6.35-rc6-ac-20100729.patch
spec files:
-----------
--- kernel-ivi.spec
+++ kernel-ivi.spec
@@ -206,9 +206,10 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-Patch200: linux-2.6.35-rc6-ac-20100727.patch
+Patch200: linux-2.6.35-rc6-ac-20100729.patch
Patch201: linux-2.6.35-ac-pending.patch
-Patch202: linux-2.6.35-make-gma600-work-on-IA.patch
+Patch202: linux-2.6.35-aava-firmware-workaround.patch
+Patch203: linux-2.6.35-make-gma600-work-on-IA.patch
#
# End of the Moorsetown architecture patches
@@ -550,12 +551,14 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-# linux-2.6.35-rc6-ac-20100727.patch
+# linux-2.6.35-rc6-ac-20100729.patch
%patch200 -p1
# linux-2.6.35-ac-pending.patch
%patch201 -p1
-# linux-2.6.35-make-gma600-work-on-IA.patch
+# linux-2.6.35-aava-firmware-workaround.patch
%patch202 -p1
+# linux-2.6.35-make-gma600-work-on-IA.patch
+%patch203 -p1
#
# End of the Moorsetown architecture patches
--- kernel-mrst.spec
+++ kernel-mrst.spec
@@ -207,9 +207,10 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-Patch200: linux-2.6.35-rc6-ac-20100727.patch
+Patch200: linux-2.6.35-rc6-ac-20100729.patch
Patch201: linux-2.6.35-ac-pending.patch
-Patch202: linux-2.6.35-make-gma600-work-on-IA.patch
+Patch202: linux-2.6.35-aava-firmware-workaround.patch
+Patch203: linux-2.6.35-make-gma600-work-on-IA.patch
#
# End of the Moorsetown architecture patches
@@ -551,12 +552,14 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-# linux-2.6.35-rc6-ac-20100727.patch
+# linux-2.6.35-rc6-ac-20100729.patch
%patch200 -p1
# linux-2.6.35-ac-pending.patch
%patch201 -p1
-# linux-2.6.35-make-gma600-work-on-IA.patch
+# linux-2.6.35-aava-firmware-workaround.patch
%patch202 -p1
+# linux-2.6.35-make-gma600-work-on-IA.patch
+%patch203 -p1
#
# End of the Moorsetown architecture patches
--- kernel-n900.spec
+++ kernel-n900.spec
@@ -206,9 +206,10 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-Patch200: linux-2.6.35-rc6-ac-20100727.patch
+Patch200: linux-2.6.35-rc6-ac-20100729.patch
Patch201: linux-2.6.35-ac-pending.patch
-Patch202: linux-2.6.35-make-gma600-work-on-IA.patch
+Patch202: linux-2.6.35-aava-firmware-workaround.patch
+Patch203: linux-2.6.35-make-gma600-work-on-IA.patch
#
# End of the Moorsetown architecture patches
@@ -550,12 +551,14 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-# linux-2.6.35-rc6-ac-20100727.patch
+# linux-2.6.35-rc6-ac-20100729.patch
%patch200 -p1
# linux-2.6.35-ac-pending.patch
%patch201 -p1
-# linux-2.6.35-make-gma600-work-on-IA.patch
+# linux-2.6.35-aava-firmware-workaround.patch
%patch202 -p1
+# linux-2.6.35-make-gma600-work-on-IA.patch
+%patch203 -p1
#
# End of the Moorsetown architecture patches
--- kernel-netbook.spec
+++ kernel-netbook.spec
@@ -206,9 +206,10 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-Patch200: linux-2.6.35-rc6-ac-20100727.patch
+Patch200: linux-2.6.35-rc6-ac-20100729.patch
Patch201: linux-2.6.35-ac-pending.patch
-Patch202: linux-2.6.35-make-gma600-work-on-IA.patch
+Patch202: linux-2.6.35-aava-firmware-workaround.patch
+Patch203: linux-2.6.35-make-gma600-work-on-IA.patch
#
# End of the Moorsetown architecture patches
@@ -550,12 +551,14 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-# linux-2.6.35-rc6-ac-20100727.patch
+# linux-2.6.35-rc6-ac-20100729.patch
%patch200 -p1
# linux-2.6.35-ac-pending.patch
%patch201 -p1
-# linux-2.6.35-make-gma600-work-on-IA.patch
+# linux-2.6.35-aava-firmware-workaround.patch
%patch202 -p1
+# linux-2.6.35-make-gma600-work-on-IA.patch
+%patch203 -p1
#
# End of the Moorsetown architecture patches
--- kernel.spec
+++ kernel.spec
@@ -218,9 +218,10 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-Patch200: linux-2.6.35-rc6-ac-20100727.patch
+Patch200: linux-2.6.35-rc6-ac-20100729.patch
Patch201: linux-2.6.35-ac-pending.patch
-Patch202: linux-2.6.35-make-gma600-work-on-IA.patch
+Patch202: linux-2.6.35-aava-firmware-workaround.patch
+Patch203: linux-2.6.35-make-gma600-work-on-IA.patch
#
# End of the Moorsetown architecture patches
@@ -592,12 +593,14 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-# linux-2.6.35-rc6-ac-20100727.patch
+# linux-2.6.35-rc6-ac-20100729.patch
%patch200 -p1
# linux-2.6.35-ac-pending.patch
%patch201 -p1
-# linux-2.6.35-make-gma600-work-on-IA.patch
+# linux-2.6.35-aava-firmware-workaround.patch
%patch202 -p1
+# linux-2.6.35-make-gma600-work-on-IA.patch
+%patch203 -p1
#
# End of the Moorsetown architecture patches
other changes:
--------------
++++++ config-generic
--- config-generic
+++ config-generic
@@ -3496,3 +3496,7 @@
# CONFIG_X86_INTEL_CE is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_N_IFX_MUX is not set
+# CONFIG_MFLD_SENSORS is not set
+# CONFIG_SENSORS_AK8974COMPASS is not set
+# CONFIG_SENSORS_APDS9802PSPROXIMITY is not set
+
++++++ config-mrst
--- config-mrst
+++ config-mrst
@@ -173,3 +173,7 @@
CONFIG_PTI_ROUTER=y
CONFIG_VIDEO_MRST_MT9D113=y
CONFIG_N_IFX_MUX=y
+CONFIG_MFLD_SENSORS=y
+CONFIG_SENSORS_AK8974COMPASS=y
+CONFIG_SENSORS_APDS9802PSPROXIMITY=y
+
++++++ linux-2.6.35-aava-firmware-workaround.patch (new)
--- linux-2.6.35-aava-firmware-workaround.patch
+++ linux-2.6.35-aava-firmware-workaround.patch
+From 70d63e7fbc48b7f93b605fcbf9096eb4b8fa441c Mon Sep 17 00:00:00 2001
+From: Jiang, Chao <chao.jiang at intel.com>
+Date: Thu, 29 Jul 2010 11:17:28 +0800
+Subject: [PATCH] add cy8ctmg110 board info
+
+The current batch of Aava devices have a firmware bug where the
+touch screen is not present in the SFI tables.
+This patch manually fake-inserts this entry from the mrst
+code; and will be dropped once the fixed firmware becomes available.
+
+
+Signed-off-by: Jiang, Chao <chao.jiang at intel.com>
+---
+ arch/x86/kernel/mrst.c | 9 +++++++++
+ 1 files changed, 9 insertions(+), 0 deletions(-)
+
+diff --git a/arch/x86/kernel/mrst.c b/arch/x86/kernel/mrst.c
+index 88ca4cf..211b134 100644
+--- a/arch/x86/kernel/mrst.c
++++ b/arch/x86/kernel/mrst.c
+@@ -1121,6 +1121,15 @@ static int __init sfi_parse_i2cb(struct sfi_table_header *table)
+ i2c_register_board_info(busnum, &info, 1);
+ }
+
++ if (mrst_platform_id() == MRST_PLATFORM_AAVA_SC) {
++ /*Add AAVA SC touch screen*/
++ info.irq = 59;
++ info.addr = 0x38;
++ info.platform_data = NULL;
++ strcpy(info.type, "cy8ctmg110");
++ i2c_register_board_info(0, &info, 1);
++ }
++
+ return 0;
+ }
+
+--
+1.6.2.5
+
++++++ linux-2.6.35-ac-pending.patch
--- linux-2.6.35-ac-pending.patch
+++ linux-2.6.35-ac-pending.patch
@@ -1,66 +1,3 @@
-diff --git a/drivers/staging/mrst/drv/psb_drv.c b/drivers/staging/mrst/drv/psb_drv.c
-index 25e521a..9bfc684 100644
---- a/drivers/staging/mrst/drv/psb_drv.c
-+++ b/drivers/staging/mrst/drv/psb_drv.c
-@@ -83,36 +83,33 @@ module_param_named(topaz_pmpolicy, drm_topaz_pmpolicy, int, 0600);
- module_param_named(topaz_sbuswa, drm_topaz_sbuswa, int, 0600);
- module_param_named(ospm, drm_psb_ospm, int, 0600);
-
--#if 0
--#ifndef CONFIG_X86_PAT
--#warning "Don't build this driver without PAT support!!!"
-+static struct pci_device_id pciidlist[] = {
-+#ifdef SGX535
-+ {0x8086, 0x8108, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_PSB_8108},
-+ {0x8086, 0x8109, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_PSB_8109},
-+ {0x8086, 0x4100, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100},
-+ {0x8086, 0x4101, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100},
-+ {0x8086, 0x4102, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100},
-+ {0x8086, 0x4103, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100},
-+ {0x8086, 0x4104, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100},
-+ {0x8086, 0x4105, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100},
-+ {0x8086, 0x4106, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100},
-+ {0x8086, 0x4107, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100},
- #endif
-+#ifdef SGX540
-+ {0x8086, 0x0130, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130},
-+ {0x8086, 0x0131, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130},
-+ {0x8086, 0x0132, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130},
-+ {0x8086, 0x0133, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130},
-+ {0x8086, 0x0134, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130},
-+ {0x8086, 0x0135, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130},
-+ {0x8086, 0x0136, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130},
-+ {0x8086, 0x0137, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130},
- #endif
--#define psb_PCI_IDS \
-- {0x8086, 0x8108, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_PSB_8108}, \
-- {0x8086, 0x8109, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_PSB_8109}, \
-- {0x8086, 0x4100, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
-- {0x8086, 0x4101, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
-- {0x8086, 0x4102, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
-- {0x8086, 0x4103, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
-- {0x8086, 0x4104, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
-- {0x8086, 0x4105, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
-- {0x8086, 0x4106, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
-- {0x8086, 0x4107, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
-- {0x8086, 0x0130, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130}, \
-- {0x8086, 0x0131, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130}, \
-- {0x8086, 0x0132, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130}, \
-- {0x8086, 0x0133, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130}, \
-- {0x8086, 0x0134, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130}, \
-- {0x8086, 0x0135, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130}, \
-- {0x8086, 0x0136, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130}, \
-- {0x8086, 0x0137, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MDFLD_0130}, \
- {0, 0, 0}
--
--static struct pci_device_id pciidlist[] = {
-- psb_PCI_IDS
- };
-
-+MODULE_DEVICE_TABLE(pci, pciidlist);
- /*
- * Standard IOCTLs.
- */
--- linux-2.6.34/drivers/staging/mrst/drv/psb_intel_display2.c~ 2010-07-26 11:39:36.000000000 -0400
+++ linux-2.6.34/drivers/staging/mrst/drv/psb_intel_display2.c 2010-07-26 12:17:17.904000652 -0400
@@ -798,7 +798,7 @@
++++++ linux-2.6.35-rc6-ac-20100729.patch (new)
--- linux-2.6.35-rc6-ac-20100729.patch
+++ linux-2.6.35-rc6-ac-20100729.patch
+diff --git a/Documentation/ABI/testing/sysfs-bus-devices-i2c-isl29020 b/Documentation/ABI/testing/sysfs-bus-devices-i2c-isl29020
+new file mode 100644
+index 0000000..bc71757
+--- /dev/null
++++ b/Documentation/ABI/testing/sysfs-bus-devices-i2c-isl29020
+@@ -0,0 +1,29 @@
++
++Where: /sys/bus/i2c/devices/.../sensing_range
++Date: April 2010
++Kernel Version: 2.6.36?
++Contact: alan.cox at intel.com
++Description: Reports the sensing range configured on the ISL29020
++ hardware (1/4/16/64000). Writing a value between 1 and 4
++ sets the sensing range to 1/4/16/64000.
++
++
++Where: /sys/bus/i2c/devices/.../power_state
++Date: April 2010
++Kernel Version: 2.6.36?
++Contact: alan.cox at intel.com
++Description: Write 1 to bring the device out of power saving mode and 0
++ to return it to power saving. When read returns 0 or 1
++ indicating the current power state.
++
++Where: /sys/bus/i2c/devices/.../lux_output
++Date: April 2010
++Kernel Version: 2.6.36?
++Contact: alan.cox at intel.com
++Description: Report the lux level being read by the sensor.
++
++
++
++
++
++
+diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352 b/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352
+new file mode 100644
+index 0000000..fbedf77
+--- /dev/null
++++ b/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352
+@@ -0,0 +1,21 @@
++Where: /sys/bus/i2c/devices/.../heading
++Date: April 2010
++Kernel Version: 2.6.36?
++Contact: alan.cox at intel.com
++Description: Reports the current heading from the compass as a floating
++ point value in degrees.
++
++Where: /sys/bus/i2c/devices/.../power_state
++Date: April 2010
++Kernel Version: 2.6.36?
++Contact: alan.cox at intel.com
++Description: Sets the power state of the device. 0 sets the device into
++ sleep mode, 1 wakes it up.
++
++Where: /sys/bus/i2c/devices/.../calibration
++Date: April 2010
++Kernel Version: 2.6.36?
++Contact: alan.cox at intel.com
++Description: Sets the calibration on or off (1 = on, 0 = off). See the
++ chip data sheet.
++
+diff --git a/Documentation/networking/caif/spi_porting.txt b/Documentation/networking/caif/spi_porting.txt
+new file mode 100644
+index 0000000..61d7c92
+--- /dev/null
++++ b/Documentation/networking/caif/spi_porting.txt
+@@ -0,0 +1,208 @@
++- CAIF SPI porting -
++
++- CAIF SPI basics:
++
++Running CAIF over SPI needs some extra setup, owing to the nature of SPI.
++Two extra GPIOs have been added in order to negotiate the transfers
++ between the master and the slave. The minimum requirement for running
++CAIF over SPI is a SPI slave chip and two GPIOs (more details below).
++Please note that running as a slave implies that you need to keep up
++with the master clock. An overrun or underrun event is fatal.
++
++- CAIF SPI framework:
++
++To make porting as easy as possible, the CAIF SPI has been divided in
++two parts. The first part (called the interface part) deals with all
++generic functionality such as length framing, SPI frame negotiation
++and SPI frame delivery and transmission. The other part is the CAIF
++SPI slave device part, which is the module that you have to write if
++you want to run SPI CAIF on a new hardware. This part takes care of
++the physical hardware, both with regard to SPI and to GPIOs.
++
++- Implementing a CAIF SPI device:
++
++ - Functionality provided by the CAIF SPI slave device:
++
++ In order to implement a SPI device you will, as a minimum,
++ need to implement the following
++ functions:
++
++ int (*init_xfer) (struct cfspi_xfer * xfer, struct cfspi_dev *dev):
++
++ This function is called by the CAIF SPI interface to give
++ you a chance to set up your hardware to be ready to receive
++ a stream of data from the master. The xfer structure contains
++ both physical and logical adresses, as well as the total length
++ of the transfer in both directions.The dev parameter can be used
++ to map to different CAIF SPI slave devices.
++
++ void (*sig_xfer) (bool xfer, struct cfspi_dev *dev):
++
++ This function is called by the CAIF SPI interface when the output
++ (SPI_INT) GPIO needs to change state. The boolean value of the xfer
++ variable indicates whether the GPIO should be asserted (HIGH) or
++ deasserted (LOW). The dev parameter can be used to map to different CAIF
++ SPI slave devices.
++
++ - Functionality provided by the CAIF SPI interface:
++
++ void (*ss_cb) (bool assert, struct cfspi_ifc *ifc);
++
++ This function is called by the CAIF SPI slave device in order to
++ signal a change of state of the input GPIO (SS) to the interface.
++ Only active edges are mandatory to be reported.
++ This function can be called from IRQ context (recommended in order
++ not to introduce latency). The ifc parameter should be the pointer
++ returned from the platform probe function in the SPI device structure.
++
++ void (*xfer_done_cb) (struct cfspi_ifc *ifc);
++
++ This function is called by the CAIF SPI slave device in order to
++ report that a transfer is completed. This function should only be
++ called once both the transmission and the reception are completed.
++ This function can be called from IRQ context (recommended in order
++ not to introduce latency). The ifc parameter should be the pointer
++ returned from the platform probe function in the SPI device structure.
++
++ - Connecting the bits and pieces:
++
++ - Filling in the SPI slave device structure:
++
++ Connect the necessary callback functions.
++ Indicate clock speed (used to calculate toggle delays).
++ Chose a suitable name (helps debugging if you use several CAIF
++ SPI slave devices).
++ Assign your private data (can be used to map to your structure).
++
++ - Filling in the SPI slave platform device structure:
++ Add name of driver to connect to ("cfspi_sspi").
++ Assign the SPI slave device structure as platform data.
++
++- Padding:
++
++In order to optimize throughput, a number of SPI padding options are provided.
++Padding can be enabled independently for uplink and downlink transfers.
++Padding can be enabled for the head, the tail and for the total frame size.
++The padding needs to be correctly configured on both sides of the link.
++The padding can be changed via module parameters in cfspi_sspi.c or via
++the sysfs directory of the cfspi_sspi driver (before device registration).
++
++- CAIF SPI device template:
++
++/*
++ * Copyright (C) ST-Ericsson AB 2010
++ * Author: Daniel Martensson / Daniel.Martensson at stericsson.com
++ * License terms: GNU General Public License (GPL), version 2.
++ *
++ */
++
++#include <linux/init.h>
++#include <linux/module.h>
++#include <linux/device.h>
++#include <linux/wait.h>
++#include <linux/interrupt.h>
++#include <linux/dma-mapping.h>
++#include <net/caif/caif_spi.h>
++
++MODULE_LICENSE("GPL");
++
++struct sspi_struct {
++ struct cfspi_dev sdev;
++ struct cfspi_xfer *xfer;
++};
++
++static struct sspi_struct slave;
++static struct platform_device slave_device;
++
++static irqreturn_t sspi_irq(int irq, void *arg)
++{
++ /* You only need to trigger on an edge to the active state of the
++ * SS signal. Once a edge is detected, the ss_cb() function should be
++ * called with the parameter assert set to true. It is OK
++ * (and even advised) to call the ss_cb() function in IRQ context in
++ * order not to add any delay. */
++
++ return IRQ_HANDLED;
++}
++
++static void sspi_complete(void *context)
++{
++ /* Normally the DMA or the SPI framework will call you back
(292521 more lines skipped)
++++++ series
--- series
+++ series
@@ -51,8 +51,9 @@
# The main consolidated MRST/MFLD tree from
# git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
#
-linux-2.6.35-rc6-ac-20100727.patch
+linux-2.6.35-rc6-ac-20100729.patch
linux-2.6.35-ac-pending.patch
+linux-2.6.35-aava-firmware-workaround.patch
linux-2.6.35-make-gma600-work-on-IA.patch
#
More information about the MeeGo-commits
mailing list