An error occurred fetching the project authors.
- 30 Mar, 2013 8 commits
-
-
Mark A. Greer authored
The omap_init_aes() routine in devices.c only needs to be called when there is no device tree present. CC: Paul Walmsley <paul@pwsan.com> Signed-off-by:
Mark A. Greer <mgreer@animalcreek.com> Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
Mark A. Greer authored
Remove the error message that prints when there is no AES IP present to make it consistent with all the other IPs. CC: Paul Walmsley <paul@pwsan.com> Signed-off-by:
Mark A. Greer <mgreer@animalcreek.com> Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
Mark A. Greer authored
Convert the device data for the OMAP3 AES crypto IP from explicit platform_data to hwmod. CC: Paul Walmsley <paul@pwsan.com> Signed-off-by:
Mark A. Greer <mgreer@animalcreek.com> [paul@pwsan.com: fixed lines causing sparse warnings] Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
Mark A. Greer authored
Convert the device data for the OMAP2 AES crypto IP from explicit platform_data to hwmod. CC: Paul Walmsley <paul@pwsan.com> Signed-off-by:
Mark A. Greer <mgreer@animalcreek.com> [paul@pwsan.com: fixed lines causing sparse warnings] Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
Mark A. Greer authored
The omap_init_sham() routine in devices.c only needs to be called when there is no device tree present. CC: Paul Walmsley <paul@pwsan.com> Signed-off-by:
Mark A. Greer <mgreer@animalcreek.com> Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
Mark A. Greer authored
Remove the error message that prints when there is no SHA IP present to make it consistent with all the other IPs. CC: Paul Walmsley <paul@pwsan.com> Signed-off-by:
Mark A. Greer <mgreer@animalcreek.com> Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
Mark A. Greer authored
Convert the device data for the OMAP3 SHAM2 (SHA1/MD5) crypto IP from explicit platform_data to hwmod. CC: Paul Walmsley <paul@pwsan.com> Signed-off-by:
Mark A. Greer <mgreer@animalcreek.com> [paul@pwsan.com: updated to use per-SoC registration lists for GP-only hwmods; fixed lines causing sparse warnings] Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
Mark A. Greer authored
Convert the device data for the OMAP2 SHAM crypto IP from explicit platform_data to hwmod. CC: Paul Walmsley <paul@pwsan.com> Signed-off-by:
Mark A. Greer <mgreer@animalcreek.com> [paul@pwsan.com: fixed lines causing sparse warnings] Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
- 12 Feb, 2013 1 commit
-
-
Paul Walmsley authored
Commit c1d1cd59 ("ARM: OMAP2+: omap_device: remove obsolete pm_lats and early_device code") missed a few omap_device_build() calls that aren't included as part of the default OMAP2+ Kconfig, omap2plus_defconfig. Ideally, all devices that are present on the SoC should be created by default, and only the corresponding device driver should be configured or deconfigured in Kconfig. This allows drivers to be built as modules and loaded later, even if they weren't part of the original kernel build. Unfortunately, we're not quite there yet. Thanks to Tony Lindgren for reporting this, found during his randconfig tests. Signed-off-by:
Paul Walmsley <paul@pwsan.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 06 Feb, 2013 1 commit
-
-
Kishon Vijay Abraham I authored
A seperate driver has been added to handle the usb part of control module. A device for the above driver is created here, using the register address information to be used by the driver for powering on the PHY and for writing to the mailbox. Signed-off-by:
Kishon Vijay Abraham I <kishon@ti.com> Acked-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
- 26 Jan, 2013 1 commit
-
-
Paul Walmsley authored
Remove now-obsolete code from arch/arm/mach-omap2/omap_device.c. This mostly consists of removing the first attempt at device PM latency handling. This was never really used, has been replaced by the common dev_pm_qos code, and needs to go away as part of the DT conversion. Also, the early platform_device creation code has been removed, as it appears to be unused. Signed-off-by:
Paul Walmsley <paul@pwsan.com> Cc: Kevin Hilman <khilman@deeprootsystems.com>
-
- 21 Jan, 2013 1 commit
-
-
Tony Lindgren authored
Otherwise we will get: WARNING: vmlinux.o(.text+0x1d4f0): Section mismatch in reference from the function omap_init_ocp2scp() to the function .init.text:omap_device_build() The function omap_init_ocp2scp() references the function __init omap_device_build(). This is often because omap_init_ocp2scp lacks a __init annotation or the annotation of omap_device_build is wrong. Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 11 Jan, 2013 1 commit
-
-
Tony Lindgren authored
This way the initcalls don't run on other SoCs on multiplatform kernels. Otherwise we'll get something like this when booting on vexpress: omap_hwmod: _ensure_mpu_hwmod_is_setup: MPU initiator hwmod mpu not yet registered ... WARNING: at arch/arm/mach-omap2/pm.c:82 _init_omap_device+0x74/0x94() _init_omap_device: could not find omap_hwmod for mpu ... omap-dma-engine omap-dma-engine: OMAP DMA engine driver ... Tested-by:
Ezequiel Garcia <ezequiel.garcia@free-electrons.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 03 Dec, 2012 1 commit
-
-
Omar Ramirez Luna authored
Use hwmod data and device attributes to build and register an omap device for iommu driver. - Update the naming convention in isp module. - Remove unneeded check for number of resources, as this is now handled by omap_device and prevents driver from loading. - Now unused, remove platform device and resource data, handling of sysconfig register for softreset purposes, use default latency structure. - Use hwmod API for reset handling. Signed-off-by:
Omar Ramirez Luna <omar.luna@linaro.org> Tested-by:
Ohad Ben-Cohen <ohad@wizery.com> Signed-off-by:
Joerg Roedel <joro@8bytes.org>
-
- 30 Nov, 2012 1 commit
-
-
Tony Lindgren authored
Based on earlier discussions[1] we attempted to find a suitable location for the omap DMA header in commit 2b6c4e73 (ARM: OMAP: DMA: Move plat/dma.h to plat-omap/dma-omap.h) until the conversion to dmaengine is complete. Unfortunately that was before I was able to try to test compile of the ARM multiplatform builds for omap2+, and the end result was not very good. So I'm creating yet another all over the place patch to cut the last dependency for building omap2+ for ARM multiplatform. After this, we have finally removed the driver dependencies to the arch/arm code, except for few drivers that are being worked on. The other option was to make the <plat-omap/dma-omap.h> path to work, but we'd have to add some new header directory to for multiplatform builds. Or we would have to manually include arch/arm/plat-omap/include again from arch/arm/Makefile for omap2+. Neither of these alternatives sound appealing as they will likely lead addition of various other headers exposed to the drivers, which we want to avoid for the multiplatform kernels. Since we already have a minimal include/linux/omap-dma.h, let's just use that instead and add a note to it to not use the custom omap DMA functions any longer where possible. Note that converting omap DMA to dmaengine depends on dmaengine supporting automatically incrementing the FIFO address at the device end, and converting all the remaining legacy drivers. So it's going to be few more merge windows. [1] https://patchwork.kernel.org/patch/1519591/# cc: Russell King <linux@arm.linux.org.uk> cc: Kevin Hilman <khilman@ti.com> cc: "Benoît Cousson" <b-cousson@ti.com> cc: Herbert Xu <herbert@gondor.apana.org.au> cc: "David S. Miller" <davem@davemloft.net> cc: Vinod Koul <vinod.koul@intel.com> cc: Dan Williams <djbw@fb.com> cc: Mauro Carvalho Chehab <mchehab@infradead.org> cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com> cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de> cc: David Woodhouse <dwmw2@infradead.org> cc: Kyungmin Park <kyungmin.park@samsung.com> cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> cc: Tomi Valkeinen <tomi.valkeinen@ti.com> cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de> cc: Hans Verkuil <hans.verkuil@cisco.com> cc: Vaibhav Hiremath <hvaibhav@ti.com> cc: Lokesh Vutla <lokeshvutla@ti.com> cc: Rusty Russell <rusty@rustcorp.com.au> cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> cc: Afzal Mohammed <afzal@ti.com> cc: linux-crypto@vger.kernel.org cc: linux-media@vger.kernel.org cc: linux-mtd@lists.infradead.org cc: linux-usb@vger.kernel.org cc: linux-fbdev@vger.kernel.org Acked-by:
Felipe Balbi <balbi@ti.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 28 Nov, 2012 1 commit
-
-
Sakari Ailus authored
Add the registers used to configure the CSI-2 receiver PHY on OMAP3430 and 3630 and map them in the ISP driver. The register is part of the control block but it only is needed by the ISP driver. Signed-off-by:
Sakari Ailus <sakari.ailus@iki.fi> Acked-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
- 20 Nov, 2012 1 commit
-
-
Tony Lindgren authored
Move iommu/iovmm headers from plat/ to platform_data/ as part of the single zImage work. Partially based on an earlier version by Ido Yariv <ido@wizery.com>. Cc: Ido Yariv <ido@wizery.com> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Cc: Omar Ramirez Luna <omar.luna@linaro.org> Acked-by:
Mauro Carvalho Chehab <mchehab@redhat.com> Acked-by:
Ohad Ben-Cohen <ohad@wizery.com> Acked-by:
Joerg Roedel <joro@8bytes.org> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 07 Nov, 2012 1 commit
-
-
Kishon Vijay Abraham I authored
Platfrom device for ocp2scp is created using omap_device_build in devices file. This is used for both omap4(musb) and omap5(dwc3). This is needed to fix MUSB regression caused by commit c9e4412a (arm: omap: phy: remove unused functions from omap-phy-internal.c) Signed-off-by:
Kishon Vijay Abraham I <kishon@ti.com> [tony@atomide.com: updated comments for regression info] Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 30 Oct, 2012 1 commit
-
-
Paul Walmsley authored
The OMAP watchdog timer driver directly calls a function exported by code in arch/arm/mach-omap2. This is not good; it tightly couples this driver to the mach-omap2 integration code. Instead, add a temporary platform_data function pointer to abstract this function call. A subsequent patch will convert the watchdog driver to use this function pointer. This patch also moves the device creation code out of arch/arm/mach-omap2/devices.c and into arch/arm/mach-omap2/wd_timer.c. This is another step towards the removal of arch/arm/mach-omap2/devices.c. Cc: Wim Van Sebroeck <wim@iguana.be> Acked-by:
Wim Van Sebroeck <wim@iguana.be> [paul@pwsan.com: skip wd_timer device creation when DT blob is present] Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
- 18 Oct, 2012 1 commit
-
-
Tony Lindgren authored
Let's make omap_hwmod local to mach-omap2 for ARM common zImage support. Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 17 Oct, 2012 1 commit
-
-
Tony Lindgren authored
Let's make omap_device local to mach-omap2 for ARM common zImage support. Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 16 Oct, 2012 1 commit
-
-
Sebastien Guiriec authored
Correct DMIC hwmod lockup error message and replace printk() by pr_err(). Signed-off-by:
Sebastien Guiriec <s-guiriec@ti.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 15 Oct, 2012 2 commits
-
-
Lokesh Vutla authored
Move plat/dma.h to plat-omap/dma-omap.h as part of single zImage work Signed-off-by:
Lokesh Vutla <lokeshvutla@ti.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
Lokesh Vutla authored
Similar to omap1, some of the omap2+ dma channel definitions are used by some drivers. For moving omap2+ dma channel definitions to mach-omap2/, the used ones should be defined locally to driver. Drivers can eliminate it using DT, platform data, or IORESOURCE_DMA And moving omap2+ DMA channel definitions to mach-omap2 Signed-off-by:
Lokesh Vutla <lokeshvutla@ti.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 23 Sep, 2012 2 commits
-
-
Jon Hunter authored
Convert OMAP2/3 devices to use HWMOD for creating a PMU device. To support PMU on OMAP2 devices we only need to use MPU sub-system and so we can simply use the MPU HWMOD to create the PMU device. To support PMU on OMAP3 devices, we need to use the MPU and DEBUG sub-systems and so use these HWMODs to create the PMU device for OMAP3. The MPU HWMOD for OMAP2/3 devices is currently missing the PMU interrupt and so add the PMU interrupt to the MPU HWMOD for these devices. This change also moves the PMU code out of the mach-omap2/devices.c files into its own pmu.c file as suggested by Kevin Hilman to de-clutter devices.c. Cc: Ming Lei <ming.lei@canonical.com> Cc: Will Deacon <will.deacon@arm.com> Cc: Benoit Cousson <b-cousson@ti.com> Cc: Paul Walmsley <paul@pwsan.com> Cc: Kevin Hilman <khilman@ti.com> Signed-off-by:
Jon Hunter <jon-hunter@ti.com> [paul@pwsan.com: fixed checkpatch messages; updated to apply; dropped old-style initial filename line in header comments] Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
Paul Walmsley authored
Move the OMAP1-specific RNG device creation off to mach-omap1/devices.c, and create a omap_device-backed registration function for OMAP2+ devices in mach-omap2/devices.c. As a nice side-benefit, we can also get rid of arch/arm/plat-omap/devices.c, thanks to some recent changes from Tony. One change from the previous behavior is that the RNG devices are now registered unconditionally. This should allow the RNG drivers to be loaded as modules, even if the original kernel was not built that way. Signed-off-by:
Paul Walmsley <paul@pwsan.com>
-
- 20 Sep, 2012 1 commit
-
-
Tony Lindgren authored
This can be local to mach-omap2. Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 19 Sep, 2012 1 commit
-
-
Arnd Bergmann authored
Platform data for device drivers should be defined in include/linux/platform_data/*.h, not in the architecture and platform specific directories. This moves such data out of the omap include directories Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Acked-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Acked-by:
Nicolas Pitre <nico@linaro.org> Acked-by:
Tony Lindgren <tony@atomide.com> Cc: Kevin Hilman <khilman@ti.com> Cc: "Benoît Cousson" <b-cousson@ti.com> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: David Woodhouse <dwmw2@infradead.org> Cc: Kyungmin Park <kyungmin.park@samsung.com> Cc: Ohad Ben-Cohen <ohad@wizery.com> Cc: Grant Likely <grant.likely@secretlab.ca> Cc: Omar Ramirez Luna <omar.ramirez@ti.com> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com> Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de> Cc: Peter Ujfalusi <peter.ujfalusi@ti.com> Cc: Jarkko Nikula <jarkko.nikula@bitmer.com> Cc: Liam Girdwood <lrg@ti.com> Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Cc: Jean Pihet <j-pihet@ti.com> Cc: J Keerthy <j-keerthy@ti.com> Cc: linux-omap@vger.kernel.org
-
- 17 Sep, 2012 1 commit
-
-
Matt Porter authored
Enable pinctrl dummy states for all OMAP platforms that don't populate DT. This allows drivers to be converted to pinctrl and not generate new warnings on platforms that do not provide pinctrl data. These platforms already have pinmuxes configured before the drivers probe. Signed-off-by:
Matt Porter <mporter@ti.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 13 Sep, 2012 2 commits
-
-
Tony Lindgren authored
As the plat and mach includes need to disappear for single zImage work, we need to remove plat/hardware.h. Do this by splitting plat/hardware.h into omap1 and omap2+ specific files. The old plat/hardware.h already has omap1 only defines, so it gets moved to mach/hardware.h for omap1. For omap2+, we use the local soc.h that for now just includes the related SoC headers to keep this patch more readable. Note that the local soc.h still includes plat/cpu.h that can be dealt with in later patches. Let's also include plat/serial.h from common.h for all the board-*.c files. This allows making the include files local later on without patching these files again. Note that only minimal changes are done in this patch for the drivers/watchdog/omap_wdt.c driver to keep things compiling. Further patches are needed to eventually remove cpu_is_omap usage in the drivers. Also only minimal changes are done to sound/soc/omap/* to remove the unneeded includes and to define OMAP44XX_MCPDM_L3_BASE locally so there's no need to include omap44xx.h. While at it, also sort some of the includes in the standard way. Cc: linux-watchdog@vger.kernel.org Cc: alsa-devel@alsa-project.org Cc: Peter Ujfalusi <peter.ujfalusi@ti.com> Cc: Jarkko Nikula <jarkko.nikula@bitmer.com> Cc: Liam Girdwood <lrg@ti.com> Acked-by:
Wim Van Sebroeck <wim@iguana.be> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
Tony Lindgren authored
As the interrupts should only be defined in the platform_data, and eventually coming from device tree, there's no need to define them in header files. Let's remove the hardcoded references to irqs.h and fix up the includes so we don't rely on headers included in irqs.h. Note that we're defining OMAP_INTC_START as 0 to the interrupts. This will be needed when we enable SPARSE_IRQ. For some drivers we need to add #include <plat/cpu.h> for now until these drivers are fixed to remove cpu_is_omapxxxx() usage. While at it, sort som of the includes the standard way, and add the trailing commas where they are missing in the related data structures. Note that for drivers/staging/tidspbridge we just define things locally. Cc: Paul Walmsley <paul@pwsan.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 10 Sep, 2012 1 commit
-
-
Igor Grinberg authored
plat/board.h file is now empty - remove it. Cc: Jarkko Lavinen <jarkko.lavinen@nokia.com> Cc: Chris Ball <cjb@laptop.org> Cc: Kyungmin Park <kyungmin.park@samsung.com> Cc: linux-mmc@vger.kernel.org Cc: linux-mtd@lists.infradead.org Signed-off-by:
Igor Grinberg <grinberg@compulab.co.il> Acked-by:
Chris Ball <cjb@laptop.org> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 23 Aug, 2012 1 commit
-
-
Sudeep KarkadaNagesha authored
The arm_pmu_type enumeration was initially introduced to identify different PMU types in the system, the usual one being that on the CPU (ARM_PMU_DEVICE_CPU). With the removal of the PMU reservation code and the introduction of devicetree bindings for the CPU PMU, the enumeration is no longer required. This patch removes the enumeration and updates the various CPU PMU platform devices so that they no longer pass an .id field referring to identify the PMU type. Cc: Haojian Zhuang <haojian.zhuang@gmail.com> Cc: Olof Johansson <olof@lixom.net> Cc: Pawel Moll <pawel.moll@arm.com> Acked-by:
Jon Hunter <jon-hunter@ti.com> Acked-by:
Kukjin Kim <kgene.kim@samsung.com> Acked-by:
Linus Walleij <linus.walleij@linaro.org> Acked-by:
Jiandong Zheng <jdzheng@broadcom.com> Signed-off-by:
Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com> [will: cosmetic edits and actual removal of the enum type] Signed-off-by:
Will Deacon <will.deacon@arm.com>
-
- 09 Jul, 2012 2 commits
-
-
R Sricharan authored
The l3 interconnect ip is same for OMAP4 and OMAP5. So reuse the l3 error handler error code for OMAP5 as well. Also a few targets has been newly added for OMAP5. So updating the driver for that here. Signed-off-by:
R Sricharan <r.sricharan@ti.com> Signed-off-by:
Santosh Shilimkar <santosh.shilimkar@ti.com>
-
Xiao Jiang authored
If provided dt support, then skip add wdt platform device as usual. Signed-off-by:
Xiao Jiang <jgq516@gmail.com> Reviewed-by:
Jon Hunter <jon-hunter@ti.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 26 Jun, 2012 1 commit
-
-
Tony Lindgren authored
This allows us to pass dma request lines in platform data to MMC driver the same way as we already do for omap2430 and later. Also note that we need to only build this code if MMC_OMAP is selected, so change Makefile accordingly and place it near the MMC_OMAP_HS in the Makefile. Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 22 Jun, 2012 1 commit
-
-
Paul Walmsley authored
Convert the old-style device registration code for HDQ1W to use omap_device. This will allow the driver to be converted to use PM runtime and to take advantage of the OMAP IP block management infrastructure (hwmod, PM, etc.). A side benefit of this conversion is that it also makes the HDQ device available on OMAP2420. The previous code only enabled it on 2430 and 3430. Signed-off-by:
Paul Walmsley <paul@pwsan.com> Cc: NeilBrown <neilb@suse.de> Tested-by:
NeilBrown <neilb@suse.de>
-
- 09 May, 2012 2 commits
-
-
Tony Lindgren authored
This allows us to pass dma request lines in platform data to MMC driver the same way as we already do for omap2430 and later. Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
Ricardo Neri authored
Add platform registration for the devices HDMI audio support. The omap-hdmi-audio-dai platform device is to be used by the ASoC HDMI CPU DAI driver. The omap-hdmi-audio platform device is to be used by the ASoC HDMI machine driver that links together the ASOC CPU DAI, ASoC plaform and ASoC codec drivers. Signed-off-by:
Ricardo Neri <ricardo.neri@ti.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 08 May, 2012 1 commit
-
-
Peter Ujfalusi authored
If dtb is provided the needed device will be created dynamically. Signed-off-by:
Peter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-