Hi Arjan,

CONFIG_MMC_CLKGATE has to be enabled for sdhci rpm to work. Could you please 
help do that?

Thanks
-Yong

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Arjan van de Ven
> Sent: Thursday, April 07, 2011 3:46 AM
> To: [email protected]
> Subject: [meego-commits] 15836: Changes to
> Trunk:Testing/kernel-adaptation-mrst
>
> Hi,
> I have made the following changes to kernel-adaptation-mrst in project
> Trunk:Testing. Please review and accept ASAP.
>
> Thank You,
> Arjan van de Ven
>
> [This message was auto-generated]
>
> ---
>
> Request #15836:
>
>   submit:   devel:kernel/kernel-adaptation-mrst(r82) ->
> Trunk:Testing/kernel-adaptation-mrst
>
>
> Message:
>     various power fixes
>
> State:   new          2011-04-06T12:46:06 arjan
> Comment: None
>
>
>
> changes files:
> --------------
> --- kernel.changes
> +++ kernel.changes
> @@ -0,0 +1,5 @@
> +* Wed Apr 6 2011 - Arjan van de Ven <[email protected]> - 2.6.37.6
> +- audio driver fixes for speaker output
> +- power management enabling for gpio, spi, audio, dma, sdhci
> +- add 8 bit probing to MMC
> +
>
> new:
> ----
>   linux-2.6.37-20110406-ac.patch
>
> spec files:
> -----------
> --- kernel-adaptation-mrst.spec
> +++ kernel-adaptation-mrst.spec
> @@ -197,7 +197,7 @@
>  # The main consolidated MRST tree from
>  # git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
>  #
> -Patch200: linux-2.6.37-20110329-ac.patch
> +Patch200: linux-2.6.37-20110406-ac.patch
>  # and revert a few pieces of it that cause bugs
>  Patch201: linux-2.6.37-revert-spi-bugs.patch
>
> @@ -262,33 +262,33 @@
>
>
>  # wiggle a random GPIO to turn on speakers
> -Patch224: linux-2.6.37-mm-spkr.patch
> -Patch225: linux-2.6.37-mm-spkr-sel-fix.patch
> +#linux-2.6.37-mm-spkr.patch
> +#linux-2.6.37-mm-spkr-sel-fix.patch
>
>
>  # correct the SDHCI quirks for the 2nd and 3rd SDHCI port for C0/C1 stepping
> -Patch226: linux-2.6.37-sdhci-quirks.patch
> +Patch224: linux-2.6.37-sdhci-quirks.patch
>
>  # etk SPI touchscreen driver
>  #linux-2.6.37-touchscreen-etk.patch
>  #linux-2.6.37-acer-touch-loopback-srcore.patch
> -Patch227: linux-2.6.37-acer-loopback.patch
> +Patch225: linux-2.6.37-acer-loopback.patch
>  #linux-2.6.37-ektf2136_spi_update_version-201.patch
>  #linux-2.6.37-ektf2136_spi_support_sr-201.patch
>  #linux-2.6.37-ektf2136-spi-Add-support-for-new-protocol.patch
>
>  # ratelimit some battery printk's
> -Patch228: linux-2.6.37-battery-ratelimit.patch
> -Patch229: linux-2.6.37-battery-dependency.patch
> +Patch226: linux-2.6.37-battery-ratelimit.patch
> +Patch227: linux-2.6.37-battery-dependency.patch
>
>
>  # Camera driver patches
> -Patch230: linux-2.6.37-camera-makefile-glue.patch
> -Patch231: linux-2.6.37-camera-driver.patch
> -Patch232: linux-2.6.37-camera-driver-adjust.patch
> -Patch233: linux-2.6.37-camera-fix-subdev-call.patch
> -Patch234: linux-2.6.37-camera-pm.patch
> -Patch235: linux-2.6.37-camera-ov5640-ov9740-version-0.92-2011-04-01.patch
> +Patch228: linux-2.6.37-camera-makefile-glue.patch
> +Patch229: linux-2.6.37-camera-driver.patch
> +Patch230: linux-2.6.37-camera-driver-adjust.patch
> +Patch231: linux-2.6.37-camera-fix-subdev-call.patch
> +Patch232: linux-2.6.37-camera-pm.patch
> +Patch233: linux-2.6.37-camera-ov5640-ov9740-version-0.92-2011-04-01.patch
>
>
>
> @@ -483,7 +483,7 @@
>  # The main consolidated MRST tree from
>  # git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
>  #
> -# linux-2.6.37-20110329-ac.patch
> +# linux-2.6.37-20110406-ac.patch
>  %patch200 -p1
>  # and revert a few pieces of it that cause bugs
>  # linux-2.6.37-revert-spi-bugs.patch
> @@ -572,45 +572,43 @@
>
>
>  # wiggle a random GPIO to turn on speakers
> -# linux-2.6.37-mm-spkr.patch
> -%patch224 -p1
> -# linux-2.6.37-mm-spkr-sel-fix.patch
> -%patch225 -p1
> +#linux-2.6.37-mm-spkr.patch
> +#linux-2.6.37-mm-spkr-sel-fix.patch
>
>
>  # correct the SDHCI quirks for the 2nd and 3rd SDHCI port for C0/C1 stepping
>  # linux-2.6.37-sdhci-quirks.patch
> -%patch226 -p1
> +%patch224 -p1
>
>  # etk SPI touchscreen driver
>  #linux-2.6.37-touchscreen-etk.patch
>  #linux-2.6.37-acer-touch-loopback-srcore.patch
>  # linux-2.6.37-acer-loopback.patch
> -%patch227 -p1
> +%patch225 -p1
>  #linux-2.6.37-ektf2136_spi_update_version-201.patch
>  #linux-2.6.37-ektf2136_spi_support_sr-201.patch
>  #linux-2.6.37-ektf2136-spi-Add-support-for-new-protocol.patch
>
>  # ratelimit some battery printk's
>  # linux-2.6.37-battery-ratelimit.patch
> -%patch228 -p1
> +%patch226 -p1
>  # linux-2.6.37-battery-dependency.patch
> -%patch229 -p1
> +%patch227 -p1
>
>
>  # Camera driver patches
>  # linux-2.6.37-camera-makefile-glue.patch
> -%patch230 -p1
> +%patch228 -p1
>  # linux-2.6.37-camera-driver.patch
> -%patch231 -p1
> +%patch229 -p1
>  # linux-2.6.37-camera-driver-adjust.patch
> -%patch232 -p1
> +%patch230 -p1
>  # linux-2.6.37-camera-fix-subdev-call.patch
> -%patch233 -p1
> +%patch231 -p1
>  # linux-2.6.37-camera-pm.patch
> -%patch234 -p1
> +%patch232 -p1
>  # linux-2.6.37-camera-ov5640-ov9740-version-0.92-2011-04-01.patch
> -%patch235 -p1
> +%patch233 -p1
>
>
>
>
> other changes:
> --------------
>
> ++++++ linux-2.6.37-20110406-ac.patch (new)
> --- linux-2.6.37-20110406-ac.patch
> +++ linux-2.6.37-20110406-ac.patch
> +diff --git a/Documentation/hwmon/intel_over_current_detector
> b/Documentation/hwmon/intel_over_current_detector
> +new file mode 100644
> +index 0000000..d9483b0
> +--- /dev/null
> ++++ b/Documentation/hwmon/intel_over_current_detector
> +@@ -0,0 +1,86 @@
> ++Kernel driver over current detection driver
> ++===========================================
> ++
> ++Supported systems:
> ++  * Intel Medfield Platform
> ++
> ++Author: Durgadoss R
> ++
> ++Description
> ++-----------
> ++
> ++This driver monitors the current drawn by the platform, and detects the
> ++peak current conditions. When the current drawn is more than the
> ++configured limit for a period of time (which is specified by a timer), an
> ++interrupt is generated. The current limit and the timer value can be
> ++configured at run time.
> ++
> ++The current thresholds aka BATTCURRENTLIMITS(BC) are of two types:
> ++    1.warning threshold(BC1)
> ++            at which the system should take actions to bring the
> ++            current consumption down.
> ++    2.shutdown threshold(BC2)
> ++            at which the hardware does a COLDOFF.
> ++
> ++The timer thresholds are of three types:
> ++    1.warning threshold(T1)
> ++            This corresponds to the first flag for time that the battery
> ++            current has been above BC1. An interrupt is generated to allow
> ++            software to correct the situation based on use-case.
> ++    2.hardware action threshold(T2)
> ++            This corresponds to the second flag for time that the battery
> ++            current has been above BC1. It signifies that the system
> ++            should control high current subsystems through hardware.
> ++            Besides a general interrupt, audio_volume_crush, vibra_disable
> ++            signals are sent.
> ++    3.shutdown threshold(T3)
> ++            This final flag signifies that when the system current exceeds
> ++            the threshold for more than T3, system should shutdown.
> ++
> ++Following table summarizes the exported sysfs files:
> ++
> ++bcu_status(RW)           -  To enable/disable burst control unit.
> ++                    0 - enables bcu, 1 - disables bcu.
> ++accumulation_time(RW)-  Time since last clearing/overflow of
> warning_count
> ++                    in milli seconds. Writing 0 resets the acc_time and
> ++                    also clears both the warning counters.
> ++warning_count(RO)    -  Two space seperated values that indicate the
> number
> ++                    of times the current thresholds have been crossed.
> ++action_mask(RW)          -  A hex value to enable/disable specific
> ++                    actions taken when current violation happens.
> ++                    bits [b4 b3 b2 b1 b0] control [a4 a3 a2 a1 a0] actions
> ++                    respectively. a4 - camera output, a3 - sys burst,
> ++                    a2 - SOC burst enable, a1 - vibra, a0 - audio output.
> ++                    bits [b7 b6 b5] - Reserved.
> ++                    Default value:08 (sys burst output is enabled).
> ++action_status(RO)    -  A hex value showing the status of actions taken
> ++                    since the __last__ interrupt.
> ++                    b7 - T3 violation
> ++                    b6 - T2 violation
> ++                    b5 - T1 violation
> ++                    b4 - camera action taken status
> ++                    b3 - sys burst disable action taken status
> ++                    b2 - SOC burst disable action taken status
> ++                    b1 - vibra disable
> ++                    b0 - audio volume crush
> ++                    A '1' in a bit position indicates that particular
> ++                    action has been taken.
> ++current_warning(RW)  -  This gives the current(in mA) at which a warning
> is
> ++                    generated. Range: 1400 to 4800. Default:3000
> ++current_shutdown(RW) -  This gives the current(in mA) at which system
> shutdown
> ++                    is initiated. Range:1800 to 5800. Default:3800
> ++timer_warning(RW)    -  Time above current_warning limit at which
> interrupts
> ++                    are trigerred(so that software can bring the current
> ++                    consumption down). Values are in micro seconds.
> ++                    Range:200 to 7700 in steps of 500
> ++timer_hw_action(RW)  -  Time above current_warning limit at which the
> system
> ++                    is trigerred into hardware control to bring down the
> ++                    current consumption. Values are in micro seconds.
> ++                    Range:200 to 7700 in steps of 500
> ++timer_shutdown(RW)   -  Time above current_warning limit at which a
> hardware
> ++                    shutdown event is trigerred. The timer values are in
> ++                    micro seconds.
> ++                    Range:1000 to 15000 in steps of 1000
> ++For all timer interfaces, tolerance shall be 5% maximum.
> ++All timers start running concurrently once
> current_warning/current_shutdown
> ++is crossed.
> +diff --git a/Documentation/kernel-parameters.txt
> b/Documentation/kernel-parameters.txt
> +index 596bb3c..fb1f1d0 100644
> +--- a/Documentation/kernel-parameters.txt
> ++++ b/Documentation/kernel-parameters.txt
> +@@ -43,11 +43,12 @@ parameter is applicable:
> +     AVR32   AVR32 architecture is enabled.
> +     AX25    Appropriate AX.25 support is enabled.
> +     BLACKFIN Blackfin architecture is enabled.
> ++    DMI     Desktop Management Interface is enabled
> ++    DRM     Direct Rendering Management support is enabled.
> ++    DYNAMIC_DEBUG Build in debug messages and enable them at runtime
> +     EDD     BIOS Enhanced Disk Drive Services (EDD) is enabled
> +     EFI     EFI Partitioning (GPT) is enabled
> +     EIDE    EIDE/ATAPI support is enabled.
> +-    DRM     Direct Rendering Management support is enabled.
> +-    DYNAMIC_DEBUG Build in debug messages and enable them at runtime
> +     FB      The frame buffer device is enabled.
> +     GCOV    GCOV profiling is enabled.
> +     HW      Appropriate hardware is enabled.
> +@@ -390,6 +391,21 @@ and is between 256 and 4096 characters. It is
> defined in the file
> +                     Format: <io>,<irq>,<mode>
> +                     See header of drivers/net/hamradio/baycom_ser_hdx.c.
> +
> ++    board_name=     [DMI]
> ++                    Override reported name in firmware DMI data. Used
> ++                    for testing and for checking board specific
> ++                    workarounds
> ++
> ++    board_vendor=   [DMI]
> ++                    Override reported vendor in firmware DMI data. Used
> ++                    for testing and for checking board specific
> ++                    workarounds
> ++
> ++    board_version=  [DMI]
> ++                    Override reported version in firmware DMI data. Used
> ++                    for testing and for checking board specific
> ++                    workarounds
> ++
> +     boot_delay=     Milliseconds to delay each printk during boot.
> +                     Values larger than 10 seconds (10000) are changed to
> +                     no delay (0).
> +diff --git a/Documentation/pti/pti_intel_mid.txt
> b/Documentation/pti/pti_intel_mid.txt
> +new file mode 100644
> +index 0000000..651fcf5
> +--- /dev/null
> ++++ b/Documentation/pti/pti_intel_mid.txt
> +@@ -0,0 +1,89 @@
> ++The Intel MID PTI project is HW implemented in Intel Atom
> ++system-on-a-chip designs based on the Parallel Trace
> ++Interface for MIPI P1149.7 cJTAG standard.  The kernel solution
> ++for this platform involves the following files:
> ++
> ++./include/linux/pti.h
> ++./include/linux/n_tracesink.h
> ++./drivers/.../n_tracerouter.c
> ++./drivers/.../n_tracesink.c
> ++./drivers/.../pti.c
> ++
> ++pti.c is the driver that enables various debugging features
> ++popular on certain mobile manufacturers.  n_tracerouter.c
> ++and n_tracesink.c allow extra system information to be
> ++collected and routed to the pti driver, such as trace
> ++debugging data from a modem.  Altough n_tracerouter
> ++and n_tracesink are a part of the complete PTI solution,
> ++these two line disciplines can work separate from
> ++pti.c and route any data stream from one /dev/tty node
> ++to another /dev/tty node via kernel-space.  This provides
> ++a stable, reliable connection that will not break unless
> ++the user-space application shuts down (plus avoids
> ++kernel->user->kernel context switch overheads of routing
> ++data).
> ++
> ++An example debugging usage for this driver system:
> ++   *Hook /dev/ttyPTI0 to syslogd.  Opening this port will also start
> ++    a console device to further capture debugging messages to PTI.
> ++   *Hook /dev/ttyPTI1 to modem debugging data to write to PTI HW.
> ++    This is where n_tracerouter and n_tracesink are used.
> ++   *Hook /dev/pti to a user-level debugging application for writing
> ++    to PTI HW.
> ++   *Use mipi_* Kernel Driver API in other device drivers for
> ++    debugging to PTI by first requesting a PTI write address via
> ++    mipi_request_masterchannel(1).
> ++
> ++Example 'privileged' (normal user privileges are not enough)
> ++user-space code on how to setup the n_tracerouter and n_tracesink
> ++ldisc drivers (note: n_tracerouter depends on n_tracesink):
> ++
> ++/////////// To hook up n_tracerouter and n_tracesink /////////
> ++
> ++#include <errno.h>
> ++#define ONE_TTY "/dev/ttyOne"
> ++#define TWO_TTY "/dev/ttyTwo"
> ++
> ++// needed global to hand onto ldisc connection
> ++static int g_fd_source = -1;
> ++static int g_fd_sink  = -1;
> ++
> ++// grab LDISC values from loaded ldisc drivers from /proc/tty/ldiscs
> ++int source_ldisc_num, sink_ldisc_num = -1;
> ++int retval;
> ++
> ++g_fd_source = open(ONE_TTY, O_RDWR); // must be R/W
> ++g_fd_sink   = open(TWO_TTY, O_RDWR); // must be R/W
> ++
> ++if (g_fd_source <= 0) || (g_fd_sink <= 0) {
> ++   // doubt you'll want to use these exact error lines of code
> (99979 more lines skipped)
>
> ++++++ linux-2.6.37-sdhci-quirks.patch
> --- linux-2.6.37-sdhci-quirks.patch
> +++ linux-2.6.37-sdhci-quirks.patch
> @@ -12,7 +12,7 @@
>  --- a/drivers/mmc/host/sdhci-pci.c
>  +++ b/drivers/mmc/host/sdhci-pci.c
>  @@ -160,11 +160,15 @@ static int mrst_hc_probe(struct sdhci_pci_chip
> *chip)
> -     .quirks         = SDHCI_QUIRK_BROKEN_ADMA |
> SDHCI_QUIRK_NO_HISPD_BIT,
> +     .probe_slot             = mrst_hc_probe_slot,
>   };
>
>  -static const struct sdhci_pci_fixes sdhci_intel_mrst_hc1_hc2 = {
>
> ++++++ series
> --- series
> +++ series
> @@ -47,7 +47,7 @@
>  # The main consolidated MRST tree from
>  # git//git.kernel.org/pub/scm/linux/kernel/git/alan/linux-2.6-mid-ref
>  #
> -linux-2.6.37-20110329-ac.patch
> +linux-2.6.37-20110406-ac.patch
>  # and revert a few pieces of it that cause bugs
>  linux-2.6.37-revert-spi-bugs.patch
>
> @@ -112,8 +112,8 @@
>
>
>  # wiggle a random GPIO to turn on speakers
> -linux-2.6.37-mm-spkr.patch
> -linux-2.6.37-mm-spkr-sel-fix.patch
> +#linux-2.6.37-mm-spkr.patch
> +#linux-2.6.37-mm-spkr-sel-fix.patch
>
>
>  # correct the SDHCI quirks for the 2nd and 3rd SDHCI port for C0/C1 stepping
>
> _______________________________________________
> MeeGo-commits mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-commits
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to