On Wed, 2012-08-29 at 17:20 -0700, Tony Lindgren wrote:
* Chandrabhanu Mahapatra cmahapa...@ti.com [120820 06:26]:
Hi everyone,
this patch series aims at cleaning up of DSS of cpu_is checks thereby
making it
more generic.
The 1st patch cleans up cpu_is checks from DISPC code.
The
On Thursday 30 August 2012 05:38 AM, Russell King - ARM Linux wrote:
On Wed, Aug 29, 2012 at 02:26:15PM +0530, Rajendra Nayak wrote:
Moving to Common clk framework for OMAP would mean we no longer use
internal lookup mechanism like omap_clk_get_by_name().
get rid of all its usage mostly from
On Thursday 30 August 2012 05:45 AM, Turquette, Mike wrote:
On Wed, Aug 29, 2012 at 1:56 AM, Rajendra Nayakrna...@ti.com wrote:
diff --git a/arch/arm/mach-omap2/clock44xx_data.c
b/arch/arm/mach-omap2/clock44xx_data.c
index d7f55e4..a3831a2 100644
--- a/arch/arm/mach-omap2/clock44xx_data.c
+++
Hi Samuel, Linus,
On 08/16/2012 03:13 PM, Peter Ujfalusi wrote:
Hello,
Changes since v1:
- Removed the ti,use-gpo property from DT bindings
- Register the GPO driver if we booted with DT blob or in legacy if the pdata
for the GPO driver is present
- DT binding Documentation update
Hi Tero,
On 08/28/2012 12:50 PM, Tero Kristo wrote:
On Tue, 2012-08-14 at 17:22 +0300, Peter Ujfalusi wrote:
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
I think this one could use a short commit message, also about why
kfree():s are dropped (handled internally by devm_* etc.)
I
Added device tree support for nop transceiver driver and updated the
Documentation with device tree binding information for am33xx platform.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
---
.../devicetree/bindings/usb/am33xx-usb.txt |3
From: Ajay Kumar Gupta ajay.gu...@ti.com
Added device tree support for dsps musb glue driver and updated the
Documentation with device tree binding information.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
Signed-off-by: Santhapuri, Damodar
From: Ajay Kumar Gupta ajay.gu...@ti.com
Moved global variable musb_debugfs_root and static variable
old_state to 'struct musb' to help support multi instance of
musb controller as present on AM335x platform.
Also removed the global variable orig_dma_mask and filled the
dev-dma_mask with parent
From: Santhapuri, Damodar damodar.santhap...@ti.com
AM335x uses NOP transceiver driver and need to enable builtin PHY
by writing into usb_ctrl register available in system control
module register space. This is being added at musb glue driver
layer untill a separate system control module driver
This series of patches adds,
a) Multi instances support in musb driver
b) DT support for musb_dsps glue layer
c) DT support for NOP transceiver
AM33xx and TI81xx has dual musb controller and has two usb PHY of same type.
This patch series uses 'phandle' based API devm_usb_get_phy_by_phandle() to
AM335x and TI81xx platform has dual musb controller so updating the
musb_dspc.c to support the same.
Changes:
- Moved otg_workaround timer to glue structure
- Moved static local variable last_timer to glue structure
- PHY on/off related cleanups
Signed-off-by: Ajay Kumar
From: Ajay Kumar Gupta ajay.gu...@ti.com
Enabled the phy control logic for am335x also based on usbss
revision register.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Santhapuri, Damodar damodar.santhap...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
---
From: Ajay Kumar Gupta ajay.gu...@ti.com
Added device tree data for usbss on am33xx. There are two musb controllers
on am33xx platform so have port0_mode and port1_mode additional data.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
Signed-off-by:
From: Ajay Kumar Gupta ajay.gu...@ti.com
As NOP device node is now added in am33xx tree so remove the call
which creates the NOP platform_device.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
Signed-off-by: Santhapuri, Damodar
Added musb_ida in musb_core.c to manage the multi core ids.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
Signed-off-by: Santhapuri, Damodar damodar.santhap...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
---
drivers/usb/musb/am35x.c | 42
From: Santhapuri, Damodar damodar.santhap...@ti.com
AM33xx has two PHY of same type used by each musb controller so
use phandle of phy nodes to get the phy pointer.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
Signed-off-by: Santhapuri, Damodar
From: Ajay Kumar Gupta ajay.gu...@ti.com
AM33xx has two musb controller and they have one NOP PHY each.
Added the device tree data for NOP PHY.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
Signed-off-by: Santhapuri, Damodar damodar.santhap...@ti.com
From: Santhapuri, Damodar damodar.santhap...@ti.com
Currently we have one single nop transceiver support as same is
defined as a global variable in drivers/usb/otg/nop-usb-xceiv.c.
This need to be changed to support multiple otg controller each
using nop transceiver on a platform such as am335x.
From: Ajay Kumar Gupta ajay.gu...@ti.com
Added NOP PHY phandle to usbss device node as same will be used
to get the phy from otg framework.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Signed-off-by: Ravi Babu ravib...@ti.com
Signed-off-by: Santhapuri, Damodar damodar.santhap...@ti.com
Hello.
On 30-08-2012 14:50, Ravi Babu wrote:
From: Ajay Kumar Gupta ajay.gu...@ti.com
Added device tree data for usbss on am33xx. There are two musb controllers
on am33xx platform so have port0_mode and port1_mode additional data.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
Create a new entity in OMAPDSS called outputs. These represent the
interfaces/outputs like DSI, HDMI etc. that a panel connects to. An output
sits in between an overlay manager and a panel. More details about outputs
are explained in the first patch of the series.
This series adds omap_dss_output
The current OMAPDSS design contains 3 software entities: Overlays, Managers and
Devices. These map to pipelines, overlay managers and the panels respectively in
hardware. One or more overlays connect to a manager to represent a composition,
the manager connects to a device(generally a display) to
Add output structs to output driver's private data. Register output instances by
having an init function in the probes of the platform device drivers for
different outputs. The *_init_output for each output registers the output and
fill up the output's plaform device, type and id fields.
In the
An output entity represented by the struct omap_dss_output connects to a
omap_dss_device entity. Add functions to set or unset an output's device. This
is similar to how managers and devices were connected previously. An output can
connect to a device without being connected to a manager. However,
Add set_output/unset_output ops for overlay managers, these form links between
managers and outputs. Create a function in dss features which tell all the
output instances that connect to a manager, use it when a manager tries to set
an output. Add a constraint of not unsetting an output when the
With the introduction of output entities, managers will now connect to outputs.
Create a helper op for managers named get_device. This will abstract away the
information on how to get the device from an overlay manager. The get_device
op currently retrieves the output via a manager-device
With the introduction of output entities, managers will now connect to outputs.
Use the helper op for managers named get_device. This will abstract away the
information on how to get the device from an overlay manager.
Using the helper function will reduce the number of pointer dereferences a
With the introduction of output entities, managers will now connect to outputs.
Use the helper op for managers named get_device. This will abstract away the
information on how to get the device from an overlay manager.
Using the helper function will reduce the number of pointer dereferences a
With the introduction of output entities, managers will now connect to outputs.
Use the helper op for managers named get_device. This will abstract away the
information on how to get the device from an overlay manager.
Using the helper function will reduce the number of pointer dereferences a
Links between DSS entities are made in dss_recheck_connections when a new panel
is probed. Rewrite the code in dss_recheck_connections to link managers to
outputs, and outputs to devices.
The fields in omap_dss_device struct gives information on which output and
manager to connect to. The desired
When a panel driver calls a DPI function, it passes the omap_dss_device
pointer, this pointer currently propagates within the DPI driver to configure
the interface.
Extract the omap_dss_output pointer from omap_dss_device received from the panel
driver, pass the output pointer to DPI functions
dsi_pdev_map is a struct visible globally in the DSI driver to get the platform
device pointer of the DSI device corresponding to it's module ID. This was
required because there was no clean way to derive the platform device from
the DSI module instance number or from the connected panel.
With
When a panel driver calls a DSI function, it passes the omap_dss_device
pointer, this pointer currently propagates within the DSI driver to configure
the interface.
Extract the omap_dss_output pointer from omap_dss_device received from the panel
driver, pass the output pointer to DSI functions
When a panel driver calls a SDI function, it passes the omap_dss_device
pointer, this pointer currently propagates within the SDI driver to configure
the interface.
Extract the omap_dss_output pointer from omap_dss_device received from the panel
driver, pass the output pointer to SDI functions
When a panel driver calls a RFBI function, it passes the omap_dss_device
pointer, this pointer currently propagates within the RFBI driver to configure
the interface.
Extract the omap_dss_output pointer from omap_dss_device received from the panel
driver, pass the output pointer to RFBI functions
All functions of an interface driver used by a panel driver should have an
omap_dss_device pointer as an argument. This may not be needed by some of the
interfaces now as driver data is globally visible in them. The correct way
to retrieve driver data is to extract the platform device from the
When a panel driver calls a VENC function, it passes the omap_dss_device
pointer, this pointer currently propagates within the VENC driver to configure
the interface.
Extract the omap_dss_output pointer from omap_dss_device received from the panel
driver, pass the output pointer to VENC functions
When a panel driver calls a HDMI function, it passes the omap_dss_device
pointer, this pointer currently propagates within the HDMI driver to configure
the interface.
Extract the omap_dss_output pointer from omap_dss_device received from the panel
driver, pass the output pointer to HDMI functions
All functions of an output driver used by a panel driver should have an
omap_dss_device pointer as an argument. This is needed as the function would
somehow need to retrieve the output driver's private data. It may not be needed
by some of the outputs for now as driver data is globally visible
To retrieve the manager pointer via a device, we need to now access it via the
output to which the device is connected. Make this change in the places where
such a reference is made.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/display.c | 11 +--
The display sysfs attribute's store function needs to be changed with the
introduction of outputs.
Providing a manager to the display isn't enough to create a link now, the
manager needs and output to connect to. A manager's display store file only
has the information of the manager and the
A manager is not connected to a device directly any more. It first connects
to an output, and then to the display. Update the manager's get_device op to
return the device via the connected output.
Signed-off-by: Archit Taneja arc...@ti.com
---
drivers/video/omap2/dss/manager.c |2 +-
1 file
An overlay isn't allowed to be enabled/disabled if it isn't connected to an
omap_dss_device. This requirement isn't needed any more. An overlay can be
enabled/disabled as long as it has an output connected to it. The output may
not be connected to a device, but we can be assured that the connected
Now that an omap_dss_output can be used to link between managers and devices, we
can remove the old way of setting manager and device links. This involves
removing the device and manager pointers from omap_overlay_manager and
omap_dss_device respectively, and removing the set_device/unset_device
On 08/30/2012 10:39 AM, Rajendra Nayak wrote:
On Thursday 30 August 2012 05:45 AM, Turquette, Mike wrote:
On Wed, Aug 29, 2012 at 1:56 AM, Rajendra Nayakrna...@ti.com wrote:
diff --git a/arch/arm/mach-omap2/clock44xx_data.c
b/arch/arm/mach-omap2/clock44xx_data.c
index d7f55e4..a3831a2 100644
On Wed, Aug 29, 2012 at 12:34:23AM +0300, Aaro Koskinen wrote:
Add i2c driver to enable access to devices behind CBUS on Nokia Internet
Tablets.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Cc: linux-...@vger.kernel.org
Acked-by: Felipe Balbi ba...@ti.com
---
On Wed, Aug 29, 2012 at 12:34:24AM +0300, Aaro Koskinen wrote:
Retu is a multi-function device found on Nokia Internet Tablets
implementing at least watchdog, RTC, headset detection and power button
functionality.
This patch implements a minimum functionality providing only register
access
On Wed, Aug 29, 2012 at 12:34:26AM +0300, Aaro Koskinen wrote:
Add platform data to enable i2c-cbus on N8x0. It will be I2C bus #3.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Acked-by: Felipe Balbi ba...@ti.com
---
arch/arm/mach-omap2/board-n8x0.c | 27 +++
On Wed, Aug 29, 2012 at 12:34:27AM +0300, Aaro Koskinen wrote:
Add Retu configuration.
Signed-off-by: Aaro Koskinen aaro.koski...@iki.fi
Acked-by: Felipe Balbi ba...@ti.com
---
arch/arm/mach-omap2/board-n8x0.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff
Hi,
On Wed, Aug 29, 2012 at 12:34:22AM +0300, Aaro Koskinen wrote:
Hi,
I would like to start converting cbus drivers from linux-omap cbus branch
for mainline inclusion. Currently e.g. watchdog support is missing at
least on Nokia N800, so you cannot run the mainline kernel for longer
than
On Wed, 29 Aug 2012, Locke, Matthew wrote:
During lunch
On the schedule[1], the TI Linux BoF is from 12:35pm to 13:20pm. So it
looks like people can get a quick lunch outside from 12:05pm to 12:30pm,
then head to Nautilus 1 for the BoF.
It's all informal, so please drop in and say hello if
On Thu, 2012-08-30 at 13:57 +0200, Benoit Cousson wrote:
On 08/30/2012 10:39 AM, Rajendra Nayak wrote:
On Thursday 30 August 2012 05:45 AM, Turquette, Mike wrote:
On Wed, Aug 29, 2012 at 1:56 AM, Rajendra Nayakrna...@ti.com wrote:
diff --git a/arch/arm/mach-omap2/clock44xx_data.c
On Wed, Aug 29, 2012 at 09:31:31AM +0100, Lee Jones wrote:
On Tue, Aug 28, 2012 at 10:21:33AM -0700, Mark Brown wrote:
The regulator-name property is used to populate constrains-name. Are
you sure you still want them all removed?
Yes, of course. There's no way that a generic .dtsi used
Hi,
* Tomi Valkeinen tomi.valkei...@ti.com [120830 00:35]:
On Wed, 2012-08-29 at 17:20 -0700, Tony Lindgren wrote:
Good to see this, we need this badly to avoid blocking
single zImage effort on omaps. Can you also please take
What is the issue with single zImage? How do cpu_is_ check
Although this kind of IR diode circuitry is known to exist only in
N900 hardware, nothing prevents making similar circuitry on any OMAP
based board. The MACH_NOKIA_RX51 dependency is thus not something we
want to be there.
Also, this should depend on LIRC as it is a LIRC driver.
Signed-off-by:
As clearly visible from the patch, this variable has no useful purpose
what so ever. Thus, it can be removed altogether without any side
effects.
Signed-off-by: Timo Kokkonen timo.t.kokko...@iki.fi
---
drivers/media/rc/ir-rx51.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff
Convert the driver from the obsolete omap_pm_set_max_mpu_wakeup_lat
API to the new PM QoS API. This allows the callback to be removed from
the platform data structure.
The latency requirements are also adjusted to prevent the MPU from
going into sleep mode. This is needed as the GP timers have no
The lirc-dev expects the ir-code to be transmitted when the write call
returns back to the user space. We should not leave TX ongoing no
matter what is the reason we return to the user space. Easiest
solution for that is to simply remove interruptible sleeps.
The first wait_event_interruptible is
This trivial fix cures the following warning message:
drivers/media/rc/Kconfig:275:warning: multi-line strings not supported
Signed-off-by: Timo Kokkonen timo.t.kokko...@iki.fi
---
drivers/media/rc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
No reason to avoid using the existing helpers.
Signed-off-by: Timo Kokkonen timo.t.kokko...@iki.fi
---
drivers/media/rc/ir-rx51.c | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/drivers/media/rc/ir-rx51.c b/drivers/media/rc/ir-rx51.c
index 16b3c1f..6e1ffa6 100644
-Fix typo
-Change pwm_timer_num type to match type in platform data
-Remove extra parenthesis
-Replace magic constant with proper bit defintions
-Remove duplicate exit pointer
Signed-off-by: Timo Kokkonen timo.t.kokko...@iki.fi
---
drivers/media/rc/Kconfig | 2 +-
This driver is useless without proper platform data. If data is not
available, we should not register the driver at all. Once this check
is done, the BUG_ON check during device open is no longer needed.
Signed-off-by: Timo Kokkonen timo.t.kokko...@iki.fi
---
drivers/media/rc/ir-rx51.c | 4 +++-
Remove a redundant macro definition. This is unneeded and becomes more
readable once the actual timer code is refactored a little.
Signed-off-by: Timo Kokkonen timo.t.kokko...@iki.fi
---
drivers/media/rc/ir-rx51.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git
These patches fix most of the issues pointed out in the patch review
by Sean Young and Sakari Ailus.
The most noticeable change after these patch set is that the IR
transmission no longer times out even if the timers are not waking up
the MPU as it should be. Now that Jean Pihet kindly instructed
These set of patches make possible the remoteproc recover after a crash.
This is a hard recovery, that means the remoteproc is reset and it will
start from the beginning. When a crash happen all the virtio devices are
destroyed. Therefore, both rpmsg drivers and devices are gracefully
removed
Add a debugfs entry (named recovery) so that recovery can be disabled
dynamically at runtime. This entry is very useful when you are trying to
debug a rproc crash. Without this a recovery will take place making
impossible to debug the issue.
Original idea from Ohad Ben-Cohen and contributions
This patch is exporting the rproc_report_crash function which can be used
to report a rproc crash to the remoteproc core. This function is specially
thought to be called by low-level remoteproc driver code in case of
detecting a crash (remoteproc is not functional anymore). Using this
function
This patch is introducing rproc_trigger_recover function which is in
charge of recovering the rproc. One way to recover the rproc after a crash
is resetting all its virtio devices. Doing that, all rpmsg drivers are
restored along with the rpmsg devices and that also causes the reset of
the
* Igor Grinberg grinb...@compulab.co.il [120828 16:19]:
This patch series cleans up the plat/board.h and related files.
Great, thanks for doing this! Nice that we can finally remove
all of that. I've also tested that 770 boots after this, so
looks like we've already fixed up whatever it was
* Artem Bityutskiy dedeki...@gmail.com [120825 04:49]:
On Tue, 2012-08-21 at 15:14 +0530, Afzal Mohammed wrote:
GPMC platform initialization provides it's clients
with interrupts that can be used through struct
resource. Make use of it for irq mode functionality.
Also now write protect
* Jon Hunter jon-hun...@ti.com [120816 08:05]:
On 08/15/2012 04:11 AM, Vaibhav Hiremath wrote:
Did we get conclude on this? I haven't got anything further on this
thread, this may block baseport support for the new devices in omap2
family, like AM33xx and OMAP5.
Sorry I have been out
* Igor Grinberg grinb...@compulab.co.il [120829 15:02]:
On 08/28/12 01:43, Shilimkar, Santosh wrote:
On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg grinb...@compulab.co.il
wrote:
Currently, omap2_sync32k_clocksource_init() function initializes the 32K
timer as the system clock source
* Paul Walmsley p...@pwsan.com [120827 16:39]:
This series converts the OMAP hardware random number generator driver
to use runtime PM. Hardware integration data is added for OMAP2xxx
systems. I'm pretty sure this device is available on other OMAP chips
too, but may require some
On Thu, Aug 30, 2012 at 01:27:08PM -0700, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [120827 16:39]:
This series converts the OMAP hardware random number generator driver
to use runtime PM. Hardware integration data is added for OMAP2xxx
systems. I'm pretty sure this device is
* AnilKumar Ch anilku...@ti.com [120828 01:11]:
Adds basic pinctrl device tree data for AM33XX family of devices.
This patch is based on the pinctrl-single driver.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi |9 +
1 file changed, 9
* AnilKumar Ch anilku...@ti.com [120828 01:11]:
Adds GPIO pinctrl nodes to am3358_pinmux master node to control
user leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
arch/arm/boot/dts/am335x-bone.dts | 14 ++
1 file
* AnilKumar Ch anilku...@ti.com [120828 01:11]:
Add Bosch D_CAN controller device tree data to AM33XX dtsi
file by adding d_can device nodes with all the necessary
parameters.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 18 ++
1 file
* Shilimkar, Santosh santosh.shilim...@ti.com [120829 08:30]:
On Wed, Aug 29, 2012 at 8:24 AM, Aaro Koskinen aaro.koski...@iki.fi wrote:
In some OMAP3 HS devices (at least Nokia N9 and N950), the public SRAM
seems to conflict with secure portition of SRAM. When booting the 3.6-rc3
kernel
* Rajendra Nayak rna...@ti.com [120827 23:22]:
Hi Tony,
* Rajendra Nayakrna...@ti.com [120730 06:17]:
regulators do not have a 'reg' property, hence the regulator@0,
regulator@1 do not make sense. get rid of it.
Looks like this needs to be refreshed to apply. Care to
refresh against
* Radek Pilar mr...@mrkva.eu [120817 09:04]:
Fix inconsistency between mach-types and CONFIG_ name that prevents touchbook
board from booting.
Thanks, applying into fixes.
Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
Hi Rajendra
On Wed, 29 Aug 2012, Rajendra Nayak wrote:
Changes in v4:
* Added *hack* comments around clk_prepare usage in hwmod
rebased on 3.6-rc
Assuming this is so (haven't looked closely at this series yet), and after
the existing comments are taken into consideration and a new version
On Thu, 30 Aug 2012, Herbert Xu wrote:
Acked-by: Herbert Xu herb...@gondor.apana.org.au
Great, thanks Herbert.
At some point in the next month or so, there should be similar series for
the OMAP crypto IP blocks too, which will need some acks - just as a
heads-up.
- Paul
--
To unsubscribe
* Mark Brown broo...@opensource.wolfsonmicro.com [120821 06:58]:
On Tue, Aug 21, 2012 at 04:47:26PM +0530, AnilKumar Ch wrote:
This patch series add AM33XX regulators (tps65910/tps65217) device
tree data to am335x-evm and am335x-bone dts files. These patches
are based on Tony L devel-dt
On 08/30/12 23:20, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [120829 15:02]:
On 08/28/12 01:43, Shilimkar, Santosh wrote:
On Mon, Aug 27, 2012 at 3:26 PM, Igor Grinberg grinb...@compulab.co.il
wrote:
Currently, omap2_sync32k_clocksource_init() function initializes the 32K
Hi all,
Here's the first set of omap header clean-up patches needed for single
zImage support. This series is based v3.6-rc3 and the following patches
to avoid merge conflicts with the includes:
- Arnd's patch ARM: omap: move platform_data definitions
- Igor's series ARM: OMAP: cleanup
This is needed to start removing hardcoded IRQs on omap2+.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/plat-omap/include/plat/dma.h |2 ++
arch/arm/plat-omap/include/plat/irqs.h |1 -
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
This is needed to start removing hardcoded IRQs for omap2+.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/plat-omap/i2c.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/plat-omap/i2c.c b/arch/arm/plat-omap/i2c.c
index db071bc..40bc06a 100644
---
Make INTCPS_NR_IRQS local for mach-omap2/irq.c
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/irq.c |2 ++
arch/arm/plat-omap/include/plat/irqs.h |3 ---
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/irq.c
This is no longer needed and assumes a fixed IRQ number
that won't work with SPARSE_IRQ.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/board-flash.c|1 -
include/linux/platform_data/mtd-nand-omap2.h |1 -
2 files changed, 2 deletions(-)
diff --git
We can't use hardcoded interrupts for SPARSE_IRQ, and can replace
the hardcoded gpio_base with twl_gpiochip.base after it's been
allocated.
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Linus Walleij linus.wall...@linaro.org
Cc: Samuel Ortiz sa...@linux.intel.com
Cc: Peter Ujfalusi
This way we can remove includes of plat/gpio.h which won't work
with the single zImage support.
Note that we also remove the cpu_class_is_omap2() check
in gpio-omap.c as the drivers should not call it as we need to
make it local to arch/arm/mach-omap2 for single zImage support.
While at it,
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. While at it, sort
the
This is now omap1 specific files.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap1/ams-delta-fiq-handler.S |1
arch/arm/mach-omap1/dma.c|3
arch/arm/mach-omap1/include/mach/ams-delta-fiq.h |2
On 8/31/2012 2:26 AM, Paul Walmsley wrote:
Hi Rajendra
On Wed, 29 Aug 2012, Rajendra Nayak wrote:
Changes in v4:
* Added *hack* comments around clk_prepare usage in hwmod
rebased on 3.6-rc
Assuming this is so (haven't looked closely at this series yet), and after
the existing
On 08/30/2012 07:52 PM, Tony Lindgren wrote:
Hi all,
Here's the first set of omap header clean-up patches needed for single
zImage support. This series is based v3.6-rc3 and the following patches
to avoid merge conflicts with the includes:
- Arnd's patch ARM: omap: move platform_data
95 matches
Mail list logo
