* [PATCH v2] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
From: Rafael J. Wysocki @ 2013-01-30 13:57 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130130134939.GE2757@S2101-09.ap.freescale.net>
On Wednesday, January 30, 2013 09:49:41 PM Shawn Guo wrote:
> On Wed, Jan 30, 2013 at 02:40:35PM +0100, Rafael J. Wysocki wrote:
> > > > Mark, AnilKumar,
> > > >
> > > > I only compile-tested it on highbank and omap2. Please give it a test
> > > > no hardware to make sure cpufreq-cpu0 still works for you. Thanks.
> > >
> > > Hi Shawn,
> > >
> > > I hope this is based on linux-omap/master, to test the driver I have
> > > to add some patches on top of this patch, because of recent changes.
> > > I will provide the test details once I am done.
> >
> > Shawn, does it mean I need to wait with applying the patch or will OMAP2
> > work as is?
> >
> I would expect that omap2/am33xx should work as it is, but I do not
> have hardware to confirm that.
>
> Also as the patch touches a few files in arch/arm/mach-omap2, we may
> need an ACK from Tony.
>
> Actually, I prefer to move omap2 bits into a separate patch and have
> it go via omap tree to avoid the possible conflict with cpufreq and
> arm-soc tree. What do you say? If you agree, I will re-iterate the
> patch to do so.
Yes, please do as you think is appropriate.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
^ permalink raw reply
* [PATCH 2/2] arm: dts: omap5-evm: Add mcspi data
From: Sourav Poddar @ 2013-01-30 13:49 UTC (permalink / raw)
To: linux-arm-kernel
Add mcspi node and pinmux data for omap5 mcspi controller.
Tested on omap5430 evm with 3.8-rc4 custom kernel.
Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
---
Develops this on the patch[1] submitted in mainline
[1]: http://www.spinics.net/lists/kernel/msg1473163.html
arch/arm/boot/dts/omap5-evm.dts | 46 +++++++++++++++++++++++++++++++++++++++
1 files changed, 46 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-evm.dts b/arch/arm/boot/dts/omap5-evm.dts
index a96acc0..252edda 100644
--- a/arch/arm/boot/dts/omap5-evm.dts
+++ b/arch/arm/boot/dts/omap5-evm.dts
@@ -115,6 +115,33 @@
0x186 0x100 /* i2c4_sda INPUTENABLE | MODE0 */
>;
};
+
+ mcspi2_pins: pinmux_mcspi2_pins {
+ pinctrl-single,pins = <
+ 0xbc 0x100
+ 0xbe 0x100
+ 0xc0 0x118
+ 0xc2 0x0
+ >;
+ };
+
+ mcspi3_pins: pinmux_mcspi3_pins {
+ pinctrl-single,pins = <
+ 0x78 0x101
+ 0x7a 0x101
+ 0x7c 0x101
+ 0x7e 0x101
+ >;
+ };
+
+ mcspi4_pins: pinmux_mcspi4_pins {
+ pinctrl-single,pins = <
+ 0x164 0x101
+ 0x168 0x101
+ 0x16a 0x101
+ 0x16c 0x101
+ >;
+ };
};
&mmc1 {
@@ -213,3 +240,22 @@
cs1-used;
device-handle = <&samsung_K3PE0E000B>;
};
+
+&mcspi1 {
+
+};
+
+&mcspi2 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&i2c5_pins>;
+};
+
+&mcspi3 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&i2c5_pins>;
+};
+
+&mcspi4 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&i2c5_pins>;
+};
--
1.7.1
^ permalink raw reply related
* [PATCH v2] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
From: Shawn Guo @ 2013-01-30 13:49 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <2871120.foIQeGmlHR@vostro.rjw.lan>
On Wed, Jan 30, 2013 at 02:40:35PM +0100, Rafael J. Wysocki wrote:
> > > Mark, AnilKumar,
> > >
> > > I only compile-tested it on highbank and omap2. Please give it a test
> > > no hardware to make sure cpufreq-cpu0 still works for you. Thanks.
> >
> > Hi Shawn,
> >
> > I hope this is based on linux-omap/master, to test the driver I have
> > to add some patches on top of this patch, because of recent changes.
> > I will provide the test details once I am done.
>
> Shawn, does it mean I need to wait with applying the patch or will OMAP2
> work as is?
>
I would expect that omap2/am33xx should work as it is, but I do not
have hardware to confirm that.
Also as the patch touches a few files in arch/arm/mach-omap2, we may
need an ACK from Tony.
Actually, I prefer to move omap2 bits into a separate patch and have
it go via omap tree to avoid the possible conflict with cpufreq and
arm-soc tree. What do you say? If you agree, I will re-iterate the
patch to do so.
Shawn
^ permalink raw reply
* [PATCH 1/2] arm: dts: omap5: add SPI devices to OMAP5 DeviceTree file
From: Sourav Poddar @ 2013-01-30 13:49 UTC (permalink / raw)
To: linux-arm-kernel
From: Felipe Balbi <balbi@ti.com>
Add all 4 mcspi instances to omap5.dtsi file.
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 40 ++++++++++++++++++++++++++++++++++++++++
1 files changed, 40 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 790bb2a..9e182a9 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -241,6 +241,46 @@
ti,hwmods = "i2c5";
};
+ mcspi1: spi at 48098000 {
+ compatible = "ti,omap4-mcspi";
+ reg = <0x48098000 0x200>;
+ interrupts = <0 65 0x4>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ ti,hwmods = "mcspi1";
+ ti,spi-num-cs = <4>;
+ };
+
+ mcspi2: spi at 4809a000 {
+ compatible = "ti,omap4-mcspi";
+ reg = <0x4809a000 0x200>;
+ interrupts = <0 66 0x4>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ ti,hwmods = "mcspi2";
+ ti,spi-num-cs = <2>;
+ };
+
+ mcspi3: spi at 480b8000 {
+ compatible = "ti,omap4-mcspi";
+ reg = <0x480b8000 0x200>;
+ interrupts = <0 91 0x4>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ ti,hwmods = "mcspi3";
+ ti,spi-num-cs = <2>;
+ };
+
+ mcspi4: spi at 480ba000 {
+ compatible = "ti,omap4-mcspi";
+ reg = <0x480ba000 0x200>;
+ interrupts = <0 48 0x4>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ ti,hwmods = "mcspi4";
+ ti,spi-num-cs = <1>;
+ };
+
uart1: serial at 4806a000 {
compatible = "ti,omap4-uart";
reg = <0x4806a000 0x100>;
--
1.7.1
^ permalink raw reply related
* [PATCH 0/2] add omap mcspi device tree data
From: Sourav Poddar @ 2013-01-30 13:48 UTC (permalink / raw)
To: linux-arm-kernel
Patch series adds omap5 evm mcspi nodes and pinctrl
data in omap5.dtsi and omap5-evm.dts files.
Felipe Balbi (1):
arm: dts: omap5: add SPI devices to OMAP5 DeviceTree file
Sourav Poddar (1):
arm: dts: omap5-evm: Add mcspi data
arch/arm/boot/dts/omap5-evm.dts | 46 +++++++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/omap5.dtsi | 40 +++++++++++++++++++++++++++++++++
2 files changed, 86 insertions(+), 0 deletions(-)
^ permalink raw reply
* [BUG] snowball board locks up on boot
From: Steven Rostedt @ 2013-01-30 13:47 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1359551685.17639.92.camel@gandalf.local.home>
On Wed, 2013-01-30 at 08:14 -0500, Steven Rostedt wrote:
> On Wed, 2013-01-30 at 09:01 +0000, Lee Jones wrote:
>
> > Can you provide your bootlog please Steven?
> >
>
> Here's the bootlog after I reverted the patch and successfully booted:
>
And here's the bootlog before I reverted. Actually, this log is from my
bisect log, where it found the bad commit:
tartup failed
EMMC: 0, MMC: 1
In: serial
Out: serial
Err: serial
Net: smc911x-0
Hit any key to stop autoboot: 3 \b\b\b 2 \b\b\b 1 \b\b\b 0
Card did not respond to voltage select!
smc911x: detected LAN9221 controller
smc911x: phy initialized
smc911x: MAC 46:36:d8:d6:64:4c
BOOTP broadcast 1
BOOTP broadcast 2
*** Unhandled DHCP Option in OFFER/ACK: 2
*** Unhandled DHCP Option in OFFER/ACK: 28
*** Unhandled DHCP Option in OFFER/ACK: 2
*** Unhandled DHCP Option in OFFER/ACK: 28
DHCP client bound to address 192.168.23.75
Using smc911x-0 device
TFTP from server 192.168.23.10; our IP address is 192.168.23.75
Filename 'snowball/image'.
Load address: 0x100000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
########################
done
Bytes transferred = 4169048 (3f9d58 hex)
## Booting kernel from Legacy Image at 00100000 ...
Image Name: Linux-3.6.0-rc3-test+
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4168984 Bytes = 4 MB
Load Address: 00008000
Entry Point: 00008000
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Linux version 3.6.0-rc3-test+ (rostedt at goliath) (gcc version 4.5.2 (GCC) ) #272 SMP PREEMPT Thu Jan 24 09:37:12 EST 2013
[ 0.000000] CPU: ARMv7 Processor [412fc091] revision 1 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Calao Systems Snowball platform
[ 0.000000] Ignoring unrecognised tag 0x41000403
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] DB8500 v2.1 [0x008500b1]
[ 0.000000] PERCPU: Embedded 9 pages/cpu @c1111000 s13184 r8192 d15488 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 206848
[ 0.000000] Kernel command line: console=ttyAMA2,115200n8 vmalloc=256M root=/dev/mmcblk0p3 rootwait mem=128M at 0 mali.mali_mem=32M at 128M hwmem=168M at 160M mem=48M at 328M mem_issw=1M at 383M mem=640M at 384M
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 128MB 48MB 640MB = 816MB total
[ 0.000000] Memory: 818892k/818892k available, 16692k reserved, 278528K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xef800000 - 0xff000000 ( 248 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef000000 ( 752 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc07c6344 (7929 kB)
[ 0.000000] .init : 0xc07c7000 - 0xc0813380 ( 305 kB)
[ 0.000000] .data : 0xc0814000 - 0xc087b850 ( 415 kB)
[ 0.000000] .bss : 0xc087b874 - 0xc0909028 ( 566 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:670
[ 0.000000] PRCMU firmware: U8500, version 3.4.9
[ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000457] Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816)
[ 0.090026] pid_max: default: 32768 minimum: 301
[ 0.090240] Security Framework initialized
[ 0.090332] AppArmor: AppArmor initialized
[ 0.090454] Mount-cache hash table entries: 512
[ 0.091888] Initializing cgroup subsys cpuacct
[ 0.091979] CPU: Testing write buffer coherency: ok
[ 0.092041] ftrace: allocating 20089 entries in 59 pages
[ 0.135833] CPU0: thread -1, cpu 0, socket 3, mpidr 80000300
[ 0.135894] smp_twd: clock not found: -2
[ 0.135894] Calibrating local timer... 399.10MHz.
[ 0.190032] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 0.190185] Setting up static identity map for 0x577a68 - 0x577ac0
[ 0.190216] L310 cache controller enabled
[ 0.190216] l2x0: 8 ways, CACHE_ID 0x410000c5, AUX_CTRL 0x7e060800, Cache size: 524288 B
[ 0.250549] CPU1: Booted secondary processor
[ 0.339965] CPU1: thread -1, cpu 1, socket 3, mpidr 80000301
[ 0.340087] Brought up 2 CPUs
[ 0.340087] SMP: Total of 2 processors activated (3188.32 BogoMIPS).
[ 0.340942] devtmpfs: initialized
[ 0.346435] pinctrl core: initialized pinctrl subsystem
[ 0.347686] dummy:
[ 0.348632] NET: Registered protocol family 16
[ 0.349487] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.352569] gpio gpio.0: at address f812e000
[ 0.353149] gpio gpio.1: at address f812e080
[ 0.353729] gpio gpio.2: at address f800e000
[ 0.354309] gpio gpio.3: at address f800e080
[ 0.354858] gpio gpio.4: at address f800e100
[ 0.355438] gpio gpio.5: at address f800e180
[ 0.356018] gpio gpio.6: at address f811e000
[ 0.356597] gpio gpio.7: at address f811e080
[ 0.357177] gpio gpio.8: at address fa3fe000
[ 0.358398] pinctrl-nomadik pinctrl-db8500: initialized Nomadik pin control driver
[ 0.360229] ab8500-core ab8500-core.0: detected chip, AB8500 rev. 3.0
[ 0.360290] ab8500-core ab8500-core.0: switch off cause(s) (0x20):
[ 0.360290] "Battery level lower than power on reset threshold"
[ 0.365112] DB8500 PRCMU initialized
[ 0.366302] mop500_msp_init: Register platform-device 'snd-soc-u8500'.
[ 0.366485] Initialize MSP I2S-devices.
[ 0.366516] Register platform-device 'ux500-msp-i2s', id 0, irq 63
[ 0.366729] Register platform-device 'ux500-msp-i2s', id 1, irq 94
[ 0.366912] Register platform-device 'ux500-msp-i2s', id 2, irq 130
[ 0.367095] Register platform-device 'ux500-msp-i2s', id 3, irq 94
[ 0.367401] mop500_msp_init: Register platform-device 'ux500-pcm'
[ 0.368286] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.368316] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.368865] db8500-vape:
[ 0.369171] db8500-varm:
[ 0.369476] db8500-vmodem:
[ 0.369750] db8500-vpll:
[ 0.370208] db8500-vsmps1:
[ 0.370483] db8500-vsmps2:
[ 0.370758] db8500-vsmps3:
[ 0.371032] db8500-vrf1:
[ 0.371307] db8500-sva-mmdsp:
[ 0.371582] db8500-sva-mmdsp-ret:
[ 0.371856] db8500-sva-pipe:
[ 0.372131] db8500-sia-mmdsp:
[ 0.372406] db8500-sia-mmdsp-ret:
[ 0.372680] db8500-sia-pipe:
[ 0.372955] db8500-sga:
[ 0.372985] db8500-sga: supplied by db8500-vape
[ 0.373291] db8500-b2r2-mcde:
[ 0.373321] db8500-b2r2-mcde: supplied by db8500-vape
[ 0.373626] db8500-esram12:
[ 0.373931] db8500-esram12-ret:
[ 0.374206] db8500-esram34:
[ 0.374511] db8500-esram34-ret:
[ 0.374786] Serial: AMBA PL011 UART driver
[ 0.374969] uart0: ttyAMA0 at MMIO 0x80120000 (irq = 43) is a PL011 rev3
[ 0.375396] uart-pl011 uart1: could not get default pinstate
[ 0.375427] uart1: ttyAMA1 at MMIO 0x80121000 (irq = 51) is a PL011 rev3
[ 0.375793] uart-pl011 uart2: could not get default pinstate
[ 0.375823] uart2: ttyAMA2 at MMIO 0x80007000 (irq = 58) is a PL011 rev3
[ 0.922393] console [ttyAMA2] enabled
[ 0.946716] bio: create slab <bio-0> at 0
And this is where the board would lock up.
-- Steve
^ permalink raw reply
* Sound/ARM/i.MX/SSI: fix SDMA starvation
From: Juergen Beisert @ 2013-01-30 13:44 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <201301240956.30641.jbe@pengutronix.de>
Juergen Beisert wrote:
> In cases when capturing is already running and someone enables also
> playback, the SDMA unit of the i.MX SoC does not see an edge on its TX DMA
> request line. This is due to the TX FIFOs are empty, and this request line
> is active all the time, when the CCSR_SSI_SIER_TDMAE bit is set.
> In this case also the TX FIFO underrun interrupt will flood the system
> forever.
>
> To ensure the first edge happens after enabling the TX side of the SSI unit
> and to trigger the SDMA unit successfully enable the CCSR_SSI_SIER_TDMAE on
> demand only. To be sure, this patch does the same for the
> CCSR_SSI_SIER_RDMAE (RX side) bit.
>
> Signed-off-by: Juergen Beisert <jbe@pengutronix.de>
>
> ---
> sound/soc/fsl/fsl_ssi.c | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
>
> Index: linux.git/sound/soc/fsl/fsl_ssi.c
> ===================================================================
> --- linux.git.orig/sound/soc/fsl/fsl_ssi.c
> +++ linux.git/sound/soc/fsl/fsl_ssi.c
> @@ -86,10 +86,9 @@ static inline void write_ssi_mask(u32 __
> #endif
>
> /* SIER bitflag of interrupts to enable */
> -#define SIER_FLAGS (CCSR_SSI_SIER_TFRC_EN | CCSR_SSI_SIER_TDMAE | \
> - CCSR_SSI_SIER_TIE | CCSR_SSI_SIER_TUE0_EN | \
> - CCSR_SSI_SIER_TUE1_EN | CCSR_SSI_SIER_RFRC_EN | \
> - CCSR_SSI_SIER_RDMAE | CCSR_SSI_SIER_RIE | \
> +#define SIER_FLAGS (CCSR_SSI_SIER_TFRC_EN | CCSR_SSI_SIER_TIE | \
> + CCSR_SSI_SIER_TUE0_EN | CCSR_SSI_SIER_TUE1_EN | \
> + CCSR_SSI_SIER_RFRC_EN | CCSR_SSI_SIER_RIE | \
> CCSR_SSI_SIER_ROE0_EN | CCSR_SSI_SIER_ROE1_EN)
>
> /**
> @@ -489,6 +488,9 @@ static int fsl_ssi_hw_params(struct snd_
> *
> * The DMA channel is in external master start and pause mode, which
> * means the SSI completely controls the flow of data.
> + *
> + * To use the i.MX's SDMA unit it is important to create an edge on the
> + * corresponding request line. Otherwise the request will be ignored!
> */
> static int fsl_ssi_trigger(struct snd_pcm_substream *substream, int cmd,
> struct snd_soc_dai *dai)
> @@ -500,20 +502,26 @@ static int fsl_ssi_trigger(struct snd_pc
> switch (cmd) {
> case SNDRV_PCM_TRIGGER_START:
> case SNDRV_PCM_TRIGGER_PAUSE_RELEASE:
> - if (substream->stream == SNDRV_PCM_STREAM_PLAYBACK)
> + if (substream->stream == SNDRV_PCM_STREAM_PLAYBACK) {
> write_ssi_mask(&ssi->scr, 0,
> CCSR_SSI_SCR_SSIEN | CCSR_SSI_SCR_TE);
> - else
> + write_ssi_mask(&ssi->sier, 0, CCSR_SSI_SIER_TDMAE);
> + } else {
> write_ssi_mask(&ssi->scr, 0,
> CCSR_SSI_SCR_SSIEN | CCSR_SSI_SCR_RE);
> + write_ssi_mask(&ssi->sier, 0, CCSR_SSI_SIER_RDMAE);
> + }
> break;
>
> case SNDRV_PCM_TRIGGER_STOP:
> case SNDRV_PCM_TRIGGER_PAUSE_PUSH:
> - if (substream->stream == SNDRV_PCM_STREAM_PLAYBACK)
> + if (substream->stream == SNDRV_PCM_STREAM_PLAYBACK) {
> write_ssi_mask(&ssi->scr, CCSR_SSI_SCR_TE, 0);
> - else
> + write_ssi_mask(&ssi->sier, CCSR_SSI_SIER_TDMAE, 0);
> + } else {
> write_ssi_mask(&ssi->scr, CCSR_SSI_SCR_RE, 0);
> + write_ssi_mask(&ssi->sier, CCSR_SSI_SIER_RDMAE, 0);
> + }
> break;
>
> default:
Any comments on this patch?
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | Phone: +49-5121-206917-5128 |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
^ permalink raw reply
* [PATCH v2] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
From: Rafael J. Wysocki @ 2013-01-30 13:40 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EAF880F@DBDE01.ent.ti.com>
On Wednesday, January 30, 2013 07:10:20 AM AnilKumar, Chimata wrote:
> On Tue, Jan 29, 2013 at 08:23:40, Shawn Guo wrote:
> > As multiplatform build is being adopted by more and more ARM platforms,
> > initcall function should be used very carefully. For example, when
> > GENERIC_CPUFREQ_CPU0 is built in the kernel, cpu0_cpufreq_driver_init()
> > will be called on all the platforms to initialize cpufreq-cpu0 driver.
> >
> > To eliminate this undesired the effect, the patch changes cpufreq-cpu0
> > driver to have it instantiated as a platform_driver. Then it will only
> > run on platforms that create the platform_device "cpufreq-cpu0".
> >
> > Along with the change, it also changes cpu_dev to be &pdev->dev,
> > so that managed functions can start working, and module build gets
> > supported too.
> >
> > The existing users of cpufreq-cpu0 driver highbank and am33xx are also
> > updated accordingly to adapt the changes.
> >
> > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > Cc: Mark Langsdorf <mark.langsdorf@calxeda.com>
> > Cc: AnilKumar Ch <anilkumar@ti.com>
> > Cc: Tony Lindgren <tony@atomide.com>
> > Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > ---
> > Changes since v1:
> > * Migrate cpufreq-cpu0 users in the same patch
> >
> > Rafael,
> >
> > The patch is based on Mark's highbank-cpufreq series and Nishanth's
> > "PM / OPP : export symbol consolidation" sereis.
> >
> > Mark, AnilKumar,
> >
> > I only compile-tested it on highbank and omap2. Please give it a test
> > no hardware to make sure cpufreq-cpu0 still works for you. Thanks.
>
> Hi Shawn,
>
> I hope this is based on linux-omap/master, to test the driver I have
> to add some patches on top of this patch, because of recent changes.
> I will provide the test details once I am done.
Shawn, does it mean I need to wait with applying the patch or will OMAP2
work as is?
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
^ permalink raw reply
* linux-next: manual merge of the arm-soc tree with the pinctrl tree
From: Stephen Rothwell @ 2013-01-30 13:36 UTC (permalink / raw)
To: linux-arm-kernel
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
drivers/pinctrl/pinctrl-nomadik.c between commit e32af8894588
("pinctrl/nomadik: add device tree support") from the pinctrl tree and
commit 6010d40320f8 ("ARM: nomadik: move GPIO and pinctrl to device
tree") from the arm-soc tree.
I fixed it up (see below) and can carry the fix as necessary (no action
is required).
--
Cheers,
Stephen Rothwell sfr at canb.auug.org.au
diff --cc drivers/pinctrl/pinctrl-nomadik.c
index 39c1651,ef21a66..0000000
--- a/drivers/pinctrl/pinctrl-nomadik.c
+++ b/drivers/pinctrl/pinctrl-nomadik.c
@@@ -2104,7 -1846,11 +2104,11 @@@ static struct pinctrl_desc nmk_pinctrl_
static const struct of_device_id nmk_pinctrl_match[] = {
{
+ .compatible = "stericsson,nmk-pinctrl-stn8815",
+ .data = (void *)PINCTRL_NMK_STN8815,
+ },
+ {
- .compatible = "stericsson,nmk_pinctrl",
+ .compatible = "stericsson,nmk-pinctrl",
.data = (void *)PINCTRL_NMK_DB8500,
},
{},
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130131/b17bd058/attachment.sig>
^ permalink raw reply
* [PATCH 1/3] atmel_lcdfb: fix 16-bpp modes on older SOCs
From: Johan Hovold @ 2013-01-30 13:26 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130129135435.GN7360@game.jcrosoft.org>
On Tue, Jan 29, 2013 at 02:54:35PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 13:28 Mon 10 Dec , Johan Hovold wrote:
> > Fix regression introduced by commit 787f9fd23283 ("atmel_lcdfb: support
> > 16bit BGR:565 mode, remove unsupported 15bit modes") which broke 16-bpp
> > modes for older SOCs which use IBGR:555 (msb is intensity) rather
> > than BGR:565.
> >
> > Use SOC-type to determine the pixel layout.
> >
> > Tested on custom at91sam9263-board.
> >
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Johan Hovold <jhovold@gmail.com>
> > ---
> > drivers/video/atmel_lcdfb.c | 22 +++++++++++++++-------
> > include/video/atmel_lcdc.h | 1 +
> > 2 files changed, 16 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/video/atmel_lcdfb.c b/drivers/video/atmel_lcdfb.c
> > index 1505539..1f68fa6 100644
> > --- a/drivers/video/atmel_lcdfb.c
> > +++ b/drivers/video/atmel_lcdfb.c
> > @@ -422,17 +422,22 @@ static int atmel_lcdfb_check_var(struct fb_var_screeninfo *var,
> > = var->bits_per_pixel;
> > break;
> > case 16:
> > + /* Older SOCs use IBGR:555 rather than BGR:565. */
> > + if (sinfo->have_intensity_bit)
> > + var->green.length = 5;
> > + else
> > + var->green.length = 6;
> > +
> > if (sinfo->lcd_wiring_mode == ATMEL_LCDC_WIRING_RGB) {
> > - /* RGB:565 mode */
> > - var->red.offset = 11;
> > + /* RGB:5X5 mode */
> > + var->red.offset = var->green.length + 5;
> > var->blue.offset = 0;
> > } else {
> > - /* BGR:565 mode */
> > + /* BGR:5X5 mode */
> > var->red.offset = 0;
> > - var->blue.offset = 11;
> > + var->blue.offset = var->green.length + 5;
> > }
> > var->green.offset = 5;
> > - var->green.length = 6;
> > var->red.length = var->blue.length = 5;
> > break;
> > case 32:
> > @@ -679,8 +684,7 @@ static int atmel_lcdfb_setcolreg(unsigned int regno, unsigned int red,
> >
> > case FB_VISUAL_PSEUDOCOLOR:
> > if (regno < 256) {
> > - if (cpu_is_at91sam9261() || cpu_is_at91sam9263()
> > - || cpu_is_at91sam9rl()) {
> > + if (sinfo->have_intensity_bit) {
> > /* old style I+BGR:555 */
> > val = ((red >> 11) & 0x001f);
> > val |= ((green >> 6) & 0x03e0);
> > @@ -870,6 +874,10 @@ static int __init atmel_lcdfb_probe(struct platform_device *pdev)
> > }
> > sinfo->info = info;
> > sinfo->pdev = pdev;
> > + if (cpu_is_at91sam9261() || cpu_is_at91sam9263() ||
> > + cpu_is_at91sam9rl()) {
> > + sinfo->have_intensity_bit = true;
> > + }
> nack
>
> you need to drop the cpu_is as this can only be use now for the core
>
> use platform_device_id to indetify the IP as done on at91-i2c as we can not
> detect the IP version
If this was a new feature and not a regression, fix I'd fully agree. There
are however currently four places in atmel_lcdfb where cpu_is macros are
used, and my patch only refactors one of them.
I can submit a follow up patch which add platform_device_id support, but
such a patch will be quite invasive and thus not 3.8-rc or stable material.
How about accepting this patch as it is, considering that it fixes an
obvious regression and also facilitate the move to platform_device_id by
introducing the intensity-bit flag?
Thanks,
Johan
^ permalink raw reply
* [PATCH 1/2] ASoC: tlv320aic3x: Convert mic bias to a supply widget
From: Hebbar Gururaja @ 2013-01-30 13:22 UTC (permalink / raw)
To: linux-arm-kernel
Convert MicBias widgets to supply widget.
On tlv320aic3x, Mic bias power on/off shares the same register bits
with output mic bias voltage. So, when power on mic bias, we need
reclaim it to voltage value.
Provide a new platform data so that the micbias voltage can be sent
according to board requirement. Now since tlc320aic3x codec driver
is DT aware, update dt files and functions to handle this new
"micbias-vg" platform data.
Because of sharing of bits, when enabling the micbias, voltage also
needs to be updated. So use SND_SOC_DAPM_POST_PMU & SND_SOC_DAPM_PRE_PMD
macro to create an event to handle this.
Signed-off-by: Hebbar Gururaja <gururaja.hebbar@ti.com>
---
Mark,
I have updated the codec driver as you suggested. Can you confirm if
this is sufficient?.
If yes, then I will send all the patch once again with new revision.
:100644 100644 e7b98f4... f47c3f5... M Documentation/devicetree/bindings/sound/tlv320aic3x.txt
:100644 100644 ffd9bc7... 9407fd0... M include/sound/tlv320aic3x.h
:100644 100644 4989143... fe6dd27... M sound/soc/codecs/tlv320aic3x.c
:100644 100644 6db3c41... e521ac3... M sound/soc/codecs/tlv320aic3x.h
.../devicetree/bindings/sound/tlv320aic3x.txt | 6 ++
include/sound/tlv320aic3x.h | 10 +++
sound/soc/codecs/tlv320aic3x.c | 85 ++++++++++++++++++--
sound/soc/codecs/tlv320aic3x.h | 4 +
4 files changed, 99 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/sound/tlv320aic3x.txt b/Documentation/devicetree/bindings/sound/tlv320aic3x.txt
index e7b98f4..f47c3f5 100644
--- a/Documentation/devicetree/bindings/sound/tlv320aic3x.txt
+++ b/Documentation/devicetree/bindings/sound/tlv320aic3x.txt
@@ -11,6 +11,12 @@ Optional properties:
- gpio-reset - gpio pin number used for codec reset
- ai3x-gpio-func - <array of 2 int> - AIC3X_GPIO1 & AIC3X_GPIO2 Functionality
+- ai3x-micbias-vg - MicBias Voltage required.
+ 1 - MICBIAS output is powered to 2.0V,
+ 2 - MICBIAS output is powered to 2.5V,
+ 3 - MICBIAS output is connected to AVDD,
+ If this node is not mentioned or if the value is incorrect, then MicBias
+ is powered down.
Example:
diff --git a/include/sound/tlv320aic3x.h b/include/sound/tlv320aic3x.h
index ffd9bc7..9407fd0 100644
--- a/include/sound/tlv320aic3x.h
+++ b/include/sound/tlv320aic3x.h
@@ -46,6 +46,13 @@ enum {
AIC3X_GPIO2_FUNC_BUTTON_PRESS_IRQ = 15
};
+enum aic3x_micbias_voltage {
+ AIC3X_MICBIAS_OFF = 0,
+ AIC3X_MICBIAS_2_0V = 1,
+ AIC3X_MICBIAS_2_5V = 2,
+ AIC3X_MICBIAS_AVDDV = 3,
+};
+
struct aic3x_setup_data {
unsigned int gpio_func[2];
};
@@ -53,6 +60,9 @@ struct aic3x_setup_data {
struct aic3x_pdata {
int gpio_reset; /* < 0 if not used */
struct aic3x_setup_data *setup;
+
+ /* Selects the micbias voltage */
+ enum aic3x_micbias_voltage micbias_vg;
};
#endif
diff --git a/sound/soc/codecs/tlv320aic3x.c b/sound/soc/codecs/tlv320aic3x.c
index 4989143..fe6dd27 100644
--- a/sound/soc/codecs/tlv320aic3x.c
+++ b/sound/soc/codecs/tlv320aic3x.c
@@ -85,6 +85,9 @@ struct aic3x_priv {
#define AIC3X_MODEL_33 1
#define AIC3X_MODEL_3007 2
u16 model;
+
+ /* Selects the micbias voltage */
+ enum aic3x_micbias_voltage micbias_vg;
};
/*
@@ -195,6 +198,37 @@ static int snd_soc_dapm_put_volsw_aic3x(struct snd_kcontrol *kcontrol,
return ret;
}
+/*
+ * mic bias power on/off share the same register bits with
+ * output voltage of mic bias. when power on mic bias, we
+ * need reclaim it to voltage value.
+ * 0x0 = Powered off
+ * 0x1 = MICBIAS output is powered to 2.0V,
+ * 0x2 = MICBIAS output is powered to 2.5V
+ * 0x3 = MICBIAS output is connected to AVDD
+ */
+static int mic_bias_event(struct snd_soc_dapm_widget *w,
+ struct snd_kcontrol *kcontrol, int event)
+{
+ struct snd_soc_codec *codec = w->codec;
+ struct aic3x_priv *aic3x = snd_soc_codec_get_drvdata(codec);
+
+ switch (event) {
+ case SND_SOC_DAPM_POST_PMU:
+ /* change mic bias voltage to user defined */
+ snd_soc_update_bits(codec, MICBIAS_CTRL,
+ MICBIAS_LEVEL_MASK,
+ aic3x->micbias_vg << MICBIAS_LEVEL_SHIFT);
+ break;
+
+ case SND_SOC_DAPM_PRE_PMD:
+ snd_soc_update_bits(codec, MICBIAS_CTRL,
+ MICBIAS_LEVEL_MASK, 0);
+ break;
+ }
+ return 0;
+}
+
static const char *aic3x_left_dac_mux[] = { "DAC_L1", "DAC_L3", "DAC_L2" };
static const char *aic3x_right_dac_mux[] = { "DAC_R1", "DAC_R3", "DAC_R2" };
static const char *aic3x_left_hpcom_mux[] =
@@ -596,12 +630,9 @@ static const struct snd_soc_dapm_widget aic3x_dapm_widgets[] = {
AIC3X_ASD_INTF_CTRLA, 0, 3, 3, 0),
/* Mic Bias */
- SND_SOC_DAPM_REG(snd_soc_dapm_micbias, "Mic Bias 2V",
- MICBIAS_CTRL, 6, 3, 1, 0),
- SND_SOC_DAPM_REG(snd_soc_dapm_micbias, "Mic Bias 2.5V",
- MICBIAS_CTRL, 6, 3, 2, 0),
- SND_SOC_DAPM_REG(snd_soc_dapm_micbias, "Mic Bias AVDD",
- MICBIAS_CTRL, 6, 3, 3, 0),
+ SND_SOC_DAPM_SUPPLY("Mic Bias", MICBIAS_CTRL, 6, 0,
+ mic_bias_event,
+ SND_SOC_DAPM_POST_PMU | SND_SOC_DAPM_PRE_PMD),
/* Output mixers */
SND_SOC_DAPM_MIXER("Left Line Mixer", SND_SOC_NOPM, 0, 0,
@@ -1386,6 +1417,24 @@ static int aic3x_probe(struct snd_soc_codec *codec)
if (aic3x->model == AIC3X_MODEL_3007)
snd_soc_add_codec_controls(codec, &aic3x_classd_amp_gain_ctrl, 1);
+ /* set mic bias voltage */
+ switch (aic3x->micbias_vg) {
+ case AIC3X_MICBIAS_2_0V:
+ case AIC3X_MICBIAS_2_5V:
+ case AIC3X_MICBIAS_AVDDV:
+ snd_soc_update_bits(codec, MICBIAS_CTRL,
+ MICBIAS_LEVEL_MASK,
+ (aic3x->micbias_vg) << MICBIAS_LEVEL_SHIFT);
+ break;
+ case AIC3X_MICBIAS_OFF:
+ /*
+ * noting to do. target won't enter here. This is just to avoid
+ * compile time warning "warning: enumeration value
+ * 'AIC3X_MICBIAS_OFF' not handled in switch"
+ */
+ break;
+ }
+
aic3x_add_widgets(codec);
list_add(&aic3x->list, &reset_list);
@@ -1461,6 +1510,7 @@ static int aic3x_i2c_probe(struct i2c_client *i2c,
struct aic3x_setup_data *ai3x_setup;
struct device_node *np = i2c->dev.of_node;
int ret;
+ u32 value;
aic3x = devm_kzalloc(&i2c->dev, sizeof(struct aic3x_priv), GFP_KERNEL);
if (aic3x == NULL) {
@@ -1474,6 +1524,7 @@ static int aic3x_i2c_probe(struct i2c_client *i2c,
if (pdata) {
aic3x->gpio_reset = pdata->gpio_reset;
aic3x->setup = pdata->setup;
+ aic3x->micbias_vg = pdata->micbias_vg;
} else if (np) {
ai3x_setup = devm_kzalloc(&i2c->dev, sizeof(*ai3x_setup),
GFP_KERNEL);
@@ -1493,6 +1544,28 @@ static int aic3x_i2c_probe(struct i2c_client *i2c,
aic3x->setup = ai3x_setup;
}
+ if (!of_property_read_u32(np, "ai3x-micbias-vg", &value)) {
+ switch (value) {
+ case 1 :
+ aic3x->micbias_vg = AIC3X_MICBIAS_2_0V;
+ break;
+ case 2 :
+ aic3x->micbias_vg = AIC3X_MICBIAS_2_5V;
+ break;
+ case 3 :
+ aic3x->micbias_vg = AIC3X_MICBIAS_AVDDV;
+ break;
+ default :
+ aic3x->micbias_vg = AIC3X_MICBIAS_OFF;
+ dev_err(&i2c->dev, "Unsuitable MicBias voltage "
+ "found in DT\n");
+ }
+ } else {
+ dev_warn(&i2c->dev, "No MicBias voltage found in DT - "
+ "using default\n");
+ aic3x->micbias_vg = AIC3X_MICBIAS_OFF;
+ }
+
} else {
aic3x->gpio_reset = -1;
}
diff --git a/sound/soc/codecs/tlv320aic3x.h b/sound/soc/codecs/tlv320aic3x.h
index 6db3c41..e521ac3 100644
--- a/sound/soc/codecs/tlv320aic3x.h
+++ b/sound/soc/codecs/tlv320aic3x.h
@@ -238,6 +238,10 @@
/* Default input volume */
#define DEFAULT_GAIN 0x20
+/* MICBIAS Control Register */
+#define MICBIAS_LEVEL_SHIFT (6)
+#define MICBIAS_LEVEL_MASK (3 << 6)
+
/* headset detection / button API */
/* The AIC3x supports detection of stereo headsets (GND + left + right signal)
--
1.7.9.5
^ permalink raw reply related
* [RFC PATCH 0/2] ARM: update cpuinfo to print CPU model name
From: Ruslan Bilovol @ 2013-01-30 13:20 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130129233842.GA8024@kahuna>
On Wed, Jan 30, 2013 at 1:38 AM, Nishanth Menon <nm@ti.com> wrote:
> On 01:08-20130130, Ruslan Bilovol wrote:
>> Hi,
>>
>> On Tue, Jan 29, 2013 at 6:02 PM, Nishanth Menon <nm@ti.com> wrote:
>> >
>> > On 17:54-20130129, Ruslan Bilovol wrote:
>> > > Hi,
>> > >
>> > > The following patches update cpuinfo to print CPU
>> > > model name for ARM. First patch exactly makes needed
>> > > changes for ARM architecture.
>> > > Second patch adds this ability to OMAP4 SoCs.
>> > >
>> > > This adds a common approach to show SoC name.
>> > >
>> > > Looks like there were few attempts to do similar
>> > > changes to cpuinfo without any luck.
>> > >
>> > > So - comments are welcome
>> > >
>> > > Ruslan Bilovol (2):
>> > > ARM: kernel: update cpuinfo to print CPU model name
>> > > ARM: OMAP4: setup CPU model name during ID initialisation
>> >
>> > We had an discussion on similar lines but a generic suggestion:
>> > https://patchwork.kernel.org/patch/98720/
>> > SoCinfo framework which was supposed to introduce this
>> >
>> > Would'nt that be a better approach to take than an OMAP only solution?
>>
>> My goal is only to say what is the SoC model name in the /proc/cpuinfo
>> (And it is not an OMAP-only solution - it is common. Support for OMAP
>> is added in second patch)
>> This is the only type of information that we can apply for any SoC.
>> My point is - any SoC-specific information should go through some other
>> way - like SoCinfo framework mentioned by you.
>> And additional point - in cpuinfo we already have CPU name and Machine name.
>> The SoC name (that is something between these two things) looks also relevant
> Looking at the sample output in patch #1/2
> OMAP4470 ES1.0 HS
>
> OMAP4470 is SoC name
> ES1.0 is SoC revision
> HS is SoC type
Will fix it in next patchseries. Let's leave only only SoC name
>
> We even have SoC features (e.g. at boot NEON etc..)
>
> Is the intent to put all this inside /proc/cpuinfo?? I bet every SoC has
> it's own interesting data it'd like to have (like some of the info
> populated by DT even). I am hardpressed to think this fits inside
> /proc/cpuinfo. I might even suspect that the list of interesting
> information might even vary per SoC.
No, I don't think we need all these information in cpuinfo - just because
it will be different for different SoC - so the file structure will be
very different..
Let's have only SoC name in cpuinfo.
>
> having machine name is something ARM specific? dumping it on my linux
> machines (x86[1] and sparc[2]) dont seem to show that.
Yes - it's ARM specific.
>
> but in the interest of not breaking existing interfaces, new interfaces
> should potentially belong elsewhere.. my 2 cents.
>
> [1] http://pastebin.com/CF8HPDAC (Xubuntu 12.04 3.2.0-36)
> [2] http://pastebin.com/qNwWHwiu (Debian 3.2.35-2)
Just look at changes in cpuinfo for ARM between kernels:
3.4 kernel: http://pastebin.com/TfmE7b2b
3.8-rc3: http://pastebin.com/zvvTGeNt
The file structure has huge changes
> --
> Regards,
> Nishanth Menon
^ permalink raw reply
* [GIT PULL] imx6q cpuidle for 3.9
From: Shawn Guo @ 2013-01-30 13:19 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130129175028.GC17935@quad.lixom.net>
On Tue, Jan 29, 2013 at 09:50:28AM -0800, Olof Johansson wrote:
> This has some small conflicts with the cleanup branch. Can you please base it
> on top of cleanup so we can avoid the merge conflicts when things go upstream?
> It's common to have the per-soc cleanup branches as bases for some of the
> feature branches just for this reason.
>
Ok, done as below.
The following changes since commit 1d7180e24e22a608cc4d7e8fd425a19a9394a7ed:
Merge tag 'imx-cleanup-3.9' into imx6q-cpuidle (2013-01-30 21:07:14 +0800)
are available in the git repository at:
git://git.linaro.org/people/shawnguo/linux-2.6.git tags/imx6q-cpudile-3.9
for you to fetch changes up to e5f9dec8ff5ff3f6254412abed1f68d758f6616b:
ARM: imx6q: support WAIT mode using cpuidle (2013-01-30 21:09:31 +0800)
----------------------------------------------------------------
imx6q cpuidle support for 3.9
- It's based on imx-cleanup-3.9 to avoid conflicts.
----------------------------------------------------------------
Shawn Guo (4):
ARM: imx: return zero in case next event gets a large increment
ARM: imx: mask gpc interrupts initially
ARM: imx: move imx6q_cpuidle_driver into a separate file
ARM: imx6q: support WAIT mode using cpuidle
arch/arm/mach-imx/Makefile | 6 ++-
arch/arm/mach-imx/clk-imx6q.c | 12 +++++
arch/arm/mach-imx/common.h | 3 ++
arch/arm/mach-imx/cpuidle-imx6q.c | 95 +++++++++++++++++++++++++++++++++++++
arch/arm/mach-imx/cpuidle.h | 5 ++
arch/arm/mach-imx/gpc.c | 5 ++
arch/arm/mach-imx/mach-imx6q.c | 17 +++----
arch/arm/mach-imx/platsmp.c | 10 ++++
arch/arm/mach-imx/time.c | 3 +-
9 files changed, 143 insertions(+), 13 deletions(-)
create mode 100644 arch/arm/mach-imx/cpuidle-imx6q.c
^ permalink raw reply
* [PATCH v2 00/30] USB: omap-ehci: Move PHY management to PHY driver
From: Mohammed, Afzal @ 2013-01-30 13:19 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130130131504.GU15258@arwen.pp.htv.fi>
Hi Felipe,
On Wed, Jan 30, 2013 at 18:45:04, Balbi, Felipe wrote:
> On Wed, Jan 30, 2013 at 02:48:50PM +0200, Roger Quadros wrote:
> > I would appreciate if someone who knows more about beaglebone can help
> > with verification.
> >
> > I could find that Robert C Nelson (now in cc) is maintaining out of tree
> > patches for the beaglebone. Maybe he could help with verification?
>
> Right, Afzal if you have the bone could you help Roger validating ?
I am not in a position to validate it, in the middle of another task.
Regards
Afzal
^ permalink raw reply
* [PATCH v2] ARM i.MX25: clk: parent per5_clk to AHB clock
From: Steffen Trumtrar @ 2013-01-30 13:16 UTC (permalink / raw)
To: linux-arm-kernel
The mxc-timer on the imx25 needs to be derived from the AHB clock.
If a bootloader reparents this clock to the ipg_clk_highfreq, which according
to the datasheet is a valid operation, the system can/will produce lockups/
freezes after some time [1].
This can be forced with code like
while(1)
syscall(SYS_clock_gettime, CLOCK_REALTIME, &tp);
This was already fixed with the commit
"i.MX25 GPT clock fix: ensure correct the clock source" [2],
for 3.1-rc2, but was lost, when i.MX was converted to the common clock framework
("ARM i.MX25: implement clocks using common clock framework") [3]
[1]: http://lists.arm.linux.org.uk/lurker/message/20130129.161230.229bda17.en.html
[2]: 2012d9ca2a1381ae3e733330a7f0d1d2f1988bba
[3]: 6bbaec5676e4f475b0d78743cbd4c70a8804ce14
Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: stable at vger.kernel.org # v3.5+
---
arch/arm/mach-imx/clk-imx25.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-imx/clk-imx25.c b/arch/arm/mach-imx/clk-imx25.c
index 5d34f67..0e6dde6 100644
--- a/arch/arm/mach-imx/clk-imx25.c
+++ b/arch/arm/mach-imx/clk-imx25.c
@@ -177,6 +177,9 @@ static int __init __mx25_clocks_init(unsigned long osc_rate)
pr_err("i.MX25 clk %d: register failed with %ld\n",
i, PTR_ERR(clk[i]));
+ /* Clock source for gpt must be derived from AHB */
+ clk_set_parent(clk[per5_sel], clk[ahb]);
+
clk_register_clkdev(clk[ipg], "ipg", "imx-gpt.0");
clk_register_clkdev(clk[gpt_ipg_per], "per", "imx-gpt.0");
--
1.7.10.4
^ permalink raw reply related
* [PATCH v2 00/30] USB: omap-ehci: Move PHY management to PHY driver
From: Roger Quadros @ 2013-01-30 13:15 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93EA95E60@DBDE01.ent.ti.com>
On 01/30/2013 03:12 PM, Mohammed, Afzal wrote:
> Hi Roger,
>
> On Wed, Jan 30, 2013 at 18:18:50, Quadros, Roger wrote:
>> On 01/30/2013 02:08 PM, Mohammed, Afzal wrote:
>
>>> Please try to ensure that beagle bone USB0 works with this.
>
>> I do not have beaglebone with me and don't seem to find beaglebone
>> board support in mainline.
>
> Ok. Fyi, beagle bone is supported in mainline - it is dt boot
OMAP USB host is not yet supported for DT boot in mainline. I'm working on this
at the moment.
cheersm
-roger
^ permalink raw reply
* [PATCH v2 00/30] USB: omap-ehci: Move PHY management to PHY driver
From: Felipe Balbi @ 2013-01-30 13:15 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <510916B2.7080509@ti.com>
Hi,
On Wed, Jan 30, 2013 at 02:48:50PM +0200, Roger Quadros wrote:
> On 01/30/2013 02:08 PM, Mohammed, Afzal wrote:
> > Hi Roger,
> >
> > On Mon, Jan 28, 2013 at 17:00:01, Quadros, Roger wrote:
> >
> >> NOTE: Tested on 4460ES-B1 Panda and BeagleBoard C4 only. Other boards are only
> >> build tested.
> >
> > Please try to ensure that beagle bone USB0 works with this.
> >
>
> Hi Afzal,
>
> I do not have beaglebone with me and don't seem to find beaglebone
> board support in mainline.
beagle bone is DT-only :-) (see arch/arm/boot/dts/am335x-bone.dts)
> I would appreciate if someone who knows more about beaglebone can help
> with verification.
>
> I could find that Robert C Nelson (now in cc) is maintaining out of tree
> patches for the beaglebone. Maybe he could help with verification?
Right, Afzal if you have the bone could you help Roger validating ?
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130130/073d5e53/attachment.sig>
^ permalink raw reply
* [BUG] snowball board locks up on boot
From: Steven Rostedt @ 2013-01-30 13:14 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130130090134.GR18212@gmail.com>
On Wed, 2013-01-30 at 09:01 +0000, Lee Jones wrote:
> Can you provide your bootlog please Steven?
>
Here's the bootlog after I reverted the patch and successfully booted:
Card did not respond to voltage select!
smc911x: detected LAN9221 controller
smc911x: phy initialized
smc911x: MAC 46:36:d8:d6:64:4c
BOOTP broadcast 1
BOOTP broadcast 2
*** Unhandled DHCP Option in OFFER/ACK: 2
*** Unhandled DHCP Option in OFFER/ACK: 28
*** Unhandled DHCP Option in OFFER/ACK: 2
*** Unhandled DHCP Option in OFFER/ACK: 28
DHCP client bound to address 192.168.23.75
Using smc911x-0 device
TFTP from server 192.168.23.10; our IP address is 192.168.23.75
Filename 'snowball/image'.
Load address: 0x100000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
##################################
done
Bytes transferred = 4315824 (41dab0 hex)
## Booting kernel from Legacy Image at 00100000 ...
Image Name: Linux-3.8.0-rc4-test+
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4315760 Bytes = 4.1 MB
Load Address: 00008000
Entry Point: 00008000
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x300
[ 0.000000] Linux version 3.8.0-rc4-test+ (rostedt at goliath) (gcc version 4.5.2 (GCC) ) #278 SMP PREEMPT Thu Jan 24 11:54:10 EST 2013
[ 0.000000] CPU: ARMv7 Processor [412fc091] revision 1 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Calao Systems Snowball platform
[ 0.000000] Ignoring unrecognised tag 0x41000403
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] DB8500 v2.1 [0x008500b1]
[ 0.000000] PERCPU: Embedded 9 pages/cpu @c1162000 s13376 r8192 d15296 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 206848
[ 0.000000] Kernel command line: console=ttyAMA2,115200n8 vmalloc=256M root=/dev/mmcblk0p3 rootwait mem=128M at 0 mali.mali_mem=32M at 128M hwmem=168M at 160M mem=48M at 328M mem_issw=1M at 383M mem=640M at 384M
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] Memory: 128MB 48MB 640MB = 816MB total
[ 0.000000] Memory: 818568k/818568k available, 17016k reserved, 278528K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xef800000 - 0xff000000 ( 248 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef000000 ( 752 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0822024 (8297 kB)
[ 0.000000] .init : 0xc0823000 - 0xc0871440 ( 314 kB)
[ 0.000000] .data : 0xc0872000 - 0xc08cc5d0 ( 362 kB)
[ 0.000000] .bss : 0xc08cc5d0 - 0xc095a880 ( 569 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] PRCMU firmware: U8500, version 3.4.9
[ 0.000000] MTU0 clock rate: 133330000 Hz
[ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000488] Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816)
[ 0.090179] pid_max: default: 32768 minimum: 301
[ 0.090393] Security Framework initialized
[ 0.090484] AppArmor: AppArmor initialized
[ 0.090606] Mount-cache hash table entries: 512
[ 0.091705] Initializing cgroup subsys cpuacct
[ 0.091796] CPU: Testing write buffer coherency: ok
[ 0.091888] ftrace: allocating 20559 entries in 61 pages
[ 0.137756] CPU0: thread -1, cpu 0, socket 3, mpidr 80000300
[ 0.137878] Setting up static identity map for 0x5b6450 - 0x5b64a8
[ 0.137939] L310 cache controller enabled
[ 0.137969] l2x0: 8 ways, CACHE_ID 0x000000c0, AUX_CTRL 0x7ec60800, Cache size: 524288 B
[ 0.238708] CPU1: Booted secondary processor
[ 0.313140] CPU1: thread -1, cpu 1, socket 3, mpidr 80000301
[ 0.313201] Brought up 2 CPUs
[ 0.313201] SMP: Total of 2 processors activated (3588.09 BogoMIPS).
[ 0.313934] devtmpfs: initialized
[ 0.318908] pinctrl core: initialized pinctrl subsystem
[ 0.320159] regulator-dummy: no parameters
[ 0.321075] NET: Registered protocol family 16
[ 0.321960] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.325164] gpio gpio.0: at address f812e000
[ 0.326019] gpio gpio.1: at address f812e080
[ 0.326812] gpio gpio.2: at address f800e000
[ 0.327667] gpio gpio.3: at address f800e080
[ 0.328460] gpio gpio.4: at address f800e100
[ 0.329315] gpio gpio.5: at address f800e180
[ 0.330200] gpio gpio.6: at address f811e000
[ 0.331054] gpio gpio.7: at address f811e080
[ 0.331939] gpio gpio.8: at address fa3fe000
[ 0.333099] pinctrl-nomadik pinctrl-db8500: initialized Nomadik pin control driver
[ 0.334991] ab8500-core ab8500-core.0: detected chip, AB8500 rev. 3.0
[ 0.335052] ab8500-core ab8500-core.0: switch off cause(s) (0x20):
[ 0.335052] "Battery level lower than power on reset threshold"
[ 0.341369] DB8500 PRCMU initialized
[ 0.344024] mop500_audio_init: Register platform-device 'snd-soc-mop500'.
[ 0.344238] Initialize MSP I2S-devices.
[ 0.344268] Register platform-device 'ux500-msp-i2s', id 0, irq 63
[ 0.344451] Register platform-device 'ux500-msp-i2s', id 1, irq 94
[ 0.344665] Register platform-device 'ux500-msp-i2s', id 2, irq 130
[ 0.344848] Register platform-device 'ux500-msp-i2s', id 3, irq 94
[ 0.345764] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.345794] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.346343] db8500-vape: no parameters
[ 0.346679] db8500-varm: no parameters
[ 0.346984] db8500-vmodem: no parameters
[ 0.347259] db8500-vpll: no parameters
[ 0.347534] db8500-vsmps1: no parameters
[ 0.347808] db8500-vsmps2: no parameters
[ 0.348114] db8500-vsmps3: no parameters
[ 0.348388] db8500-vrf1: no parameters
[ 0.348724] db8500-sva-mmdsp: no parameters
[ 0.348999] db8500-sva-mmdsp-ret: no parameters
[ 0.349273] db8500-sva-pipe: no parameters
[ 0.349578] db8500-sia-mmdsp: no parameters
[ 0.349853] db8500-sia-mmdsp-ret: no parameters
[ 0.350128] db8500-sia-pipe: no parameters
[ 0.350433] db8500-sga: no parameters
[ 0.350463] db8500-sga: supplied by db8500-vape
[ 0.351135] db8500-b2r2-mcde: no parameters
[ 0.351165] db8500-b2r2-mcde: supplied by db8500-vape
[ 0.351531] db8500-esram12: no parameters
[ 0.351837] db8500-esram12-ret: no parameters
[ 0.352111] db8500-esram34: no parameters
[ 0.352386] db8500-esram34-ret: no parameters
[ 0.352691] Serial: AMBA PL011 UART driver
[ 0.352874] uart0: ttyAMA0 at MMIO 0x80120000 (irq = 43) is a PL011 rev3
[ 0.353424] uart1: ttyAMA1 at MMIO 0x80121000 (irq = 51) is a PL011 rev3
[ 0.353912] uart2: ttyAMA2 at MMIO 0x80007000 (irq = 58) is a PL011 rev3
[ 0.901672] console [ttyAMA2] enabled
[ 0.926879] bio: create slab <bio-0> at 0
[ 0.931762] dma40 dma40.0: hardware revision: 3 @ 0x801c0000
[ 0.937469] dma40 dma40.0: 7 of 8 physical DMA channels available
[ 0.943603] dma40 dma40.0: [d40_phy_res_init] INFO: channel 4 is misconfigured (0)
[ 0.951171] dma40 dma40.0: [d40_phy_res_init] INFO: channel 5 is misconfigured (0)
[ 0.958740] dma40 dma40.0: [d40_phy_res_init] INFO: channel 6 is misconfigured (0)
[ 0.982788] dma40 dma40.0: initialized
[ 0.987060] EN-3V3: Failed to request enable GPIO337: -517
[ 0.992767] reg-fixed-voltage reg-fixed-voltage.1: Failed to register regulator: -517
[ 1.000610] platform reg-fixed-voltage.1: Driver reg-fixed-voltage requests probe deferral
[ 1.010345] V-DISPLAY: 2500 <--> 2900 mV at 2500 mV
[ 1.015777] V-eMMC1: 1100 <--> 3300 mV at 2900 mV
[ 1.020935] V-MMC-SD: 1200 <--> 2910 mV at 2910 mV
[ 1.026184] V-INTCORE: at 1250 mV
[ 1.030029] V-TVOUT: 2000 mV
[ 1.033294] LDO-USB: 3300 mV
[ 1.036529] V-AUD: 2000 mV
[ 1.039672] V-AMIC1: 2050 mV
[ 1.042907] V-AMIC2: 2050 mV
[ 1.046173] V-DMIC: 1800 mV
[ 1.049346] V-CSI/DSI: 1200 mV
[ 1.052551] V-CSI/DSI: Failed to create debugfs directory
[ 1.060028] SCSI subsystem initialized
[ 1.063842] ssp-pl022 ssp0: ARM PL022 driver, device ID: 0x01080022
[ 1.070190] ssp-pl022 ssp0: could not get default pinstate
[ 1.075714] pl022: mapped registers from 0x80002000 to ef860000
[ 1.081726] ssp-pl022 ssp0: setup for DMA on RX dma0chan0, TX dma0chan1
[ 1.089843] usbcore: registered new interface driver usbfs
[ 1.095520] usbcore: registered new interface driver hub
[ 1.101043] usbcore: registered new device driver usb
[ 1.106353] ab8500-usb ab8500-usb.0: AB8500 usb driver initialized
[ 1.113372] nmk-i2c nmk-i2c.0: initialize Nomadik I2C0 at [mem 0x80004000-0x80004fff] on virtual base ef862000
[ 1.123748] nmk-i2c nmk-i2c.1: initialize Nomadik I2C1 at [mem 0x80122000-0x80122fff] on virtual base ef864000
[ 1.134094] nmk-i2c nmk-i2c.2: initialize Nomadik I2C2 at [mem 0x80128000-0x80128fff] on virtual base ef866000
[ 1.144439] nmk-i2c nmk-i2c.3: initialize Nomadik I2C3 at [mem 0x80110000-0x80110fff] on virtual base ef868000
[ 1.155792] Advanced Linux Sound Architecture Driver Initialized.
[ 1.162902] Bluetooth: Core ver 2.16
[ 1.166717] NET: Registered protocol family 31
[ 1.171142] Bluetooth: HCI device and connection manager initialized
[ 1.177520] Bluetooth: HCI socket layer initialized
[ 1.182403] Bluetooth: L2CAP socket layer initialized
[ 1.187469] Bluetooth: SCO socket layer initialized
[ 1.192901] cfg80211: Calling CRDA to update world regulatory domain
[ 1.199432] NetLabel: Initializing
[ 1.202880] NetLabel: domain hash size = 128
[ 1.207244] NetLabel: protocols = UNLABELED CIPSOv4
[ 1.212249] NetLabel: unlabeled traffic allowed by default
[ 1.219024] ab8500-charger ab8500-charger.0: falling back to legacy platform data
[ 1.226623] ab8500-charger ab8500-charger.0: failed to get vddadc regulator
[ 1.233673] platform ab8500-charger.0: Driver ab8500-charger requests probe deferral
[ 1.241668] ab8500-btemp ab8500-btemp.0: falling back to legacy platform data
[ 1.248992] ab8500-btemp ab8500-btemp.0: No fg found
[ 1.253997] ab8500-btemp ab8500-btemp.0: ab8500_btemp_id get batctrl res failed
[ 1.261291] ab8500-btemp ab8500-btemp.0: failed to identify the battery
[ 1.277252] ab8500-fg ab8500-fg.0: falling back to legacy platform data
[ 1.289733] Switching to clocksource dbx500-prcmu-timer
[ 1.319610] AppArmor: AppArmor Filesystem Enabled
[ 1.353912] NET: Registered protocol family 2
[ 1.359039] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 1.366210] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 1.372833] TCP: Hash tables configured (established 8192 bind 8192)
[ 1.379425] TCP: reno registered
[ 1.382659] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 1.388671] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 1.395355] NET: Registered protocol family 1
[ 1.400573] NetWinder Floating Point Emulator V0.97 (double precision)
[ 1.407196] CPU PMU: probing PMU on CPU 0
[ 1.411224] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 1.420837] audit: initializing netlink socket (disabled)
[ 1.426269] type=2000 audit(1.130:1): initialized
[ 1.445343] bounce pool size: 64 pages
[ 1.449371] VFS: Disk quotas dquot_6.5.2
[ 1.453430] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.460632] 9p: Installing v9fs 9p2000 file system support
[ 1.466156] msgmni has been set to 1054
[ 1.471069] io scheduler noop registered
[ 1.474975] io scheduler deadline registered (default)
[ 1.480285] io scheduler cfq registered
[ 1.485229] uart-pl011 uart0: DMA channel TX dma0chan2
[ 1.490417] uart-pl011 uart0: DMA channel RX dma0chan3
[ 1.495544] uart-pl011 uart1: DMA channel TX dma0chan4
[ 1.500732] uart-pl011 uart1: DMA channel RX dma0chan5
[ 1.505889] uart-pl011 uart2: DMA channel TX dma0chan6
[ 1.511047] uart-pl011 uart2: DMA channel RX dma0chan7
[ 1.516540] [drm] Initialized drm 1.1.0 20060810
[ 1.532897] brd: module loaded
[ 1.542419] loop: module loaded
[ 1.546844] tun: Universal TUN/TAP device driver, 1.6
[ 1.551940] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 1.558898] smsc911x: Driver version 2008-10-21
[ 1.563537] smsc911x smsc911x.0: Failed to get supply 'vdd33a': -517
[ 1.570434] smsc911x smsc911x.0 (unregistered net_device): couldn't get regulators -517
[ 1.578552] platform smsc911x.0: Driver smsc911x requests probe deferral
[ 1.585449] PPP generic driver version 2.4.2
[ 1.590209] PPP MPPE Compression module registered
[ 1.595642] usbcore: registered new interface driver cdc_acm
[ 1.601348] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 1.609405] Initializing USB Mass Storage driver...
[ 1.614501] usbcore: registered new interface driver usb-storage
[ 1.620574] USB Mass Storage support registered.
[ 1.625183] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[ 1.633972] input: AB8500 POn(PowerOn) Key as /devices/soc0/db8500-prcmu.0/ab8500-core.0/ab8500-poweron-key.0/input/input0
[ 1.662811] ab8500-rtc ab8500-rtc.0: rtc core: registered ab8500-rtc as rtc0
[ 1.670257] i2c /dev entries driver
[ 1.675018] ab8500-chargalg ab8500-chargalg.0: falling back to legacy platform data
[ 1.683166] ab8500-chargalg ab8500-chargalg.0: probe success
[ 1.689331] device-mapper: uevent: version 1.0.3
[ 1.694274] device-mapper: ioctl: 4.23.1-ioctl (2012-12-18) initialised: dm-devel at redhat.com
[ 1.702789] Bluetooth: HCI UART driver ver 2.2
[ 1.707336] cpufreq for DB8500 started
[ 1.711151] db8500-cpufreq : Failed to get armss clk
[ 1.716125] db8500-cpufreq : Failed to get armss clk
[ 1.721435] cpuidle: using governor ladder
[ 1.725677] cpuidle: using governor menu
[ 1.730682] mmci-pl18x sdi4: Provided ocr_mask/setpower will not be used (using regulator instead)
[ 1.739746] mmci-pl18x sdi4: mmc0: PL180 manf 80 rev4 at 0x80114000 irq 131,0 (pio)
[ 1.747497] mmci-pl18x sdi4: DMA channels RX dma0chan24, TX dma0chan25
[ 1.785675] mmci-pl18x sdi0: Provided ocr_mask/setpower will not be used (using regulator instead)
[ 1.794799] mmci-pl18x sdi0: mmc1: PL180 manf 80 rev4 at 0x80126000 irq 92,0 (pio)
[ 1.802520] mmci-pl18x sdi0: DMA channels RX dma0chan26, TX dma0chan27
[ 1.846679] usbcore: registered new interface driver usbhid
[ 1.852325] usbhid: USB HID core driver
[ 1.857025] usbcore: registered new interface driver snd-usb-audio
[ 1.864257] Netfilter messages via NETLINK v0.30.
[ 1.869110] nf_conntrack version 0.5.0 (12790 buckets, 51160 max)
[ 1.875488] ctnetlink v0.93: registering with nfnetlink.
[ 1.881256] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 1.886688] TCP: cubic registered
[ 1.890197] NET: Registered protocol family 10
[ 1.895446] NET: Registered protocol family 17
[ 1.900085] NET: Registered protocol family 15
[ 1.904724] Bluetooth: RFCOMM TTY layer initialized
[ 1.909729] Bluetooth: RFCOMM socket layer initialized
[ 1.914886] Bluetooth: RFCOMM ver 1.11
[ 1.918731] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1.924072] Bluetooth: BNEP filters: protocol multicast
[ 1.929351] mmc0: new high speed MMC card at address 0001
[ 1.929382] Bluetooth: BNEP socket layer initialized
[ 1.929382] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1.929382] Bluetooth: HIDP socket layer initialized
[ 1.929412] NET: Registered protocol family 35
[ 1.955078] 9pnet: Installing 9P2000 support
[ 1.955749] mmcblk0: mmc0:0001 3.53 GiB
[ 1.955963] mmcblk0boot0: mmc0:0001 partition 1 2.00 MiB
[ 1.956176] mmcblk0boot1: mmc0:0001 partition 2 2.00 MiB
[ 1.956390] mmcblk0rpmb: mmc0:0001 partition 3 128 KiB
[ 1.979492] NET: Registered protocol family 37
[ 1.984069] Key type dns_resolver registered
[ 1.984100] mmcblk0: p1 p2 p3
[ 1.991577] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 2
[ 1.999481] Registering SWP/SWPB emulation handler
[ 2.007751] LDO-USB: disabling
[ 2.010925] db8500-esram34: disabling
[ 2.014648] db8500-esram12: disabling
[ 2.018890] EN-3V3: Failed to request enable GPIO337: -517
[ 2.024597] input: gpio-keys as /devices/soc0/gpio-keys/input/input1
[ 2.024658] reg-fixed-voltage reg-fixed-voltage.1: Failed to register regulator: -517
[ 2.024688] platform reg-fixed-voltage.1: Driver reg-fixed-voltage requests probe deferral
[ 2.024780] ab8500-charger ab8500-charger.0: falling back to legacy platform data
[ 2.024963] ab8500-charger ab8500-charger.0: failed to get vddadc regulator
[ 2.024993] platform ab8500-charger.0: Driver ab8500-charger requests probe deferral
[ 2.025054] smsc911x: Driver version 2008-10-21
[ 2.025146] smsc911x smsc911x.0: Failed to get supply 'vdd33a': -517
[ 2.025146] smsc911x smsc911x.0 (unregistered net_device): couldn't get regulators -517
[ 2.025177] platform smsc911x.0: Driver smsc911x requests probe deferral
[ 2.095001] mmcblk0boot1: unknown partition table
[ 2.100128] EN-3V3: Failed to request enable GPIO337: -517
[ 2.106201] reg-fixed-voltage reg-fixed-voltage.1: Failed to register regulator: -517
[ 2.114379] platform reg-fixed-voltage.1: Driver reg-fixed-voltage requests probe deferral
[ 2.122802] ab8500-charger ab8500-charger.0: falling back to legacy platform data
[ 2.122833] ab8500-rtc ab8500-rtc.0: setting system clock to 2013-01-24 17:10:21 UTC (1359047421)
[ 2.122955] ALSA device list:
[ 2.122955] No soundcards found.
[ 2.145721] mmcblk0boot0: unknown partition table
[ 2.150878] ab8500-charger ab8500-charger.0: failed to get vddadc regulator
[ 2.158020] platform ab8500-charger.0: Driver ab8500-charger requests probe deferral
[ 2.165832] smsc911x: Driver version 2008-10-21
[ 2.170532] smsc911x smsc911x.0: Failed to get supply 'vdd33a': -517
[ 2.176910] smsc911x smsc911x.0 (unregistered net_device): couldn't get regulators -517
[ 2.184967] platform smsc911x.0: Driver smsc911x requests probe deferral
[ 2.185119] EXT3-fs (mmcblk0p3): error: couldn't mount because of unsupported optional features (240)
[ 2.186431] EXT2-fs (mmcblk0p3): error: couldn't mount because of unsupported optional features (244)
[ 2.210479] EN-3V3: Failed to request enable GPIO337: -517
[ 2.216278] reg-fixed-voltage reg-fixed-voltage.1: Failed to register regulator: -517
[ 2.224121] platform reg-fixed-voltage.1: Driver reg-fixed-voltage requests probe deferral
[ 2.604156] EXT4-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is recommended
[ 2.618927] EXT4-fs (mmcblk0p3): recovery complete
[ 2.631408] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[ 2.639587] VFS: Mounted root (ext4 filesystem) on device 179:3.
[ 2.650085] devtmpfs: mounted
[ 2.653350] Freeing init memory: 312K
[ 3.095977] init: ureadahead main process (692) terminated with status 5
[ 3.983581] mmci-pl18x sdi4: error during DMA transfer!
[ 3.988952] mmcblk0rpmb: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
[ 3.998840] mmcblk0rpmb: retrying using single block read
[ 4.412017] mmci-pl18x sdi4: error during DMA transfer!
[ 4.417358] mmcblk0rpmb: error -110 transferring data, sector 8, nr 8, cmd response 0x900, card status 0xb00
[ 4.427429] mmcblk0rpmb: retrying using single block read
[ 4.842041] mmci-pl18x sdi4: error during DMA transfer!
[ 4.847381] mmcblk0rpmb: error -110 transferring data, sector 24, nr 8, cmd response 0x900, card status 0xb00
[ 4.857360] mmcblk0rpmb: retrying using single block read
[ 5.272949] mmci-pl18x sdi4: error during DMA transfer!
[ 5.278289] mmcblk0rpmb: error -110 transferring data, sector 56, nr 8, cmd response 0x900, card status 0xb00
[ 5.288269] mmcblk0rpmb: retrying using single block read
[ 5.703063] mmci-pl18x sdi4: error during DMA transfer!
[ 5.708404] mmcblk0rpmb: error -110 transferring data, sector 120, nr 8, cmd response 0x900, card status 0xb00
[ 5.718475] mmcblk0rpmb: retrying using single block read
[ 6.132965] mmci-pl18x sdi4: error during DMA transfer!
[ 6.138336] mmcblk0rpmb: error -110 transferring data, sector 64, nr 8, cmd response 0x900, card status 0xb00
[ 6.148315] mmcblk0rpmb: retrying using single block read
[ 6.563507] mmci-pl18x sdi4: error during DMA transfer!
[ 6.568847] mmcblk0rpmb: error -110 transferring data, sector 16, nr 8, cmd response 0x900, card status 0xb00
[ 6.579071] mmcblk0rpmb: retrying using single block read
[ 6.994110] mmci-pl18x sdi4: error during DMA transfer!
[ 6.999450] mmcblk0rpmb: error -110 transferring data, sector 128, nr 8, cmd response 0x900, card status 0xb00
[ 7.009521] mmcblk0rpmb: retrying using single block read
[ 7.424499] mmci-pl18x sdi4: error during DMA transfer!
[ 7.429870] mmcblk0rpmb: error -110 transferring data, sector 32, nr 8, cmd response 0x900, card status 0xb00
[ 7.439819] mmcblk0rpmb: retrying using single block read
[ 7.472686] mmcblk0boot0: r/w command failed, status = 0x80000900
[ 7.478851] end_request: I/O error, dev mmcblk0boot0, sector 3832
[ 7.484954] Buffer I/O error on device mmcblk0boot0, logical block 479
* Starting mDNS/DNS-SD daemon^[[74G[ OK ]
* Starting configure network device security^[[74G[ OK ]
[ 11.248016] mmci-pl18x sdi4: error during DMA transfer!
[ 11.253417] mmcblk0rpmb: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
[ 11.792541] mmci-pl18x sdi4: error during DMA transfer!
[ 11.797973] mmcblk0rpmb: error -110 transferring data, sector 24, nr 8, cmd response 0x900, card status 0xb00
[ 12.237579] mmci-pl18x sdi4: error during DMA transfer!
[ 12.242980] mmcblk0rpmb: error -110 transferring data, sector 8, nr 8, cmd response 0x900, card status 0xb00
* Starting Mount network filesystems^[[74G[ OK ]
* Starting Upstart job to start rpcbind on boot only^[[74G[ OK ]
* Starting Failsafe Boot Delay^[[74G[ OK ]
* Stopping Upstart job to start rpcbind on boot only^[[74G[ OK ]
* Starting Bridge socket events into upstart^[[74G[ OK ]
[ 12.788513] mmci-pl18x sdi4: error during DMA transfer!
[ 12.793945] mmcblk0rpmb: error -110 transferring data, sector 56, nr 8, cmd response 0x900, card status 0xb00
[ 12.823486] mmcblk0boot0: r/w command failed, status = 0x80000900
[ 12.836425] end_request: I/O error, dev mmcblk0boot0, sector 3832
[ 12.842529] Buffer I/O error on device mmcblk0boot0, logical block 479
* Stopping Mount network filesystems^[[74G[ OK ]
* Starting RPC portmapper replacement^[[74G[ OK ]
* Starting Start this job to wait until rpcbind is started or fails to start^[[74G[ OK ]
* Stopping Start this job to wait until rpcbind is started or fails to start^[[74G[ OK ]
* Stopping rpcsec_gss daemon^[[74G[ OK ]
[ 13.397216] mmci-pl18x sdi4: error during DMA transfer!
[ 13.402618] mmcblk0rpmb: error -110 transferring data, sector 120, nr 8, cmd response 0x900, card status 0xb00
[ 14.008239] mmci-pl18x sdi4: error during DMA transfer!
[ 14.013610] mmcblk0rpmb: error -110 transferring data, sector 64, nr 8, cmd response 0x900, card status 0xb00
[ 14.463684] mmci-pl18x sdi4: error during DMA transfer!
[ 14.469177] mmcblk0rpmb: error -110 transferring data, sector 16, nr 8, cmd response 0x900, card status 0xb00
[ 14.911254] mmci-pl18x sdi4: error during DMA transfer!
[ 14.916625] mmcblk0rpmb: error -110 transferring data, sector 128, nr 8, cmd response 0x900, card status 0xb00
[ 15.366241] mmci-pl18x sdi4: error during DMA transfer!
[ 15.371612] mmcblk0rpmb: error -110 transferring data, sector 32, nr 8, cmd response 0x900, card status 0xb00
[ 15.831939] mmci-pl18x sdi4: error during DMA transfer!
[ 15.837341] mmcblk0rpmb: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
* Starting NSM status monitor^[[74G[ OK ]
* Stopping Failsafe Boot Delay^[[74G[ OK ]
* Starting System V initialisation compatibility^[[74G[ OK ]
* Starting configure network device^[[74G[ OK ]
* Stopping cold plug devices^[[74G[ OK ]
* Stopping log initial device creation^[[74G[ OK ]
[ 16.339935] gadget: no file given for LUN0
[ 16.417297] g_multi musb-hdrc.0.auto: failed to start g_multi: -22
Last login: Thu Jan 24 17:09:11 UTC 2013 on tty1
speech-dispatcher disabled; edit /etc/default/speech-dispatcher
Checking for running unattended-upgrades:
Welcome to Linaro 12.02 (GNU/Linux 3.8.0-rc4-test+ armv7l)
* Documentation: https://wiki.linaro.org/
New release '12.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
*** /dev/mmcblk0p3 will be checked for errors at next reboot ***
* Starting bluetooth ^[[80G root at linaro-ubuntu-desktop:~# ^[[74G[ OK ]
^[[33m*^[[39;49m PulseAudio configured for per-user sessions
saned disabled; edit /etc/default/saned
-- Steve
^ permalink raw reply
* [PATCH v2 00/30] USB: omap-ehci: Move PHY management to PHY driver
From: Mohammed, Afzal @ 2013-01-30 13:12 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <510916B2.7080509@ti.com>
Hi Roger,
On Wed, Jan 30, 2013 at 18:18:50, Quadros, Roger wrote:
> On 01/30/2013 02:08 PM, Mohammed, Afzal wrote:
> > Please try to ensure that beagle bone USB0 works with this.
> I do not have beaglebone with me and don't seem to find beaglebone
> board support in mainline.
Ok. Fyi, beagle bone is supported in mainline - it is dt boot.
Regards
Afzal
> I would appreciate if someone who knows more about beaglebone can help
> with verification.
>
> I could find that Robert C Nelson (now in cc) is maintaining out of tree
> patches for the beaglebone. Maybe he could help with verification?
^ permalink raw reply
* [PATCH] ARM i.MX25: clk: parent per5_clk to AHB clock
From: Steffen Trumtrar @ 2013-01-30 13:10 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130130095353.GI8668@pengutronix.de>
On Wed, Jan 30, 2013 at 10:53:53AM +0100, Uwe Kleine-K?nig wrote:
> On Wed, Jan 30, 2013 at 10:33:55AM +0100, Steffen Trumtrar wrote:
> > The mxc-timer on the imx25 needs to be derived from the AHB clock.
> > If a bootloader reparents this clock to the ipg_clk_highfreq, which according
> > to the datasheet is a valid operation, the system can/will produce lockups/
> > freezes after some time [1].
> >
> > This can be forced with code like
> > while(1)
> > syscall(SYS_clock_gettime, CLOCK_REALTIME, &tp);
> >
> > This was already fixed with the commit
> > "i.MX25 GPT clock fix: ensure correct the clock source" [2],
> > but it seems, that it got lost. So, re-add this to have a correct gpt.
> >
> > [1]: http://lists.arm.linux.org.uk/lurker/message/20130129.161230.229bda17.en.html
> > [2]: 2012d9ca2a1381ae3e733330a7f0d1d2f1988bba
> Instead of the last paragraph I'd write:
>
> This problem was already fixed with commit
>
> 2012d9c (i.MX25 GPT clock fix: ensure correct the clock source)
>
> for v3.1-rc2 but this was lost when i.MX was converted to the common
> clock framework (commit 6bbaec5; ARM i.MX25: implement clocks using
> common clock framework).
>
> > Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> > Cc: stable at vger.kernel.org
>
> Cc: stable at vger.kernel.org # v3.5+
>
That is better. I will resend my patch in a sec with a new commit message.
Thanks,
Steffen
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
^ permalink raw reply
* [PATCH v2 19/27] pci: PCIe driver for Marvell Armada 370/XP systems
From: Thomas Petazzoni @ 2013-01-30 13:07 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130130120344.GA29490@avionic-0098.mockup.avionic-design.de>
Dear Thierry Reding,
On Wed, 30 Jan 2013 13:03:44 +0100, Thierry Reding wrote:
> That approach isn't going to work very well with multi-platform,
> though, since the function can only be overridden on a
> per-architecture basis.
I can do like is done for pcibios_align_resource(): put a single
implementation of the function in arch/arm/kernel/bios32.c, and make it
call a hook registered in the hw_pci structure, or even directly use a
numerical value in hw_pci, as Russell suggested earlier.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply
* [PATCH 2/2] ARM: imx_v6_v7_defconfig: Add VPU support
From: Shawn Guo @ 2013-01-30 13:04 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1359474553-8949-2-git-send-email-fabio.estevam@freescale.com>
On Tue, Jan 29, 2013 at 01:49:13PM -0200, Fabio Estevam wrote:
> Let the VPU driver be built by default.
>
Do we have any imx_v6_v7 platform supported by VPU driver today?
Shawn
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> arch/arm/configs/imx_v6_v7_defconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/configs/imx_v6_v7_defconfig b/arch/arm/configs/imx_v6_v7_defconfig
> index 6966713..83822d9 100644
> --- a/arch/arm/configs/imx_v6_v7_defconfig
> +++ b/arch/arm/configs/imx_v6_v7_defconfig
> @@ -160,6 +160,8 @@ CONFIG_MEDIA_CAMERA_SUPPORT=y
> CONFIG_SOC_CAMERA=y
> CONFIG_SOC_CAMERA_OV2640=y
> CONFIG_VIDEO_MX3=y
> +CONFIG_V4L_MEM2MEM_DRIVERS=y
> +CONFIG_VIDEO_CODA=y
> CONFIG_FB=y
> CONFIG_LCD_PLATFORM=y
> CONFIG_BACKLIGHT_LCD_SUPPORT=y
> --
> 1.7.9.5
>
>
^ permalink raw reply
* [PATCH V3 0/5] W1: Support onewire master on i.MX53
From: Shawn Guo @ 2013-01-30 13:02 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20130129154608.5184.46101.stgit@localhost>
On Tue, Jan 29, 2013 at 04:46:08PM +0100, Martin Fuzzey wrote:
> W1: Support onewire master on i.MX53
> * Add device tree and pinctrl support to the MXC master driver
> * Convert to use devm_
> * Add i.MX53 clocks
> * Add i.MX53 device tree entries
Applied, thanks.
I changed the patch order a little bit, moving dts change to the last,
and also fix the patch subject prefix.
W1: Add device tree support to MXC onewire master.
W1: Convert MXC onewire master to devm_ functions.
W1: Add pinctrl support to MXC onewire master.
ARM: i.MX53: Add clocks for i.mx53 onewire master.
ARM: dts: Add device tree entry for onewire master on i.MX53
One 'new blank line at EOF' warning on patch #1 gets fixed.
And please remember to add some commit log for patches you submit in
the future. Empty commit log is not good.
Shawn
^ permalink raw reply
* [PATCH v2 00/30] USB: omap-ehci: Move PHY management to PHY driver
From: Roger Quadros @ 2013-01-30 12:48 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93EA95DF0@DBDE01.ent.ti.com>
On 01/30/2013 02:08 PM, Mohammed, Afzal wrote:
> Hi Roger,
>
> On Mon, Jan 28, 2013 at 17:00:01, Quadros, Roger wrote:
>
>> NOTE: Tested on 4460ES-B1 Panda and BeagleBoard C4 only. Other boards are only
>> build tested.
>
> Please try to ensure that beagle bone USB0 works with this.
>
Hi Afzal,
I do not have beaglebone with me and don't seem to find beaglebone
board support in mainline.
I would appreciate if someone who knows more about beaglebone can help
with verification.
I could find that Robert C Nelson (now in cc) is maintaining out of tree
patches for the beaglebone. Maybe he could help with verification?
regards,
-roger
^ permalink raw reply
* [PATCH] ARM:boot: support the command with COMMAND_LINE_SIZE - 1 useful chars
From: Chen Gang @ 2013-01-30 12:32 UTC (permalink / raw)
To: linux-arm-kernel
originally, not support the command with COMMAND_LINE_SIZE - 1 useful chars.
but in fact, we can support it:
Signed-off-by: Chen Gang <gang.chen@asianux.com>
---
arch/arm/boot/compressed/atags_to_fdt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/compressed/atags_to_fdt.c b/arch/arm/boot/compressed/atags_to_fdt.c
index aabc02a..ed23ec2 100644
--- a/arch/arm/boot/compressed/atags_to_fdt.c
+++ b/arch/arm/boot/compressed/atags_to_fdt.c
@@ -63,7 +63,7 @@ static void merge_fdt_bootargs(void *fdt, const char *fdt_cmdline)
/* copy the fdt command line into the buffer */
fdt_bootargs = getprop(fdt, "/chosen", "bootargs", &len);
if (fdt_bootargs)
- if (len < COMMAND_LINE_SIZE) {
+ if (len <= COMMAND_LINE_SIZE) {
memcpy(ptr, fdt_bootargs, len);
/* len is the length of the string
* including the NULL terminator */
@@ -73,7 +73,7 @@ static void merge_fdt_bootargs(void *fdt, const char *fdt_cmdline)
/* and append the ATAG_CMDLINE */
if (fdt_cmdline) {
len = strlen(fdt_cmdline);
- if (ptr - cmdline + len + 2 < COMMAND_LINE_SIZE) {
+ if (ptr - cmdline + len + 2 <= COMMAND_LINE_SIZE) {
*ptr++ = ' ';
memcpy(ptr, fdt_cmdline, len);
ptr += len;
--
1.7.10.4
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox