aboutsummaryrefslogtreecommitdiff
path: root/arch
AgeCommit message (Collapse)Author
2011-03-17OMAP4: PandaBoard: remove unused power regulatorsDavid Anders
the pandaboard does not use the VUSIM or VAUX1 power regulators on the TWL6030 and are left floating. if the VUSIM and VAUX1 power regulators are initilized, noise on the unloaded regulators generates an overcurrent interrupt causing the system to power down. this patch removes the initialization of the unused power regulators of VUSIM and VAUX1. Signed-off-by: David Anders <x0132446@ti.com> Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org>
2011-03-17OMAP4:Fix -EINVAL for vana, vcxio, vdacBalaji T K
Fixed regulators in twl6030 do not have set_voltage hook. Regulator core returns -22 if set_voltage is NULL and apply_uV is set while applying the constraint to set voltage resulting in failure during probe of these regulators. Do not set apply_uV for fixed regulators which don't have set_voltage. machine_constraints_voltage: VANA: failed to apply 2100000uV constraint twl_reg twl_reg.43: can't register VANA, -22 twl_reg: probe of twl_reg.43 failed with error -22 machine_constraints_voltage: VCXIO: failed to apply 1800000uV constraint twl_reg twl_reg.44: can't register VCXIO, -22 twl_reg: probe of twl_reg.44 failed with error -22 machine_constraints_voltage: VDAC: failed to apply 1800000uV constraint twl_reg twl_reg.45: can't register VDAC, -22 twl_reg: probe of twl_reg.45 failed with error -22 Signed-off-by: Balaji T K <balajitk@ti.com>
2011-03-16mach-ux500: fix build errorJohn Rigby
the commit: mach-ux500: basic HREFv60 support v2 u8500_init_machine was changed to mop500_init_machine and 2 of 3 uses instances of .init_machine were changed. Fix the 3rd one. Signed-off-by: John Rigby <john.rigby@linaro.org>
2011-03-16Revert "LINARO: WORKAROUND: Temporarily disable display on OMAP4"John Rigby
This reverts commit f03bf640e07f4ba62db11963707eab048e230164. Signed-off-by: John Rigby <john.rigby@linaro.org>
2011-03-16LINARO: WORKAROUND: Temporarily disable display on OMAP4John Rigby
Signed-off-by: John Rigby <john.rigby@linaro.org>
2011-03-16(drop after v2.6.38) x86, quirk: Fix SB600 revision checkAndreas Herrmann
Commit 7f74f8f28a2bd9db9404f7d364e2097a0c42cc12 (x86 quirk: Fix polarity for IRQ0 pin2 override on SB800 systems) introduced a regression. It removed some SB600 specific code to determine the revision ID without adapting a corresponding revision ID check for SB600. See this mail thread http://marc.info/?l=linux-kernel&m=129980296006380&w=2 This patch adapts the corresponding check to cover all SB600 revisions. Cc: stable@kernel.org # 38.x, 37.x, 32.x Tested-by: Wang Lei <f3d27b@gmail.com> Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16UBUNTU: SAUCE: match up ENTRY/END naming for 32/64 bitAndy Whitcroft
Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16Quirk to fix suspend/resume on Lenovo Edge 11,13,14,15Manoj Iyer
Set acpi_skip_timer_override to force ignoring BIOS IRQ0 pin2 override. This fixes resume from suspend on AMD based ThinkPad Edge 11,13,14 and 15. Please note that with this patch applied, you will see a warning message from the kernel, this is printed in acpi/boot.c before it sets acpi_skip_timer_override=1; [ 0.000000] ------------[ cut here ]------------ [ 0.000000] WARNING: at /home/manjo/ubuntu-maverick-674710/arch/x86/kernel/acpi/boot.c:1345 dmi_ignore_irq0_timer_override+0x2e/0x52() [ 0.000000] Hardware name: 254523U [ 0.000000] ati_ixp4x0 quirk not complete. [ 0.000000] Modules linked in: [ 0.000000] Pid: 0, comm: swapper Not tainted 2.6.35-25-generic #43 [ 0.000000] Call Trace: [ 0.000000] [<c014ad42>] warn_slowpath_common+0x72/0xa0 [ 0.000000] [<c0826724>] ? dmi_ignore_irq0_timer_override+0x2e/0x52 [ 0.000000] [<c0826724>] ? dmi_ignore_irq0_timer_override+0x2e/0x52 [ 0.000000] [<c014ae13>] warn_slowpath_fmt+0x33/0x40 [ 0.000000] [<c0826724>] dmi_ignore_irq0_timer_override+0x2e/0x52 [ 0.000000] [<c04dd7d0>] dmi_check_system+0x30/0x50 [ 0.000000] [<c0826df4>] acpi_boot_table_init+0x10/0x7d [ 0.000000] [<c0821ea7>] ? io_delay_init+0x16/0x18 [ 0.000000] [<c081f556>] setup_arch+0x562/0x645 [ 0.000000] [<c012cf19>] ? default_spin_lock_flags+0x9/0x10 [ 0.000000] [<c081b57b>] start_kernel+0xcf/0x374 [ 0.000000] [<c081b0d7>] i386_start_kernel+0xd7/0xdf [ 0.000000] ---[ end trace a7919e7f17c0a725 ]--- [ 0.000000] ThinkPad Edge detected: Ignoring BIOS IRQ0 pin2 override Signed-off-by: Manoj Iyer <manoj.iyer@canonical.com> BugLink: http://launchpad.net/bugs/702434 Acked-by: Stefan Bader <stefan.bader@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16UBUNTU: SAUCE: OMAP3630: PM: don't warn the user with a trace in case of ↵Ricardo Salveti de Araujo
PM34XX_ERRATUM This patch has been submitted upstream, but likely won't make 2.6.38. In case in user has a OMAP3630 < ES1.2 the kernel should warn the user about the ERRATUM, but using pr_warning instead of WARN_ON is already enough, as there is nothing else the user can do besides changing the board. With this we avoid having the following calltrace while booting with some Beagle xM revisions: WARNING: at /home/apw/build/ubuntu-natty2/ubuntu-natty2/arch/arm/mach-omap2/cpuidle34xx.c:468 omap_init_power_states+0x230/0x238() omap_init_power_states: core off state C7 disabled due to i583 Modules linked in: [<c00596f4>] (unwind_backtrace+0x0/0xfc) from [<c04f29a8>] (dump_stack+0x18/0x1c) [<c04f29a8>] (dump_stack+0x18/0x1c) from [<c008510c>] (warn_slowpath_common+0x5c/0x6c) [<c008510c>] (warn_slowpath_common+0x5c/0x6c) from [<c00851c0>] (warn_slowpath_fmt+0x38/0x40) [<c00851c0>] (warn_slowpath_fmt+0x38/0x40) from [<c00676f4>] (omap_init_power_states+0x230/0x238) [<c00676f4>] (omap_init_power_states+0x230/0x238) from [<c00131a0>] (omap3_idle_init+0x74/0x18c) [<c00131a0>] (omap3_idle_init+0x74/0x18c) from [<c00126b4>] (omap3_pm_init+0x1ac/0x308) [<c00126b4>] (omap3_pm_init+0x1ac/0x308) from [<c00474c0>] (do_one_initcall+0x3c/0x1b4) [<c00474c0>] (do_one_initcall+0x3c/0x1b4) from [<c0008d58>] (kernel_init+0xe0/0x178) [<c0008d58>] (kernel_init+0xe0/0x178) from [<c00532c8>] (kernel_thread_exit+0x0/0x8) ---[ end trace e639b107cbbc60f1 ]--- Signed-off-by: Ricardo Salveti de Araujo <ricardo.salveti@canonical.com> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
2011-03-16UBUNTU: SAUCE: omap3: beaglexm: fix DVI initializationRicardo Salveti de Araujo
Function beagle_twl_gpio_setup is called after beagle_display_init, what makes lets reset_gpio with an invalid value at the time it request the gpio. As a side effect the DVI reset GPIO is not properly set. Also removing old code that power down DVI in a hardcoded way, as it's not necessary anymore. Tested with Beagle-xM and C4. Signed-off-by: Ricardo Salveti de Araujo <ricardo.salveti@canonical.com> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
2011-03-16UBUNTU: SAUCE: x86 fix up jiffies/jiffies_64 handlingAndy Whitcroft
Based on a patched by Anvin, H Peter <h.peter.anvin@intel.com> and Shaohua Li <shaohua.li@intel.com>. Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16UBUNTU: SAUCE: ARM: Adding vdd_sdi regulator supply to OMAP3EVMMathieu J. Poirier
https://bugs.launchpad.net/bugs/630885 Taken from Maverick and slightly modified to compile in Natty. When booting, the omapdss subsystem is looking for a regulator named "vdds_sdi". When the regulator is not found the initialisation sequence is aborted resulting in omapfb not finding a display to work with. This patch allows the omapfb sub system to complete its initialisation properly and enable LCD display. The problem was fixed by lumping a "vdds_sdi" with the already existing "vdds_dsi" regulator. This fix takes its root from work done on the Beagle board and the Pandora board. More spefically: - 7b097896e4a5b5ea4798db806e63a1138b1b8eb8 - f6873eedd94df20cfb705856a78440a4c176c6b6 Signed-off-by: Mathieu Poirier <mathieu.poirier@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16Revert "UBUNTU: SAUCE: Enable speedstep for sonoma processors."Andy Whitcroft
This reverts commit 15d3c038e86bb4b2f4a3d430d777b6f1cf6ca7ef. As per discussion with Colin King, this is very old and never was accepted upstream. We should drop it and see who screams. Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16nx-emu: fix inverted report of disable_nxKees Cook
This nx-emu commit: http://git.kernel.org/?p=linux/kernel/git/frob/linux-2.6-roland.git;a=commitdiff;h=b86f45c02494d4cba26caf132e8a178854e812fd was intended to replace "exec_shield" with "!disable_nx", but in x86_report_nx() it was not correctly inverted resulting in a backward report to dmesg about the state of nx-emu. Signed-off-by: Kees Cook <kees.cook@canonical.com> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
2011-03-16Revert "ARM: initial stack protector (-fstack-protector) support"Andy Whitcroft
This reverts commit e186433a0b95417413ac9726d974de80322ea72c. Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16Revert "[ARM] implement arch_randomize_brk()"Andy Whitcroft
This reverts commit 5523e01b790d956164021e6ac4bde605723946a8. Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16UBUNTU: SAUCE: nx-emu: use upstream ASLR when possibleKees Cook
Only perform ASCII-armor ASLR when nx-emulation is happening. Signed-off-by: Kees Cook <kees.cook@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16exec-randomization: brk away from exec rand areaKees Cook
This is a fix for the NX emulation patch to force the brk area well outside of the exec randomization area to avoid future allocation or brk growth collisions. Normally this isn't a problem, except when the text region has been loaded from a PIE binary and the CS limit can't be put just above bss. A test-case that will show failures without this patch can be found here: http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/annotate/head%3A/scripts/kernel-aslr-collisions/explode-brk.c Signed-off-by: Kees Cook <kees.cook@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16mmap randomization for executable mappings on 32-bitRoland McGrath
This code is originally from Ingo, with some later rebasing and fixes to respect all the randomization-disabling knobs. It provides a new address randomization algorithm that's preferable for executable mappings in 32-bit processes. Signed-off-by: Roland McGrath <roland@redhat.com> Signed-off-by: Kees Cook <kees.cook@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16nx-emu: standardize boottime message prefixKees Cook
The state of NX in the booted kernel is easier to find in dmesg if all the possible modes start with the same bit of text. There's no good reason to have the NX-emulation message have a different format. Signed-off-by: Kees Cook <kees.cook@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16nx-emu: drop exec-shield sysctl, merge with disable_nxKees Cook
The "exec-shield" sysctl doesn't really make much sense any more, and the functionality is better merged with the existing "disable_nx" kernel boot option. Signed-off-by: Kees Cook <kees.cook@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16i386: NX emulationRoland McGrath
This is old code with some cruft, all originally by Ingo with much later rebasing by Fedora folks and at least one arcane fix by Roland a few years ago. Signed-off-by: Roland McGrath <roland@redhat.com> Signed-off-by: Kees Cook <kees.cook@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16[ARM] implement arch_randomize_brk()Nicolas Pitre
For this feature to take effect, CONFIG_COMPAT_BRK must be turned off. This can safely be turned off for any EABI user space versions. Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org> (cherry picked from commit 990cb8acf23cab19a2930f1ed5e7dc108f89079b) Signed-off-by: Leann Ogasawara <leann.ogasawara@canonical.com>
2011-03-16ARM: initial stack protector (-fstack-protector) supportNicolas Pitre
This is the very basic stuff without the changing canary upon task switch yet. Just the Kconfig option and a constant canary value initialized at boot time. Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org> (cherry picked from commit c743f38013aeff58ef6252601e397b5ba281c633) Signed-off-by: Leann Ogasawara <leann.ogasawara@canonical.com>
2011-03-16UBUNTU: SAUCE: fix pv-ops for legacy XenJohn Johansen
Import fix_xen_guest_on_old_EC2.patch from fedora 14 Legacy hypervisors (RHEL 5.0 and RHEL 5.1) do not handle guest writes to cr4 gracefully. If a guest attempts to write a bit of cr4 that is unsupported, then the HV is so offended it crashes the domain. While later guest kernels (such as RHEL6) don't assume the HV supports all features, they do expect nicer responses. That assumption introduced code that probes whether or not xsave is supported early in the boot. So now when attempting to boot a RHEL6 guest on RHEL5.0 or RHEL5.1 an early crash will occur. This patch is quite obviously an undesirable hack. The real fix for this problem should be in the HV, and is, in later HVs. However, to support running on old HVs, RHEL6 can take this small change. No impact will occur for running on any RHEL HV (not even RHEL 5.5 supports xsave). There is only potential for guest performance loss on upstream Xen. All this by way of explanation for why is this patch not going upstream. Signed-off-by: John Johansen <john.johansen@canonical.com> Signed-off-by: Tim Gardner <tim.gardner@canonical.com> Signed-off-by: Leann Ogasawara <leann.ogasawara@canonical.com>
2011-03-16UBUNTU: SAUCE: ARM: OMAP: Add macros for comparing silicon revisionLee Jones
BugLink: http://bugs.launchpad.net/bugs/608095 Adapted from arago project patch by Sanjeev Premi <premi@ti.com> This helps provide the required setup to enable USB Ethernet (usb0) and USB host on the XM Beagleboard (A rev). This will be submitted upstream by Steve Sakoman. Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Lee Jones <lee.jones@canonical.com> Signed-off-by: Leann Ogasawara <leann.ogasawara@canonical.com>
2011-03-16UBUNTU: ARM: Adding regulator supply for vdds_sdi.Mathieu J. Poirier
The omapfb driver couldn't locate its display sink because of an initialisation error in the DSS subsystem. This error was caused by a missing 'sdi' entry in the board power regulator list. BugLink: https://bugs.launchpad.net/bugs/597904 Signed-off-by: Mathieu Poirier <mathieu.poirier@canonical.com> Signed-off-by: Leann Ogasawara <leann.ogasawara@canonical.com>
2011-03-16UBUNTU: SAUCE: (no-up) dma-mapping: Remove WARN_ON in dma_free_coherentStefan Bader
BugLink: http://bugs.launchpad.net/bugs/458201 Triggered by the following backtrace: WARNING: at /build/buildd/linux-2.6.32/arch/x86/include/asm/dma-mapping.h:154 ___free_dma_mem_cluster+0x102/0x110() [<ffffffff81064f9b>] warn_slowpath_common+0x7b/0xc0 [<ffffffff81064ff4>] warn_slowpath_null+0x14/0x20 [<ffffffff8139a2a2>] ___free_dma_mem_cluster+0x102/0x110 [<ffffffff8139a072>] __sym_mfree+0xd2/0x100 [<ffffffff8139a109>] __sym_mfree_dma+0x69/0x100 [<ffffffff8139245f>] sym_hcb_free+0x8f/0x1f0 This patch never will be accepted upstream because the WARN_ON is supposed to perevent driver development which is only compatible with x86 on x86 (ARM can sleep in that function). The right way to fix it would be to make the offending function use locks in the right way but that requires careful implementation. Signed-off-by: Stefan Bader <stefan.bader@canonical.com> Acked-by: Andy Whitcroft <apw@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16x86, mce: Make xeon75xx memory driver dependent on PCIAndi Kleen
commit 757fd770c649b0dfa6eeefc2d5e2ea3119b6be9c upstream (linux-2.6-tip) Found by Ingo Molnar's automated tester. Reported-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Andi Kleen <ak@linux.intel.com> LKML-Reference: <20100123113359.GA29555@one.firstfloor.org> Signed-off-by: H. Peter Anvin <hpa@zytor.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16x86, mce: Rename cpu_specific_poll to mce_cpu_specific_pollH. Peter Anvin
commit f91c4d2649531cc36e10c6bc0f92d0f99116b209 upstream (linux-2.6-tip) cpu_specific_poll is a global variable, and it should have a global namespace name. Since it is MCE-specific (it takes a struct mce *), rename it mce_cpu_specific_poll. Signed-off-by: H. Peter Anvin <hpa@zytor.com> Cc: Andi Kleen <andi@firstfloor.org> LKML-Reference: <20100121221711.GA8242@basil.fritz.box> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16x86, mce: Xeon75xx specific interface to get corrected memory error informationAndi Kleen
commit c773f70fd6b53ee646727f871833e53649907264 upstream (linux-2.6-tip) Xeon 75xx doesn't log physical addresses on corrected machine check events in the standard architectural MSRs. Instead the address has to be retrieved in a model specific way. This makes it impossible to do predictive failure analysis. Implement cpu model specific code to do this in mce-xeon75xx.c using a new hook that is called from the generic poll code. The code retrieves the physical address/DIMM of the last corrected error from the platform and makes the address look like a standard architectural MCA address for further processing. In addition the DIMM information is retrieved and put into two new aux0/aux1 fields in struct mce. These fields are specific to a given CPU. These fields can then be decoded by mcelog into specific DIMM information. The latest mcelog version has support for this. Longer term this will be likely in a different output format, but short term that seemed like the least intrusive solution. Older mcelog can deal with an extended record. There's no code to print this information on a panic because this only works for corrected errors, and corrected errors do not usually result in panics. The act of retrieving the DIMM/PA information can take some time, so this code has a rate limit to avoid taking too much CPU time on a error flood. The whole thing can be loaded as a module and has suitable PCI-IDs so that it can be auto-loaded by a distribution. The code also checks explicitely for the expected CPU model number to make sure this code doesn't run anywhere else. Signed-off-by: Andi Kleen <ak@linux.intel.com> LKML-Reference: <20100121221711.GA8242@basil.fritz.box> Signed-off-by: H. Peter Anvin <hpa@zytor.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16UBUNTU: (no-up) arm -- enable ubuntu/ directoryEric Miao
Signed-off-by: Eric Miao <eric.miao@canonical.com> Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16UBUNTU: SAUCE: (no-up) select a v7 CPU for versatileLoic Minier
This allows us to use this kernel under QEMU while still using the main Ubuntu ARMv7 userspace. Signed-off-by: Andy Whitcroft <apw@canonical.com>
2011-03-16UBUNTU: SAUCE: Enable speedstep for sonoma processors.cking
OriginalAuthor: Christophe Dumez, repackaged by Wolfgang Tremmel OriginalLocation: http://launchpadlibrarian.net/11575235/speedstep-sonoma.patch Bug: 132271 Signed-off-by: Colin Ian King <colin.king@canonical.com> Signed-off-by: Ben Collins <ben.collins@canonical.com>
2011-03-16UBUNTU: (no-up) fold down debian for ubuntu-natty 2.6.36 rebaseLeann Ogasawara
Ignore: yes Signed-off-by: Leann Ogasawara <leann.ogasawara@canonical.com>
2011-03-15Merge commit '10a8c38' (rmk/misc branch) into linaro-2.6.38Nicolas Pitre
Conflicts: arch/arm/Kconfig
2011-03-15ARM: omap3: Fix assembler breakage in sleep34xx.SJohn Rigby
Assembler in latest binutils needs extra option to enable smc instructions introduced in: ARM: omap3: Remove hand-encoded SMC instructions Signed-off-by: John Rigby <john.rigby@linaro.org> Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org>
2011-03-15Merge remote-tracking branch 'rmk/devel-stable' into linaro-2.6.38Nicolas Pitre
Conflicts: arch/arm/mach-exynos4/cpufreq.c arch/arm/mach-exynos4/irq-eint.c arch/arm/mach-mx5/clock-mx51-mx53.c arch/arm/mach-ux500/board-mop500-sdi.c arch/arm/plat-s5p/Makefile
2011-03-15Merge remote-tracking branch 'rmk/fixes' into linaro-2.6.38Nicolas Pitre
2011-03-15Merge commit 'v2.6.38' into linaro-2.6.38Nicolas Pitre
2011-03-15Merge branch 'for-rmk' of ↵Russell King
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung into devel-stable Conflicts: arch/arm/mm/Kconfig
2011-03-15Merge branch 'davinci-next-2' of ↵Russell King
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-davinci into devel-stable
2011-03-15davinci: DM644x EVM: register MUSB device earlierSergei Shtylyov
The MUSB driver doesn't see its platform device on DM644x EVM board anymore since commit 73b089b052a69020b953312a624a6e1eb5b81fab (usb: musb: split davinci to its own platform_driver) because the new probe is called as subsys_initcall() now, and the device is registered later than that by the board code. Move the registration to davinci_evm_init() -- it's safe to do so because the MUSB core device still gets initialized as fs_initcall() -- which is late enough for the I2C GPIO expander (which controls VBUS) to be initialized. Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com> Acked-by: Felipe Balbi <balbi@ti.com> Tested-by: Sekhar Nori <nsekhar@ti.com> Signed-off-by: Kevin Hilman <khilman@ti.com>
2011-03-15davinci: add spi devices on tnetv107x evmCyril Chemparathy
This patch adds definitions for spi devices on the tnetv107x evm platform. Signed-off-by: Cyril Chemparathy <cyril@ti.com> Signed-off-by: Sekhar Nori <nsekhar@ti.com> Signed-off-by: Kevin Hilman <khilman@ti.com>
2011-03-15davinci: add ssp config for tnetv107x evm boardCyril Chemparathy
This patch adds SSP configuration and pin muxing info for tnetv107x evm boards. Signed-off-by: Cyril Chemparathy <cyril@ti.com> Signed-off-by: Sekhar Nori <nsekhar@ti.com> Signed-off-by: Kevin Hilman <khilman@ti.com>
2011-03-15davinci: add tnetv107x ssp platform deviceCyril Chemparathy
This patch adds an SSP platform device definition for the tnetv107x soc family. The clock lookup entry has also been updated to match. Signed-off-by: Cyril Chemparathy <cyril@ti.com> Signed-off-by: Sekhar Nori <nsekhar@ti.com> Signed-off-by: Kevin Hilman <khilman@ti.com>
2011-03-15ARM: EXYNOS4: Implement Clock gating for System MMUKyongHo Cho
This patch includes the implementation of the clock gating for System MMU. Initially, all System MMUs are not asserted the system clock. Asserting the system clock to a System MMU is enabled only when s5p_sysmmu_enable() is called. Likewise, it is disabled only when s5p_sysmmu_disable() is called. Therefore, clock gating on System MMUs are still invisible to the outside of the System MMU driver. Signed-off-by: KyongHo Cho <pullip.cho@samsung.com> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
2011-03-15ARM: EXYNOS4: Enhancement of System MMU driverKyongHo Cho
This patch includes the following enhancements for System MMU: - Enhanced readability - Removal of unused data structures or their members - Simplified function definitions - Corrections of some logical errors - Full compliance with Linux coding style - Simpler way of registering callback functions of System MMU faults Signed-off-by: KyongHo Cho <pullip.cho@samsung.com> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
2011-03-15ARM: EXYNOS4: Add support for gpio interruptsMarek Szyprowski
This patch adds support for gpio interrupts on Samsung EXYNOS4 platform. Common s5p-gpioint.c code is used for handling gpio interrupts. Each gpio line that needs gpio interrupt support must be later registered with s5p_register_gpio_interrupt() function. Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
2011-03-15ARM: S5P: Add function to register gpio interrupt bank dataMarek Szyprowski
This patch removes all global data from common s5p gpio interrupt handler code. This enables to reuse this code on EXYNOS4 platform. Instead of global data (IRQ_GPIOINT interrupt number, S5P_GPIOINT_GROUP_MAXNR groups count), a s5p_register_gpioint_bank() function is introduced. It is aimed to be called from gpiolib init. Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-13 08:21:31 +0000