+devicet...@hellion.org.uk
Cc: Kumar Gala ga...@codeaurora.org
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 1 +
arch/arm/boot/dts/am4372.dtsi | 1 +
arch/arm/boot/dts/dra7.dtsi | 13 +
arch/arm/boot/dts/omap2420.dtsi | 1 +
arch/arm/boot/dts
: Ohad Ben-Cohen o...@wizery.com
Cc: Omar Ramirez Luna omar.rami...@copitl.com
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree/bindings/mailbox/omap-mailbox.txt | 24 ++
drivers/mailbox/omap-mailbox.c | 343
Add the device tree bindings document for OMAP2+ mailbox.
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Ian Campbell ijc+devicet...@hellion.org.uk
Cc: Kumar Gala ga...@codeaurora.org
Signed-off-by: Suman Anna s-a...@ti.com
driver compatible match data.
The non-DT support has to be maintained for now to not break
OMAP3 legacy boot, and the legacy-style code will be cleaned
up once OMAP3 is also converted to DT-boot only.
Cc: Jassi Brar jassisinghb...@gmail.com
Cc: Rob Herring robh...@kernel.org
Signed-off-by: Suman Anna s
On 07/09/2014 03:29 AM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140708 10:57]:
Hi Tony, Pavel,
On 07/04/2014 03:23 AM, Tony Lindgren wrote:
* Pavel Machek pa...@ucw.cz [140704 01:07]:
Hi!
The non-DT support has to be maintained for now to not break
OMAP3 legacy boot
Hi Ohad,
On 07/04/2014 12:01 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 8:28 PM, Suman Anna s-a...@ti.com wrote:
OK, but we would still require this function to lookup the registered
device from the controller-phandle to retrieve the base_id.
Can we retrieve the base_id
Hi Ohad,
On 07/03/2014 11:58 PM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 8:35 PM, Suman Anna s-a...@ti.com wrote:
Not at the moment, with the existing platform implementations. So, if I
understand you correctly, you are asking to leave out the xlate ops and
make
.
Cc: Sjur Brændeland sjur.brandel...@stericsson.com
Cc: Robert Tivy rt...@ti.com
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/remoteproc/omap_remoteproc.c | 6 ++
drivers/remoteproc/remoteproc_core.c | 15 ++-
include/linux/remoteproc.h | 2 ++
3 files changed, 10
-off-by: Robert Tivy rt...@ti.com
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/remoteproc/remoteproc_core.c | 85 +++-
include/linux/remoteproc.h | 43 +-
2 files changed, 126 insertions(+), 2 deletions(-)
diff --git a/drivers
submit soon.
The two patches are based on 3.16-rc4 and are technically independent of each
other, but submitting them together as the WkupM3 remoteproc driver would need
both of them.
regards
Suman
Suman Anna (2):
remoteproc: use a flag to detect the presence of IOMMU
remoteproc: add support
Hi Tony, Pavel,
On 07/04/2014 03:23 AM, Tony Lindgren wrote:
* Pavel Machek pa...@ucw.cz [140704 01:07]:
Hi!
The non-DT support has to be maintained for now to not break
OMAP3 legacy boot, and the legacy-style code will be cleaned
up once OMAP3 is also converted to DT-boot only.
@@
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given the total lack of response here, I suggest just deleting the
driver. No one has ever done the real work that is going to be
required to get this code out of
Hi Ohad,
On 07/03/2014 02:00 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 12:14 AM, Suman Anna s-a...@ti.com wrote:
I'm not sure we need this patch.
This patch is needed if we use the controller-phandle + args specifier
for requesting hwlocks by a client, as we need
Hi Ohad,
On 07/03/2014 02:15 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 12:14 AM, Suman Anna s-a...@ti.com wrote:
Do we have a use case today that require the xlate() method?
If not, let's remove it as we could always add it back if some new
hardware shows up that needs
-by: Suman Anna s-a...@ti.com
---
drivers/rpmsg/virtio_rpmsg_bus.c | 41 +---
1 file changed, 26 insertions(+), 15 deletions(-)
diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
index b6135d4..e9866a6 100644
--- a/drivers/rpmsg
Hi Ohad,
On 07/01/2014 07:51 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, May 1, 2014 at 3:34 AM, Suman Anna s-a...@ti.com wrote:
The number of hwspinlocks are determined based on the value read
from the IP block's SYSSTATUS register. However, the module may
not be enabled and clocked
Hi Ohad,
On 07/01/2014 07:48 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, May 1, 2014 at 3:34 AM, Suman Anna s-a...@ti.com wrote:
static int omap_hwspinlock_probe(struct platform_device *pdev)
{
- struct hwspinlock_pdata *pdata = pdev-dev.platform_data;
+ struct device_node
Hi Ohad,
On 07/01/2014 07:26 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, May 1, 2014 at 3:34 AM, Suman Anna s-a...@ti.com wrote:
The hwspinlock_device structure is used for registering a bank of
locks with the driver core. The structure already contains the
necessary members to identify
Hi Ohad,
On Thu, May 1, 2014 at 3:34 AM, Suman Anna s-a...@ti.com wrote:
2. The of_hwspin_lock_simple_xlate() is a simple default
translator function for hwspinlock provider implementations
that use a single cell number for requesting a specific lock
(relatively indexed) within
series, as per the discussion
on the lists.
regards
Suman
[1] https://patchwork.kernel.org/patch/4096831/
[2] https://patchwork.kernel.org/patch/4096761/
Suman Anna (2):
hwspinlock/omap: enable module before reading SYSSTATUS register
hwspinlock/omap: enable build for AM33xx, AM43xx DRA7xx
.
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/drivers/hwspinlock/Kconfig
index 70637d2..3612cb5 100644
--- a/drivers/hwspinlock/Kconfig
+++ b/drivers/hwspinlock/Kconfig
@@ -10,7
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 | 27 ---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git
Hi Pavel,
On 06/28/2014 12:07 PM, Pavel Machek wrote:
Hi!
The non-DT support has to be maintained for now to not break
OMAP3 legacy boot, and the legacy-style code will be cleaned
up once OMAP3 is also converted to DT-boot only.
@@ -587,24 +606,157 @@ static int
Hi Pavel,
The non-DT support has to be maintained for now to not break
OMAP3 legacy boot, and the legacy-style code will be cleaned
up once OMAP3 is also converted to DT-boot only.
@@ -587,24 +606,157 @@ static int omap_mbox_unregister(struct
omap_mbox_device *mdev)
return 0;
}
Hi Arnd,
On 06/25/2014 03:39 AM, Arnd Bergmann wrote:
On Tuesday 24 June 2014 20:47:58 Suman Anna wrote:
+static struct mbox_chan *omap_mbox_of_xlate(struct mbox_controller
*controller,
+ const struct of_phandle_args *sp)
+{
+ phandle phandle
Use the various devm_ interfaces to simplify the cleanup in
probe and remove functions in OMAP2+ mailbox driver.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap2.c | 64 -
1 file changed, 19 insertions(+), 45 deletions(-)
diff
-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap2.c | 1 -
drivers/mailbox/omap-mailbox.c | 22 ++
drivers/mailbox/omap-mbox.h | 5 -
3 files changed, 2 insertions(+), 26 deletions(-)
diff --git a/drivers/mailbox/mailbox-omap2.c b/drivers/mailbox
://lkml.org/lkml/2014/6/12/470
Suman Anna (7):
mailbox/omap: use devm_* interfaces
mailbox/omap: remove OMAP1 mailbox driver
mailbox/omap: remove omap_mbox_type_t from mailbox ops
mailbox/omap: simplify the fifo assignment by using macros
mailbox/omap: consolidate OMAP mailbox driver
be simplified and streamlined better for
converting to mailbox framework.
Cc: Aaro Koskinen aaro.koski...@iki.fi
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/configs/omap1_defconfig | 2 -
drivers/mailbox/Kconfig | 15 +--
drivers/mailbox/Makefile | 2 -
drivers/mailbox/mailbox
The OMAP mailbox IP has two different type of interrupt configuration
registers between OMAP4+ SoCs and OMAP2/3 SoCs. Simplify the current
interrupt configuration by using a single macro that translates the
two variants.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/mailbox-omap2.c
be invoked
without using a configuration counter.
- move all definitions from private omap_mbox.h into the
source code, and eliminate this internal header.
- rename some variables that used the omap2_mbox prefix with
a generic omap_mbox prefix.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers
.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/omap-mailbox.c | 126 -
1 file changed, 63 insertions(+), 63 deletions(-)
diff --git a/drivers/mailbox/omap-mailbox.c b/drivers/mailbox/omap-mailbox.c
index 66b02ab..d9a5039 100644
--- a/drivers
structure.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/omap-mailbox.c | 173 +++--
1 file changed, 115 insertions(+), 58 deletions(-)
diff --git a/drivers/mailbox/omap-mailbox.c b/drivers/mailbox/omap-mailbox.c
index d9a5039..a27e00e 100644
): http://slexy.org/view/s2nttmOLSq
[1] http://marc.info/?l=linux-omapm=140365705821115w=2
Suman Anna (9):
ARM: dts: OMAP4: Add mailbox node
ARM: dts: AM33xx: Add mailbox node
ARM: dts: AM4372: Correct mailbox node data
ARM: dts: DRA7: Add mailbox nodes
ARM: DRA7: hwmod_data: Add mailbox
): http://slexy.org/view/s2nttmOLSq
[1] http://marc.info/?l=linux-omapm=140365705821115w=2
Suman Anna (9):
ARM: dts: OMAP4: Add mailbox node
ARM: dts: AM33xx: Add mailbox node
ARM: dts: AM4372: Correct mailbox node data
ARM: dts: DRA7: Add mailbox nodes
ARM: DRA7: hwmod_data: Add mailbox
The mailbox DT node data has been added for OMAP44xx
devices.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 7e26d22..55bec30 100644
--- a/arch
The mailbox DT node data has been added for AM33xx device.
The mailbox IP in AM33xx is similar to the version found in
OMAP4+ devices.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts
The mailbox DT node for AM4372 has been corrected to include
the correct compatible flag, and remove the other properties
that have crept in by mistake.
Fixes: 9e3269b (ARM: dts: AM4372: Add L2, EDMA, mailbox, MMC and SHAM nodes)
Cc: Lokesh Vutla lokeshvu...@ti.com
Signed-off-by: Suman Anna s
with different number of mailbox fifos
and IP interrupts, and hence the omap4 compatibility string
is used.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 91 +
1 file changed, 91 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b
The legacy-style definition of the hwmod addr space is no longer
required as AM33xx/AM43xx are DT-boot only, and the minimal mailbox
DT nodes have been added, so clean up this data.
Cc: Paul Walmsley p...@pwsan.com
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2
The legacy platform device for mailbox should not be created for
a DT boot, so adjust the platform device initialization logic
appropriately.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/devices.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm
The legacy-style definition of the hwmod addr space is no longer
required after the addition of the OMAP4 mailbox DT node, so
clean up this data.
Cc: Paul Walmsley p...@pwsan.com
Cc: Benoît Cousson bcous...@baylibre.com
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2
is hardware controlled.
Cc: Rajendra Nayak rna...@ti.com
Cc: Paul Walmsley p...@pwsan.com
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 305 ++
1 file changed, 305 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
OMAP2 devices are devicetree boot only, and the legacy mode
of mailbox device creation should no longer be used, so remove
the mailbox attribute data and the hwmod addr space used for
creating mailboxes in legacy mode.
Cc: Paul Walmsley p...@pwsan.com
Signed-off-by: Suman Anna s-a...@ti.com
On 06/24/2014 08:00 PM, Suman Anna wrote:
Hi Tony, Paul,
Please ignore this, resent the same message and the series with the
proper subject.
regards
Suman
This patch series adds the minimal mailbox DT nodes for the SoCs that are
currently missing them (OMAP4, AM335x, DRA7). It also limits
://slexy.org/view/s20WvIuITK
AM43xx (AM437x GP EVM): http://slexy.org/view/s213DqnSg5
[1] https://lkml.org/lkml/2014/6/12/470
[2] http://marc.info/?l=linux-omapm=137582560717973w=2
[3] http://marc.info/?l=linux-omapm=140365705821115w=2
[4] http://marc.info/?l=linux-omapm=140365833121612w=2
Suman
Add the device tree bindings document for OMAP2+ mailbox.
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Ian Campbell ijc+devicet...@hellion.org.uk
Cc: Kumar Gala ga...@codeaurora.org
Signed-off-by: Suman Anna s-a...@ti.com
driver compatible match data.
The non-DT support has to be maintained for now to not break
OMAP3 legacy boot, and the legacy-style code will be cleaned
up once OMAP3 is also converted to DT-boot only.
Cc: Jassi Brar jassisinghb...@gmail.com
Cc: Rob Herring robh...@kernel.org
Signed-off-by: Suman Anna s
+devicet...@hellion.org.uk
Cc: Kumar Gala ga...@codeaurora.org
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 1 +
arch/arm/boot/dts/am4372.dtsi | 1 +
arch/arm/boot/dts/dra7.dtsi | 13 +
arch/arm/boot/dts/omap2420.dtsi | 1 +
arch/arm/boot/dts
, and will be removed once OMAP3 becomes DT-boot
only.
Cc: Jassi Brar jassisinghb...@gmail.com
Cc: Ohad Ben-Cohen o...@wizery.com
Cc: Omar Ramirez Luna omar.rami...@copitl.com
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/omap
of
omap_mbox_dev_info structure used in the hwmod data.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Ian Campbell ijc+devicet...@hellion.org.uk
Cc: Kumar Gala ga...@codeaurora.org
Signed-off-by: Suman
phandles for the pargs
specifier instead of indexing to avoid any channel registration
order dependencies.
Cc: Jassi Brar jassisinghb...@gmail.com
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/mailbox/omap-mailbox.c | 23 +++
1 file changed, 23 insertions(+)
diff --git
)
make[3]: *** [drivers/staging/tidspbridge/core/tiomap3430_pwr.o] Error 1
make[2]: *** [drivers/staging/tidspbridge] Error 2
Fixes: 7be914f (ARM: OMAP3: PRM/CM: Cleanup unused header)
Cc: Rajendra Nayak rna...@ti.com
Cc: Paul Walmsley p...@pwsan.com
Signed-off-by: Suman Anna s-a...@ti.com
---
arch
family both before creating the device and allocating
the carveout memory for the device.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/dsp.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/mach-omap2/dsp.c b/arch/arm/mach-omap2/dsp.c
index b8208b4..f7492df
as non-urgent fixes.
Suman Anna (3):
staging: tidspbridge: fix an erroneous removal of parentheses
ARM: OMAP3: PRM/CM: Add back macros used by TI DSP/Bridge driver
ARM: OMAP2+: create dsp device only on OMAP3 SoCs
arch/arm/mach-omap2/cm-regbits-34xx.h | 3 +++
arch/arm/mach-omap2/dsp.c
: Aybuke Ozdemir aybuke@gmail.com
Cc: Peter P Waskiewicz Jr peter.p.waskiewicz...@intel.com
Cc: Omar Ramirez Luna omar.rami...@copitl.com
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/staging/tidspbridge/core/tiomap3430.c | 6 --
1 file
Dan,
On 05/06/2014 08:18 AM, Murphy, Dan wrote:
Tony
Thanks for the comments
On 05/05/2014 05:01 PM, Tony Lindgren wrote:
* Dan Murphy dmur...@ti.com [140505 13:10]:
+
+Required parent properties:
+- compatible : Should be one of,
+ ti,omap4-prm for OMAP4 PRM instances
+
Hi Josh,
On 05/05/2014 04:54 PM, Josh Cartwright wrote:
On Mon, May 05, 2014 at 04:44:25PM -0500, Suman Anna wrote:
Hi Rob,
On 04/30/2014 07:34 PM, Suman Anna wrote:
The property 'hwlock-reserved-locks' will be used to represent
the number of locks to be reserved for clients that would need
Hi Rob,
On 05/05/2014 03:37 PM, Rob Herring wrote:
On Wed, Apr 30, 2014 at 7:34 PM, Suman Anna s-a...@ti.com wrote:
The HwSpinlock core requires a base id for registering a bank
of hwspinlocks. This base id needs to be unique across multiple
IP instances of a hwspinlock device, so that each
Hi Rob,
On 04/30/2014 07:34 PM, Suman Anna wrote:
The property 'hwlock-reserved-locks' will be used to represent
the number of locks to be reserved for clients that would need
to request/operate on specific locks. A new OF helper function,
of_hwspin_lock_get_num_reserved_locks(), is added
Hi Rob,
On 05/02/2014 09:58 AM, Rob Herring wrote:
On Wed, Apr 30, 2014 at 7:34 PM, Suman Anna s-a...@ti.com wrote:
This patch adds the generic common bindings used to represent
a hwlock device and use/request locks in a device-tree build.
All the platform-specific hwlock driver
of reserved locks. A new element is added to struct hwlock to
identify whether it is reserved to be allocated using the
hwspin_lock_request_specific() variants or available for dynamic
allocation. A new tag name, HWSPINLOCK_RESERVED, is introduced
to mark the reserved locks as such.
Signed-off-by: Suman
client api functions are
also modified to check for an invalid hwlock handle.
The consumers MUST check using IS_ERR() when requesting hwlocks
going forward to determine a valid hwlock.
Signed-off-by: Suman Anna s-a...@ti.com
---
TODO: Move this patch before the Patch4,
hwspinlock/core: add
Retrieve the number of reserved locks for OMAP by using the
of_hwspin_lock_get_num_reserved_locks() OF helper function
provided by the hwspinlock core. The range sanity check will
be performed by the hwspinlock core during the registration.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers
Changed the return statements to return an ERR_PTR instead of NULL
in case of an error. This patch helps with deferred probing of any
client users if the corresponding hwspinlock bank is not yet registered
with the hwspinlock core.
Signed-off-by: Suman Anna s-a...@ti.com
---
TODO: Collapse
.
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/drivers/hwspinlock/Kconfig
index 70637d2..3612cb5 100644
--- a/drivers/hwspinlock/Kconfig
+++ b/drivers/hwspinlock/Kconfig
@@ -10,7
Rearrange the code between hwspin_lock_unregister() and the underlying
hwspin_lock_unregister_single() functions so that the semantics are
similar to the _register_ functions. This change prepares the hwspinlock
driver core to support unregistration of reserved locks better.
Signed-off-by: Suman
also been updated to adjust
for the change of the registration API.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/hwspinlock/hwspinlock_core.c | 20
drivers/hwspinlock/hwspinlock_internal.h | 3 +++
drivers/hwspinlock/omap_hwspinlock.c | 4 ++--
drivers
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 | 27 ---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git
'hwlock-base-id', and retrieve the value through a core
OF helper function, of_hwspin_lock_get_base_id(). The representation
in DT provides a uniform way of assigning a fixed base value for a
hwspinlock device across different SoCs.
Signed-off-by: Suman Anna s-a...@ti.com
---
Documentation
the '#hwlock-cells' property.
Note that the document is named hwlock.txt deliberately to keep it
a bit more generic.
Cc: Rob Herring robh...@kernel.org
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree/bindings/hwlock/hwlock.txt | 52 ++
1 file changed, 52
the
phandle + args specifier. This function relies on the
implementation providing back a relative hwlock id within
the bank from the args specifier.
Signed-off-by: Suman Anna s-a...@ti.com
---
Documentation/hwspinlock.txt | 34 ++-
drivers/hwspinlock/hwspinlock_core.c
and a specific lock belonging to the device
requested through a phandle + args approach.
Signed-off-by: Suman Anna s-a...@ti.com
---
Documentation/hwspinlock.txt | 2 ++
drivers/hwspinlock/hwspinlock_core.c | 51
drivers/hwspinlock/hwspinlock_internal.h | 2
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
[t...@atomide.com
HwSpinlock IP is present only on OMAP4 and other newer SoCs,
which are all device-tree boot only. This patch adds the
DT bindings information for OMAP hwspinlock module.
Cc: Rob Herring robh...@kernel.org
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree/bindings/hwlock/omap
.
- OMAP4 DT node patch is unchanged
http://marc.info/?l=linux-omapm=137944644112727w=2
v1:
- Add DT parse support to OMAP hwspinlock driver
- Add OMAP4 DT node and bindings information
http://marc.info/?l=linux-omapm=137823082308009w=2
---
Suman Anna (15):
Documentation: dt: add common bindings
Tony,
On 04/25/2014 11:57 AM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140422 15:24]:
Hi Tony, Benoit,
This series includes couple of minor fixes in the OMAP DTS files. The patches
are based on 3.15-rc2.
The first patch fixes the only WARN_ON trace present during kernel boot
Hi Rajendra,
On 04/24/2014 05:06 AM, Nayak, Rajendra wrote:
The only difference from the dra74x devices is the missing .smp entry.
While at it, also fix the use of __initdata (across the file) and replace them
with __initconst as reported by checkpatch
ERROR: Use of const init definition
.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/am3517.dtsi | 16
arch/arm/boot/dts/omap3.dtsi | 2 +-
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/am3517.dtsi b/arch/arm/boot/dts/am3517.dtsi
index 788391f..5a452fd 100644
: doesn't have mpu register target base.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 6f3de22..e8988bb 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b
480c5000.aes: Cannot lookup hwmod 'aes'
[0.462403] platform 480c3000.sham: Cannot lookup hwmod 'sham'
[0.463246] platform 480cb000.smartreflex: Cannot lookup hwmod
'smartreflex_core'
[0.477243] platform 480ab000.usb_otg_hs: Cannot lookup hwmod 'usb_otg_hs'
regards
Suman
Suman Anna (3
the above differentiation. Also,
added back the interrupt-names on OMAP2420, that were
previously defined in hwmod data.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap2.dtsi| 7 ---
arch/arm/boot/dts/omap2420.dtsi | 8
arch/arm/boot/dts/omap2430.dtsi | 7 +++
3
and always reaches obj-nr_tlb_entries.
Given that we can't have two TLB entries for the same VA, break from the
loop when a match is found.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
Thanks for the reworked and simplified patch.
Acked-by: Suman Anna s-a...@ti.com
in flush_iotlb_page()
iommu/omap: Remove comment about supporting single page mappings only
iommu/omap: Fix map protection value handling
Suman Anna (3):
iommu/omap: Correct init value of iotlb_entry valid field
iommu/omap: Remove omap_iommu_domain_has_cap() function
iommu/omap
break out of the loop
- Added patches 1/6 to 3/6
Laurent Pinchart (3):
iommu/omap: Fix 'no page for' debug message in flush_iotlb_page()
iommu/omap: Remove comment about supporting single page mappings only
iommu/omap: Fix map protection value handling
Suman Anna (3):
iommu/omap
On 03/18/2014 08:35 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Tue, Mar 18, 2014 at 1:46 AM, Suman Anna s-a...@ti.com wrote:
So far, we have not come across multiple controllers. I see your point,
and I think this also depends on the semantics of how you exchange the
lock id number
Hi Ohad,
On 03/17/2014 09:23 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Sat, Mar 15, 2014 at 1:58 AM, Suman Anna s-a...@ti.com wrote:
The series doesn't change the semantics of hwspinlock registration or adds a
new OF controller registration function. Implementations would still need to
register
Hi Santosh,
On 03/15/2014 12:54 PM, Santosh Shilimkar wrote:
On Friday 14 March 2014 09:49 PM, Suman Anna wrote:
Hi Santosh, Laurent, Russell, Arnd,
On 03/14/2014 12:51 PM, Santosh Shilimkar wrote:
On Friday 14 March 2014 12:38 PM, Laurent Pinchart wrote:
Hi Santosh,
On Friday 14 March
Hi Laurent, Sakari,
On 03/16/2014 04:54 PM, Sakari Ailus wrote:
Hi Laurent and Suman,
On Fri, Mar 14, 2014 at 12:00:16PM +0100, Laurent Pinchart wrote:
Hi Suman,
(CC'ing Joerg Roedel and Marek Szyprowski for the core IOMMU discussion)
On Thursday 13 March 2014 21:33:37 Suman Anna wrote
Hi Arnd, Tony,
On 03/17/2014 11:45 AM, Tony Lindgren wrote:
* Arnd Bergmann a...@arndb.de [140317 07:18]:
On Thursday 13 March 2014, Tony Lindgren wrote:
Hi,
Resending these two, looks like my updated scripts have some issues hitting
the mailing lists..
The following changes since commit
Hi Ohad,
On 03/17/2014 02:47 PM, Ohad Ben-Cohen wrote:
Hi Suman,
On Mon, Mar 17, 2014 at 9:10 PM, Suman Anna s-a...@ti.com wrote:
base_id would be a property (if added) of the hwspinlock controller node,
and from DT perspective, we will be using the phandle for the controller
anyway. So
On 03/17/2014 06:12 PM, Laurent Pinchart wrote:
Hi Arnd,
On Friday 14 March 2014 17:57:48 Arnd Bergmann wrote:
On Friday 14 March 2014, Santosh Shilimkar wrote:
I remember NAKing this approach in past and my stand remains same. The
cache APIs which you are trying to use here are not suppose
Hi Ohad,
On 03/14/2014 03:10 PM, Ohad Ben-Cohen wrote:
Hi Suman, Mark,
On Mon, Feb 24, 2014 at 8:14 PM, Suman Anna s-a...@ti.com wrote:
Mark, Ohad,
...
Gentle reminder, can you provide your acks/comments?
Sorry for the late jump in.
I have a few comments:
Thanks for the comments
Hi Joel,
On 03/13/2014 03:35 PM, Joel Fernandes wrote:
We introduce functions to initialize clocksource and clockevent, use
CLOCKSOURCE_OF_DECLARE to declare the clocksource, and handle the clocksource
selection on a per-SoC basis (Currently only AM335x is supported). Powering up
of the timer
Hi Laurent,
On 03/14/2014 04:46 AM, Laurent Pinchart wrote:
Hi Suman,
Thank you for the review.
On Thursday 13 March 2014 19:07:33 Suman Anna wrote:
On 03/07/2014 06:46 PM, Laurent Pinchart wrote:
The prot flags passed to the IOMMU map handler are defined in
include/linux/iommu.h as IOMMU_
Hi Laurent,
On 03/07/2014 06:46 PM, Laurent Pinchart wrote:
Flushing the TLB before updating translation entries creates a race
condition and can lead to stale TLB entries if a translation request
arrives between flushing the TLB and updating the translation entries.
As there's no requirement
Hi Santosh, Laurent, Russell, Arnd,
On 03/14/2014 12:51 PM, Santosh Shilimkar wrote:
On Friday 14 March 2014 12:38 PM, Laurent Pinchart wrote:
Hi Santosh,
On Friday 14 March 2014 12:15:11 Santosh Shilimkar wrote:
+ Russell, Arnd
On Thursday 13 March 2014 10:47 PM, Anna, Suman wrote:
On
Hi Rajendra,
On 03/14/2014 04:20 AM, Nayak, Rajendra wrote:
The only difference from the dra75x devices is the missing .smp entry.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/board-generic.c | 18 ++
1 file changed, 18 insertions(+)
diff --git
Hi Laurent,
On 03/07/2014 06:46 PM, Laurent Pinchart wrote:
The flush_iotlb_page() function prints a debug message when no
corresponding page was found in the TLB. That condition is incorrectly
checked and always resolves to true, given that the for_each_iotlb_cr()
loop is never interrupted and
Hi Laurent,
On 03/07/2014 06:46 PM, Laurent Pinchart wrote:
Flushing the TLB before updating translation entries creates a race
condition and can lead to stale TLB entries if a translation request
arrives between flushing the TLB and updating the translation entries.
As there's no requirement
301 - 400 of 639 matches
Mail list logo
