Hi Mark,
On Fri, Sep 27, 2013 at 05:06:38PM +0100, Kumar Gala wrote:
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes
controlled, and it is disabled out of
reset. Make sure the module is enabled and clocked before reading
the SYSSTATUS register.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/hwspinlock/omap_hwspinlock.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/drivers
Add the hwspinlock device tree node for OMAP4 family
of SoCs.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 45708e1..74db751 100644
--- a/arch
Add the hwspinlock device tree node for OMAP5 SoCs.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 86295d2..2a98a59 100644
--- a/arch/arm/boot/dts
, and to request a specific lock using
the phandle + args specifier. The latter function is different
from the existing non-DT function, in that the specifier is
relative to the hwlock device instead of being a global lock id
registered with the core.
Signed-off-by: Suman Anna s-a...@ti.com
Add the hwspinlock device tree node for AM33xx family
of SoCs.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 8692490..49dfb86 100644
to OMAP hwspinlock driver
- Add OMAP4 DT node and bindings information
http://marc.info/?l=linux-omapm=137823082308009w=2
[1] https://lkml.org/lkml/2013/8/14/528
[2] http://marc.info/?t=13782309035r=1w=2
Suman Anna (8):
hwspinlock/core: maintain a list of registered hwspinlock banks
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing with the traditional platform device instantiation.
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree
AM33XX device family also supports hwspinlocks. The IP
is identical to that of OMAP4/OMAP5, except for the
number of locks.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/hwspinlock/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwspinlock/Kconfig b
and a specific lock belonging to the device
requested through a phandle + args approach.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/hwspinlock/hwspinlock_core.c | 48
drivers/hwspinlock/hwspinlock_internal.h | 2 ++
2 files changed, 50 insertions(+)
diff --git
On 10/09/2013 02:12 AM, Paul Walmsley wrote:
On Tue, 17 Sep 2013, Suman Anna wrote:
Add the hwmod data for the spinlock IP in OMAP5 SoC.
This is needed to be able to enable the OMAP spinlock
support for OMAP5.
Signed-off-by: Suman Anna s-a...@ti.com
Thanks, queued. You can omit
Hi Paul,
On 10/09/2013 12:35 AM, Paul Walmsley wrote:
Hi
On Thu, 3 Oct 2013, Suman Anna wrote:
The hwmod init sequence involves initializing and idling all the
hwmods during bootup. If a module class has sysconfig, the init
sequence utilizes the module register base for performing any
Tony,
On 10/08/2013 01:09 PM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [131003 10:07]:
The hwmod init sequence involves initializing and idling all the
hwmods during bootup. If a module class has sysconfig, the init
sequence utilizes the module register base for performing any
sysc
On 10/07/2013 04:19 PM, Nishanth Menon wrote:
On 10/03/2013 11:59 AM, Suman Anna wrote:
The hwmod init sequence involves initializing and idling all the
hwmods during bootup. If a module class has sysconfig, the init
sequence utilizes the module register base for performing any
sysc
dereference and a kernel boot hang.
Handle this scenario by checking for a valid module address space
during the _init of each hwmod, and leaving it in the registered
state if no module register address base is defined in either of
the hwmod data or the DT data.
Signed-off-by: Suman Anna s
Tony,
On 10/03/2013 01:05 PM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [130903 11:00]:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing
Hi Mark,
On Fri, Sep 27, 2013 at 05:06:38PM +0100, Kumar Gala wrote:
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes
, at 2:30 PM, Suman Anna wrote:
All the platform-specific hwlock driver implementations need the
number of locks and the associated base id for registering the
locks present within a hwspinlock device with the driver core.
These two variables are represented by 'hwlock-num-locks' and
'hwlock
On 09/29/2013 10:12 PM, Paul Walmsley wrote:
Hi
On Fri, 27 Sep 2013, Suman Anna wrote:
Paul,
The hwmod data patches needs to be merged only after the respective DT
node patches are merged, without which the hwmod entry will not have a
base address while enabling and idling (using sysc
On 09/17/2013 02:30 PM, Suman Anna wrote:
Hi,
This is an updated series for adding the device tree support to
the OMAP hwspinlock driver. The series is based on 3.12-rc1, and
includes patches on hwspinlock driver, OMAP hwmod data files and
OMAP DTS files. The updated series adds new patches
On 09/27/2013 11:06 AM, Kumar Gala wrote:
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing
Kumar,
On 09/27/2013 11:04 AM, Kumar Gala wrote:
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
All the platform-specific hwlock driver implementations need the
number of locks and the associated base id for registering the
locks present within a hwspinlock device with the driver core
Kumar,
On 09/27/2013 11:04 AM, Kumar Gala wrote:
On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
All the platform-specific hwlock driver implementations need the
number of locks and the associated base id for registering the
locks present within a hwspinlock device with the driver core
Hi Paul,
Hi,
I have an OMAP5432 uEVM which I cannot get to boot with recent mainline
(tried 3.11 and 3.12-rc1). I have the TI GLSDK for this board
(v6.0.0.7),
which comes with 3.8.4 which works fine.
I found this thread: http://marc.info/?l=fedora-armm=137717811815777
and
Wrong
On 09/26/2013 06:44 PM, Paul Zimmerman wrote:
From: Suman Anna [mailto:s-a...@ti.com]
Sent: Thursday, September 26, 2013 1:36 PM
I have an OMAP5432 uEVM which I cannot get to boot with recent
mainline
(tried 3.11 and 3.12-rc1). I have the TI GLSDK for this board
(v6.0.0.7),
which comes
Santosh,
On 09/24/2013 06:55 PM, Santosh Shilimkar wrote:
On Tuesday 24 September 2013 07:48 PM, Suman Anna wrote:
On 09/24/2013 05:24 PM, Santosh Shilimkar wrote:
On Tuesday 24 September 2013 04:30 PM, Paul Zimmerman wrote:
From: Paul Zimmerman
Sent: Tuesday, September 24, 2013 1:21 PM
Hi
Paul,
On 09/25/2013 10:02 AM, Santosh Shilimkar wrote:
On Tuesday 24 September 2013 07:59 PM, Paul Zimmerman wrote:
From: Suman Anna [mailto:s-a...@ti.com]
Sent: Tuesday, September 24, 2013 4:48 PM
On 09/24/2013 05:24 PM, Santosh Shilimkar wrote:
On Tuesday 24 September 2013 04:30 PM, Paul
On 09/24/2013 05:24 PM, Santosh Shilimkar wrote:
On Tuesday 24 September 2013 04:30 PM, Paul Zimmerman wrote:
From: Paul Zimmerman
Sent: Tuesday, September 24, 2013 1:21 PM
Hi,
I have an OMAP5432 uEVM which I cannot get to boot with recent mainline
(tried 3.11 and 3.12-rc1). I have the TI
(Patch 3)
v1:
- Add DT parse support to OMAP hwspinlock driver
- Add OMAP4 DT node and bindings information
http://marc.info/?l=linux-omapm=137823082308009w=2
[1] https://lkml.org/lkml/2013/8/14/528
[2] http://marc.info/?t=13782309035r=1w=2
Suman Anna (9):
hwspinlock/core: add common dt
. The documentation and OF helpers to
retrieve these common properties have been added to the driver core.
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree/bindings/hwlock/hwlock.txt | 26 +
drivers/hwspinlock/hwspinlock_core.c | 61 +-
include/linux
AM33XX device family also supports hwspinlocks. The IP
is identical to that of OMAP4/OMAP5, except for the
number of locks.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/hwspinlock/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwspinlock/Kconfig b
controlled, and it is disabled out of
reset. Make sure the module is enabled and clocked before reading
the SYSSTATUS register.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/hwspinlock/omap_hwspinlock.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/drivers
Add the hwspinlock device tree node for OMAP4 family
of SoCs.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 22d9f2b..a8cc274 100644
--- a/arch
Add the missing sysc configuration to the AM335 spinlock hwmod
data. This ensures that smart-idle is enabled whenever the module
is enabled by the driver.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 13 +
1 file changed, 13 insertions
Add the hwspinlock device tree node for AM33xx family
of SoCs.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index f9c5da9..4371257 100644
Add the hwspinlock device tree node for OMAP5 SoCs.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 07be2cd..449be92 100644
--- a/arch/arm/boot/dts
Add the hwmod data for the spinlock IP in OMAP5 SoC.
This is needed to be able to enable the OMAP spinlock
support for OMAP5.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 44 ++
1 file changed, 44 insertions(+)
diff --git
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing with the traditional platform device instantiation.
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree
Hi Benoit,
On 08/08/2013 17:44, Suman Anna wrote:
On 08/08/2013 09:34 AM, Kumar Gala wrote:
On Aug 7, 2013, at 3:08 PM, Suman Anna wrote:
On 08/07/2013 12:41 PM, Kumar Gala wrote:
On Aug 7, 2013, at 11:59 AM, Suman Anna wrote:
Kumar,
Logic has been added to the OMAP2+ mailbox code
Kevin,
Sorry, I couldn't get back earlier due to long weekend.
On 08/29/2013 11:57 AM, Kevin Hilman wrote:
Suman Anna s-a...@ti.com writes:
[...]
Yeah, the wkupm3 mbox usage is actually odd (an unfortunate result of
the way the hardware is designed)
heh, design is a generous term
Kumar,
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing with the traditional platform device instantiation.
Signed-off-by: Suman Anna s-a...@ti.com
On 09/04/2013 03:09 AM, Stanimir Varbanov wrote:
Hi Suman,
Thanks for the patch.
On 09/03/2013 08:52 PM, Suman Anna wrote:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing with the traditional platform device instantiation.
Signed-off-by: Suman Anna s-a...@ti.com
On 09/04/2013 12:51 PM, Kumar Gala wrote:
On Sep 4, 2013, at 12:03 PM, Suman Anna wrote:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing
Kevin,
Sorry, I couldn't get back earlier due to long weekend.
On 08/29/2013 11:57 AM, Kevin Hilman wrote:
Suman Anna s-a...@ti.com writes:
[...]
Yeah, the wkupm3 mbox usage is actually odd (an unfortunate result of
the way the hardware is designed)
heh, design is a generous term
from the MSM HW Mutex driver support series
in [1]).
[1] https://lkml.org/lkml/2013/8/14/528
Suman Anna (2):
hwspinlock/omap: add support for dt nodes
ARM: dts: OMAP4: Add hwspinlock node
.../devicetree/bindings/hwlock/omap-hwspinlock.txt | 28 ++
arch/arm/boot/dts/omap4.dtsi
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing with the traditional platform device instantiation.
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree
Add the hwspinlock device tree node for OMAP4 family
of SoCs.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 22d9f2b..a8cc274 100644
--- a/arch
Kumar,
On 09/03/2013 01:50 PM, Kumar Gala wrote:
On Sep 3, 2013, at 12:52 PM, Suman Anna wrote:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing
Kumar,
On 09/03/2013 01:50 PM, Kumar Gala wrote:
On Sep 3, 2013, at 12:52 PM, Suman Anna wrote:
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
base support for parsing the DT nodes, and removes the code
dealing
Kevin,
On 08/27/2013 04:25 PM, Kevin Hilman wrote:
Suman Anna s-a...@ti.com writes:
Kevin,
On 08/26/2013 10:50 PM, Kevin Hilman wrote:
Suman Anna s-a...@ti.com writes:
The WkupM3 mailbox used for triggering PM operations such as suspend
and resume on AM33x/AM43x is special
Kevin,
On 08/26/2013 10:50 PM, Kevin Hilman wrote:
Suman Anna s-a...@ti.com writes:
The WkupM3 mailbox used for triggering PM operations such as suspend
and resume on AM33x/AM43x is special in that the M3 processor cannot
access the mailbox registers. However, an interrupt is needed
.
Signed-off-by: Jingoo Han jg1@samsung.com
Acked-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap2.c |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mailbox/mailbox-omap2.c b/drivers/mailbox/mailbox-omap2.c
index eba380d..42d2b89 100644
--- a/drivers/mailbox
Tony, Benoit,
This is an updated series for adding the device tree support to
the OMAP mailbox driver. The series is based on 3.11-rc4 and now
includes the support for AM335 WkupM3 mailbox.
The support for WkupM3 mailbox is essential for achieving the PM
Suspend on AM335 devices, and this
Paul,
On 08/20/2013 06:39 PM, Paul Walmsley wrote:
Hi
a few comments
On Wed, 14 Aug 2013, Suman Anna wrote:
The remoteproc infrastructure is currently tied closely with the
virtio/rpmsg framework, and the boot requires that there are virtio
devices present in the resource table from
Kevin, Santosh, Dave, Russ,
On 08/13/2013 02:11 PM, Kevin Hilman wrote:
Russ Dill russ.d...@gmail.com writes:
ARM world is also moving towards that by standardizing some of these
through (read PSCI) and thats the way to go in general.
Agreed, but I'm not sure (yet) about enforcing PSCI on
On 08/08/2013 09:34 AM, Kumar Gala wrote:
On Aug 7, 2013, at 3:08 PM, Suman Anna wrote:
On 08/07/2013 12:41 PM, Kumar Gala wrote:
On Aug 7, 2013, at 11:59 AM, Suman Anna wrote:
Kumar,
Logic has been added to the OMAP2+ mailbox code to
parse the mailbox dt nodes and construct
type configuration information.
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree/bindings/mailbox/omap-mailbox.txt | 43 +++
drivers/mailbox/mailbox-omap2.c| 130
++---
2 files changed, 158 insertions(+), 15 deletions(-)
create mode 100644
On 08/07/2013 12:41 PM, Kumar Gala wrote:
On Aug 7, 2013, at 11:59 AM, Suman Anna wrote:
Kumar,
Logic has been added to the OMAP2+ mailbox code to
parse the mailbox dt nodes and construct the different
mailboxes associated with the instance. The design is
based on gathering the same
://marc.info/?l=linux-omapm=137452880325361w=2
v1:
http://marc.info/?l=linux-omapm=137159523405468w=2
[1] http://marc.info/?l=linux-omapm=137581142013093w=2
Suman Anna (8):
mailbox/omap: add a parent structure common to all mboxes
mailbox/omap: add support for parsing dt devices
ARM: dts: OMAP2+: Add
configuration information.
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree/bindings/mailbox/omap-mailbox.txt | 43 +++
drivers/mailbox/mailbox-omap2.c| 130 ++---
2 files changed, 158 insertions(+), 15 deletions(-)
create mode 100644 Documentation
of single global configuration variables for all h/w
instances.
Reviewed-by: Russ Dill russ.d...@ti.com
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap1.c | 27 +---
drivers/mailbox/mailbox-omap2.c | 95 +
drivers/mailbox/omap
Add the hwmod data for the mailbox IP in OMAP5 SoC.
This is needed to be able to enable the OMAP mailbox
support for OMAP5.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 42 ++
1 file changed, 42 insertions(+)
diff --git
The mailbox DT node data has been added for OMAP2420,
OMAP2430, OMAP3430/OMAP3630, OMAP44xx devices. Data
for OMAP5 and other SoCs will be added separately.
The mailbox static device initialization logic is also
adjusted for a DT boot.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot
The type definition omap_mbox_type_t used for distinguishing
OMAP1 from OMAP2+ mailboxes does not really belong to the
ops, and has been cleaned up.
Signed-off-by: Loic Pallardy loic.palla...@st.com
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap1.c | 27
spurious interrupts to
the M3.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap2.c | 87 -
1 file changed, 86 insertions(+), 1 deletion(-)
diff --git a/drivers/mailbox/mailbox-omap2.c b/drivers/mailbox/mailbox-omap2.c
index fef18f4
the code.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 38b446b..413dfa56 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot
Add the mailbox device DT node for OMAP5 SoC.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index e643620..a08f1ca 100644
--- a/arch/arm/boot
The mailbox DT node data has been added for OMAP2420,
OMAP2430, OMAP3430/OMAP3630, OMAP44xx devices. Data
for OMAP5 and other SoCs will be added separately.
The mailbox static device initialization logic is also
adjusted for a DT boot.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot
data
- Includes 2 new patches that adds the data for OMAP5.
v1:
http://marc.info/?l=linux-omapm=137159523405468w=2
Suman Anna (5):
mailbox/omap: add a parent structure common to all mboxes
mailbox/omap: add support for parsing dt devices
ARM: dts: OMAP2+: Add mailbox nodes
ARM: OMAP5: hwmod
Add the hwmod data for the mailbox IP in OMAP5 SoC.
This is needed to be able to enable the OMAP mailbox
support for OMAP5.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 42 ++
1 file changed, 42 insertions(+)
diff --git
of single global configuration variables for all h/w
instances.
Reviewed-by: Russ Dill russ.d...@ti.com
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap1.c | 27 +---
drivers/mailbox/mailbox-omap2.c | 95 +
drivers/mailbox/omap
configuration information.
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree/bindings/mailbox/omap-mailbox.txt | 43 +++
drivers/mailbox/mailbox-omap2.c| 130 ++---
2 files changed, 158 insertions(+), 15 deletions(-)
create mode 100644 Documentation
Add the mailbox device DT node for OMAP5 SoC.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index e643620..a08f1ca 100644
--- a/arch/arm/boot
On 07/15/2013 05:01 AM, Rajendra Nayak wrote:
On Monday 15 July 2013 12:14 PM, Rajendra Nayak wrote:
On Friday 12 July 2013 06:10 AM, Suman Anna wrote:
On 07/11/2013 04:59 AM, Grygorii Strashko wrote:
Hi,
On 07/11/2013 09:32 AM, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [130710 09:18
On 07/11/2013 04:59 AM, Grygorii Strashko wrote:
Hi,
On 07/11/2013 09:32 AM, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [130710 09:18]:
On Wed, Jul 10, 2013 at 07:07:04PM +0300, Felipe Balbi wrote:
how about something like below ? It makes omap_device/hwmod and
pm_runtime agree on
Barry,
On Mon, Jul 8, 2013 at 10:31 AM, Barry Song 21cn...@gmail.com wrote:
hi Ohad/all,
i am trying to find some real users of rpmsg, here i only get
samples/rpmsg/rpmsg_client_sample.c, does it mean other real drivers
are out of mainline?
Yes
where could i get them?
TI maintains
Hi Benoit,
On 06/20/2013 04:45 PM, Cousson, Benoit wrote:
Hi Suman,
On 6/18/2013 5:34 PM, Suman Anna wrote:
Logic has been added to the OMAP2+ mailbox code to
parse the mailbox dt nodes and construct the different
mailboxes associated with the instance. The design is
based on gathering
Hi Benoit,
On 06/20/2013 04:57 PM, Cousson, Benoit wrote:
On 6/18/2013 5:35 PM, Suman Anna wrote:
The mailbox DT node data has been added for OMAP2420,
OMAP2430, OMAP3430/OMAP3630, OMAP44xx devices. Data for
OMAP5 is skipped for now since the corresponding hwmod
entry is not present
configuration information.
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree/bindings/mailbox/omap-mailbox.txt | 46 +++
drivers/mailbox/mailbox-omap2.c| 141 ++---
2 files changed, 172 insertions(+), 15 deletions(-)
create mode 100644 Documentation
/linux-omap-dt.git/log/?h=for_3.11/dts
Suman Anna (3):
mailbox/omap: add a parent structure common to all mboxes
mailbox/omap: add support for parsing dt devices
ARM: dts: OMAP2+: Add mailbox nodes
.../devicetree/bindings/mailbox/omap-mailbox.txt | 46 +
arch/arm/boot/dts/omap2420
of single global configuration variables for all h/w
instances.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap1.c | 27 +---
drivers/mailbox/mailbox-omap2.c | 95 +
drivers/mailbox/omap-mailbox.c | 32 ++
drivers
The mailbox DT node data has been added for OMAP2420,
OMAP2430, OMAP3430/OMAP3630, OMAP44xx devices. Data for
OMAP5 is skipped for now since the corresponding hwmod
entry is not present.
The mailbox static device initialization logic is also
adjusted for a DT boot.
Signed-off-by: Suman Anna s
driver needs.
regards
Suman
On Thu, Jun 13, 2013 at 11:59 PM, Suman Anna s-a...@ti.com
mailto:s-a...@ti.com wrote:
Tan,
On 06/13/2013 06:01 AM, LF.Tan wrote:
Hi
I would like to add a new mailbox driver with this mailbox framework.
May I know this mailbox
On 06/12/2013 08:37 PM, Felipe Balbi wrote:
Hi,
On Wed, Jun 12, 2013 at 04:58:26PM -0500, Suman Anna wrote:
The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10:
Linux 3.10-rc5 (2013-06-08 17:41:04 -0700)
are available in the git repository at:
g
Linus Walleij wrote:
On Fri, May 3, 2013 at 3:25 PM, Arnd Bergmann a...@arndb.de
mailto:a...@arndb.de wrote:
On Thursday 02 May 2013 17:09:07 Suman Anna wrote:
I do not know how much of an impact it is for the ST driver as the
series adds the driver, and would have to wait until the RFC
device data through platform data/hwmod attrs
- move the omap mailbox code out of plat-omap/mach-omapX to
drivers/mailbox folder.
Suman Anna (6):
omap: mailbox: check iomem resource before dereferencing it
omap: mailbox
Add a NULL check for iomem resource in mailbox probe functions.
Signed-off-by: Fernando Guzman Lugo lugo.ferna...@gmail.com
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap1/mailbox.c | 3 +++
arch/arm/mach-omap2/mailbox.c | 3 +++
2 files changed, 6 insertions(+)
diff --git
,
and the move enables the driver to be built again and be functional.
These also serve as the base preparatory patches for adapting the
OMAP mailbox code to the upcoming mailbox framework, and for
device-tree conversion.
http://marc.info/?l=linux-omapm=137065697924665w=2
Suman Anna (6):
omap: mailbox
registers, and so
has been added to the platform data.
This data together with the interrupt-type configuration can be
used in properly figuring out the number of registers to save
and restore in the OMAP mailbox driver code.
Cc: Paul Walmsley p...@pwsan.com
Signed-off-by: Suman Anna s-a...@ti.com
is changed as
mailbox_omap1.ko for OMAP1
mailbox_omap2.ko for OMAP2+
Cc: Tony Lindgren t...@atomide.com
[gre...@linuxfoundation.org: ack for staging part]
Acked-by: Greg Kroah-Hartman gre...@linuxfoundation.org
Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com
Signed-off-by: Suman Anna s
The argument type used in the actual individual omap_mbox_ops
for irqs should be omap_mbox_irq_t instead of omap_mbox_type_t.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap1/mailbox.c | 6 +++---
arch/arm/mach-omap2/mailbox.c | 15 ---
2 files changed, 7 insertions
The OMAP mailbox startup code is enabling the interrupt before any
of the associated mailbox queues are allocated. Move this code so
that the interrupt configuration for a mailbox is together.
Signed-off-by: Fernando Guzman Lugo lugo.ferna...@gmail.com
Signed-off-by: Suman Anna s-a...@ti.com
driver. This data is now represented in a concise format
and moved to the respective omap_hwmod data files and published
to the driver through the platform data.
Cc: Paul Walmsley p...@pwsan.com
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/devices.c | 9 +-
arch/arm
Russ,
On 06/08/2013 02:16 PM, Russ Dill wrote:
On Fri, Jun 7, 2013 at 6:58 PM, Suman Anna s-a...@ti.com wrote:
The OMAP mailbox platform driver code has been cleaned up to
remove the dependencies with soc.h in preparation for moving
the mailbox code to drivers folder.
The code relied
Russ,
On 06/08/2013 01:46 PM, Russ Dill wrote:
On Fri, Jun 7, 2013 at 6:57 PM, Suman Anna s-a...@ti.com wrote:
The mailbox_put function must check the notifier block for
NULL before trying to unregister it.
I'm going to nack this one. Why must it check for NULL? None of the
callers pass
Russ,
On 06/08/2013 01:53 PM, Russ Dill wrote:
On Fri, Jun 7, 2013 at 6:57 PM, Suman Anna s-a...@ti.com wrote:
The OMAP mailbox startup code is enabling the interrupt even before
any of the associated mailbox queues are allocated. Any pending
received mailbox message could cause a kernel
The mailbox_put function must check the notifier block for
NULL before trying to unregister it.
Signed-off-by: Fernando Guzman Lugo lugo.ferna...@gmail.com
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/plat-omap/mailbox.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
.
Signed-off-by: Fernando Guzman Lugo lugo.ferna...@gmail.com
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/plat-omap/mailbox.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/arch/arm/plat-omap/mailbox.c b/arch/arm/plat-omap/mailbox.c
index 5fb4027..e1bd333
is changed as
mailbox_omap1.ko for OMAP1
mailbox_omap2.ko for OMAP2+
Cc: Tony Lindgren t...@atomide.com
Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com
Signed-off-by: Suman Anna s-a...@ti.com
This is similar to Omar's earlier patches for moving the code, but is
revised to prepare
501 - 600 of 639 matches
Mail list logo
