aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2012-05-21blackfin: add spi/sport3/ppi head file for bf60xScott Jiang3-0/+493
Signed-off-by: Scott Jiang <[email protected]> Signed-off-by: Bob Liu <[email protected]>
2012-05-21blackfin: cplb: add support for bf60xBob Liu4-2/+16
Bf60x support big CPLB pages, this commit enable it. Signed-off-by: Bob Liu <[email protected]>
2012-05-21blackfin: mach-common: add sec support for bf60xSteven Miao2-39/+385
Add system event controller support for bf60x so that interrupt can be handled. Signed-off-by: Steven Miao <[email protected]> Signed-off-by: Bob Liu <[email protected]>
2012-05-21blackfin: bf60x: add clock supportSteven Miao6-2/+495
Add clock support for bf60x. Signed-off-by: Steven Miao <[email protected]> Signed-off-by: Bob Liu <[email protected]>
2012-05-21blackfin: add bf60x to current frameworkBob Liu19-146/+840
This patch added bf60x to current blackfin kernel framework. Signed-off-by: Bob Liu <[email protected]>
2012-05-21blackfin: mach-bf609: add machine filesSonic Zhang20-0/+9781
Add machine files for bf60x including head files, Kconfig/Makefile and board file. Signed-off-by: Sonic Zhang <[email protected]> Signed-off-by: Bob Liu <[email protected]>
2012-05-21blackfin: asm: fix blackfin.h brokenBob Liu1-6/+2
do{...}while makes no sense in __ASSEMBLY__ code paths. now kernels fail to build: arch/blackfin/mach-bf561/atomic.S: Assembler messages: arch/blackfin/mach-bf561/atomic.S:48: Error: syntax error. Input text was do. arch/blackfin/mach-bf561/atomic.S:48: Error: arch/blackfin/mach-bf561/atomic.S:48: Error: syntax error. Input text was }. arch/blackfin/mach-bf561/atomic.S:48: Error: arch/blackfin/mach-bf561/atomic.S:53: Error: syntax error. Input text was do. arch/blackfin/mach-bf561/atomic.S:53: Error: arch/blackfin/mach-bf561/atomic.S:53: Error: syntax error. Input text was }. Signed-off-by: Bob Liu <[email protected]>
2012-05-21blackfin: configs: add SMP support back to BF561-EZKIT-SMP_defconfigBob Liu1-3/+1
SMP support was removed from BF561-EZKIT-SMP_defconfig in last commit by mistake, this patch add it back. Signed-off-by: Bob Liu <[email protected]>
2012-05-20Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/netDavid S. Miller60-260/+514
2012-05-20iscsi-target: Fix iov_count calculation bug in iscsit_allocate_iovecsNicholas Bellinger1-1/+1
This patch fixes a bug in iscsit_allocate_iovecs() where iov_count was incorrectly calculated using min(1UL, data_length / PAGE_SIZE) instead of max(1UL, data_length / PAGE_SIZE), that ends up triggering an OOPs for large block I/O when the SGL <-> iovec mapping exceeds the bogus iov_count allocation size. This is a regression introduced during the iscsi-target conversion back to using core memory allocation here: commit bfb79eac2026b411df9e253a9c350039b4b04bb7 Author: Andy Grover <[email protected]> Date: Tue Apr 3 15:51:29 2012 -0700 target/iscsi: Go back to core allocating data buffer for cmd Cc: Andy Grover <[email protected]> Signed-off-by: Nicholas Bellinger <[email protected]>
2012-05-20Linux 3.4Linus Torvalds1-1/+1
2012-05-20ipv6/exthdrs: strict Pad1 and PadN checkEldad Zack1-1/+14
The following tightens the padding check from commit c1412fce7eccae62b4de22494f6ab3ff8a90c0c6 : * Take into account combinations of consecutive Pad1 and PadN. * Catch the corner case of when only padding is present in the header, when the extention header length is 0 (i.e., 8 bytes). In this case, the header would have exactly 6 bytes of padding: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : Next Header : Hdr Ext Len=0 : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + : Padding (Pad1 or PadN) : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Signed-off-by: Eldad Zack <[email protected]> Signed-off-by: David S. Miller <[email protected]>
2012-05-20USB: qmi_wwan: Add ZTE (Vodafone) K3520-ZAndrew Bird (Sphere Systems)1-0/+18
Signed-off-by: Andrew Bird <[email protected]> Acked-by: Bjørn Mork <[email protected]> Signed-off-by: David S. Miller <[email protected]>
2012-05-20USB: qmi_wwan: Add ZTE (Vodafone) K3765-ZAndrew Bird (Sphere Systems)1-0/+9
Add the ZTE (Vodafone) K3765-Z to the whitelist. This requires the previous patch to make the whitelist with forced interface 4 generic or the device fails to initialise. After applying this patch and loading the Option driver without usb-modeswitch's bind all interfaces trick, a wwan0 net interface and /dev/cdc-wdm0 device file were created. Using Bjorn Mork's perl connection script a connection was made to a mobile network using QMI and the network interface's IPv4 address was configured OK. Signed-off-by: Andrew Bird <[email protected]> Acked-by: Bjørn Mork <[email protected]> Signed-off-by: David S. Miller <[email protected]>
2012-05-20USB: qmi_wwan: Make forced int 4 whitelist genericAndrew Bird (Sphere Systems)1-2/+2
Change the forced interface 4 whitelist to use the generic shared binder instead of the Gobi specific one. Certain ZTE devices (K3520-Z & K3765-Z) don't work with the Gobi version, but function quite happily with the generic. This has been tested with the following devices: K3520-Z K3565-Z K3765-Z K4505-Z It hasn't been tested with the ZTE MF820D, which is the only other device that uses this whitelist at present. Although Bjorn doesn't expect any problems, any testing with that device would be appreciated. Signed-off-by: Andrew Bird <[email protected]> Acked-by: Bjørn Mork <[email protected]> Signed-off-by: David S. Miller <[email protected]>
2012-05-20sparc32: use flushi when run-time patching in per_cpu_patchSam Ravnborg3-13/+10
Davis S. Miller wrote: " The way we do that now is overkill. We only needed to use the MMU cache ops when we had sun4c around because sun4c lacked support for the "flush" instruction. But all sun4m and later chips have it so we can use it unconditionally. So in the per_cpu_patch() code, get rid of the cache ops invocation, and instead execute a "flush %reg" after each of the instruction patch assignments, where %reg is set to the address of the instruction that was stored into. Perhaps take the flushi() definition from asm/cacheflush_64.h and place it into asm/cacheflush.h, then you can simply use that. " Implemented as per suggestion. Moved run-time patching before we call paging_init(), so helper methods in paging_init() may utilise run-time patching too. Signed-off-by: Sam Ravnborg <[email protected]> Signed-off-by: David S. Miller <[email protected]>
2012-05-20sparc32: fix cpuid_patch run-time patchingSam Ravnborg1-0/+2
We hang forever when trying to do run-time patching of instructions identified by the cpuid_patch section Signed-off-by: Sam Ravnborg <[email protected]> Signed-off-by: David S. Miller <[email protected]>
2012-05-20pinctrl: pinctrl-imx: add imx51 pinctrl driverDong Aisheng4-0/+2118
ChangeLog v1->v2: * change PIN_FUNC_ID base in binding doc to 0 from 1. Acked-by: Shawn Guo <[email protected]> Acked-by: Stephen Warren <[email protected]> Signed-off-by: Dong Aisheng <[email protected]> Signed-off-by: Linus Walleij <[email protected]>
2012-05-20pinctrl: pinctrl-imx: add imx53 pinctrl driverDong Aisheng4-0/+2860
ChangeLog v1->v2: * change PIN_FUNC_ID base in binding doc to 0 from 1. Acked-by: Shawn Guo <[email protected]> Acked-by: Stephen Warren <[email protected]> Signed-off-by: Dong Aisheng <[email protected]> Signed-off-by: Linus Walleij <[email protected]>
2012-05-20regulator: tps65910: use of_node of matched regulator being registerLaxman Dewangan1-7/+12
After getting matched regulators by using of_regulator_match(), initialize the config.of_node of regulator being register with of_regulator_match.of_node of that regulator. This is require for supporting regulator consumers in dt. Signed-off-by: Laxman Dewangan <[email protected]> Signed-off-by: Mark Brown <[email protected]>
2012-05-20regulator: tps65910: dt: support when "regulators" node foundLaxman Dewangan1-0/+4
The device tree binding for the tps65910 is described as: tps65911 { reg = <0x2d> ::::::::: regulators { compatible = "ti,tps65911"; ldo1_reg: ldo1 { /** regulator entry */ }; ldo2_reg: ldo2 { /** regulator entry */ }; :::::::::: }; }; Support the regulators functionality only when there is "regulators" child node available for tps65910. Signed-off-by: Laxman Dewangan <[email protected]> Signed-off-by: Mark Brown <[email protected]>
2012-05-20regulator: tps65910: add error message in case of failureLaxman Dewangan1-4/+8
Prints error message whenever there is failure on resource allocation. Also used dev_* to print messages instead of pr_* Signed-off-by: Laxman Dewangan <[email protected]> Signed-off-by: Mark Brown <[email protected]>
2012-05-20regulator: tps62360: dt: initialize of_node param for regulator register.Laxman Dewangan1-0/+1
Initialize config.of_node for regulator before registering. This is needed for DT based regulator support. Regulator stores this of_node value in rdev->dev.of_node and used for lookup when client ask for regulator_get(). Signed-off-by: Laxman Dewangan <[email protected]> Signed-off-by: Mark Brown <[email protected]>
2012-05-20m68k: add a defconfig for the M5475EVB ColdFire with MMU boardGreg Ungerer1-0/+62
Add a default configuration for the newly supported ColdFire CPUs running with MMU enabled. This is based on Freescales own M5475EVB demo board. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: unaligned.h fix for M68000 coreLuis Alves1-1/+1
This patch fixes unaligned memory access for the 68000 core based cpu's. Some time ago, my cpu (68000) was raising address/bus error's when mounting cifs shares (didn't bother to debug it at the time). After developing the MMC/SD card driver I was having the same issue when mounting the vfat fs. I've traced the issue down to the 'unaligned.h' file. (I guess nobody has ever used unaligned.h back in the 68328 'era'. Signed-off-by: Luis Alves <[email protected]> Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68k: merge the MMU and non-MMU versions of the arch dma codeGreg Ungerer3-209/+162
The majority of the m68k architecture dma code is the same, so merge the current separated files dma_no.c and dma_mm.c back into a single dma.c The main alloc and free routines are a little different, so we keep a single #ifdef based on CONFIG_MMU for them. All the other support functions are now identical. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Geert Uytterhoeven <[email protected]>
2012-05-20m68knommu: reorganize the no-MMU cache flushing to match m68kGreg Ungerer1-4/+28
Introduce cache_push() and cache_clear() functions for the non-MMU m68k devices. With these in place we can more easily merge some of the common m68k arch code. In particular by reorganizing the __flush_cache_all() code and separating the cache push and clear functions it becomes trivial to implement the new cache_push() and cache_clear() functions. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Geert Uytterhoeven <[email protected]>
2012-05-20m68knommu: move the 54xx platform code into the common ColdFire code directoryGreg Ungerer5-21/+2
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 532x platform code into the common ColdFire code directoryGreg Ungerer4-20/+1
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 5407 platform code into the common ColdFire code directoryGreg Ungerer4-20/+1
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 5307 platform code into the common ColdFire code directoryGreg Ungerer5-22/+4
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 528x platform code into the common ColdFire code directoryGreg Ungerer4-20/+1
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 527x platform code into the common ColdFire code directoryGreg Ungerer4-20/+1
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 5272 platform code into the common ColdFire code directoryGreg Ungerer5-20/+1
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 5249 platform code into the common ColdFire code directoryGreg Ungerer5-20/+1
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 523x platform code into the common ColdFire code directoryGreg Ungerer4-19/+1
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 520x platform code into the common ColdFire code directoryGreg Ungerer4-19/+1
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: move the 5206 platform code into the common ColdFire code directoryGreg Ungerer4-22/+2
All these separate directories for each ColdFire CPU SoC varient seems like overkill. The majority of them only contain a single small config file. Move these into the common ColdFire code directory. Signed-off-by: Greg Ungerer <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 5407 GPIO struct setupGreg Ungerer3-28/+10
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 532x GPIO struct setupGreg Ungerer3-44/+26
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 5307 GPIO struct setupGreg Ungerer3-28/+10
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 528x GPIO struct setupGreg Ungerer3-50/+32
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 527x GPIO struct setupGreg Ungerer3-62/+44
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 5272 GPIO struct setupGreg Ungerer3-30/+12
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 5249 GPIO struct setupGreg Ungerer3-29/+11
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 523x GPIO struct setupGreg Ungerer3-41/+23
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 520x GPIO struct setupGreg Ungerer3-35/+17
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: simplify the ColdFire 5206 GPIO struct setupGreg Ungerer3-28/+10
The GPIO data struct setup is now the only remaining code in the platform gpio.c file. So move it to the platform config.c code and remove the gpio.c file. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: make duplicated ColdFire GPIO init code common for allGreg Ungerer13-100/+34
The code that adds each ColdFire platforms GPIO signals is duplicated in each platforms specific code. Remove it from each platforms code and put a single version in the existing ColdFire gpio subsystem init code. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
2012-05-20m68knommu: switch to GPIO init macros in ColdFire 532x init codeGreg Ungerer1-303/+17
Modify the GPIO setup table to use the mcfgpio.h macros for table init. Simplifies code and reduces line count significantly. Signed-off-by: Greg Ungerer <[email protected]> Acked-by: Steven King <[email protected]>
Powered by cgit, Gruvboxed by Blaster4385.