returning a fixed value.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu-debug.c | 13 -
1 file changed, 13 deletions(-)
diff --git a/drivers/iommu/omap-iommu-debug.c b/drivers/iommu/omap-iommu-debug.c
index 531658d..0fb92aa 100644
--- a/drivers/iommu/omap-iommu
-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu.c | 9 -
drivers/iommu/omap-iommu.h | 4
drivers/iommu/omap-iommu2.c | 2 --
3 files changed, 15 deletions(-)
diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap-iommu.c
index ed26701..332bfb9 100644
--- a/drivers
to users prior to the IOMMU framework adaptation,
but are now redundant.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu2.c | 20 +---
1 file changed, 1 insertion(+), 19 deletions(-)
diff --git a/drivers/iommu/omap-iommu2.c b/drivers/iommu/omap-iommu2.c
index
the proper L2 PTE instead of the previous L1 page descriptor
pointer.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu-debug.c | 81 ++--
1 file changed, 28 insertions(+), 53 deletions(-)
diff --git a/drivers/iommu/omap-iommu-debug.c b/drivers
against double inclusion as well.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu.h | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/omap-iommu.h b/drivers/iommu/omap-iommu.h
index 4fc51c8..d7c5132 100644
--- a/drivers/iommu/omap-iommu.h
IOMMU driver, and
there won't be external users for these functions. So, remove
the EXPORT_SYMBOL_GPL on these. The omap_iopgtable_store_entry()
is also made internal only, after making the 'pagetable' debugfs
entry read-only.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu.c | 6
The .domain field in omap_iommu struct is set properly when the
OMAP IOMMU device is attached to, but is never reset properly
on detach. Reset this properly so that the OMAP IOMMU debugfs
logic can depend on this field before allowing the debugfs
operations.
Signed-off-by: Suman Anna s
The omap2_iommu_save_ctx() and omap2_iommu_restore_ctx()
performs a sanity version check against a fixed value
that is correct only for OMAP2/OMAP3 IOMMUs. This fixed check
does not scale for all OMAP2+ IOMMUs and is not absolutely
required, so it has been removed.
Signed-off-by: Suman Anna s
a Operation not permitted trace when the
corresponding IOMMU is not enabled.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu-debug.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/iommu/omap-iommu-debug.c b/drivers/iommu/omap-iommu-debug.c
index
is defined
- iotlb_dump_cr() is similarly defined only when CONFIG_OMAP_IOMMU_DEBUG
is defined
- Elimination of the OMAP IOMMU exported functions to register the
arch ops, omap_install_iommu_arch() omap_uninstall_iommu_arch()
- Any stale comments about OMAP1 are also cleaned up
Signed-off-by: Suman
-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu.c | 15 +++
drivers/iommu/omap-iommu.h | 1 -
2 files changed, 3 insertions(+), 13 deletions(-)
diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap-iommu.c
index 4b432c4..ed26701 100644
--- a/drivers/iommu/omap
The isr_priv field is a left-over from before the IOMMU API
adaptation, this was used to store the callback data. This is
no longer relevant, so remove it.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iommu/omap
Hi Bjorn,
On 09/30/2014 03:54 PM, Bjorn Andersson wrote:
On Fri, Sep 12, 2014 at 1:24 PM, Suman Anna s-a...@ti.com wrote:
Hi Ohad,
This is an update to the hwspinlock dt support series. The series
is rebased onto v3.17-rc3, and addresses the review comments on the
previous v5 series. I have
Hi Bjorn,
On 09/26/2014 09:40 AM, Bjorn Andersson wrote:
On Mon, Jan 13, 2014 at 4:19 PM, Suman Anna s-a...@ti.com wrote:
This patch adds three new OF helper functions to use/request
locks from a hwspinlock device instantiated through a
device-tree blob.
Hi Ohad, Suman
I'm about
Hi Laurent,
On Tuesday 09 September 2014 17:31:44 Suman Anna wrote:
On Tuesday 09 September 2014 16:33:11 Suman Anna wrote:
On 09/09/2014 10:45 AM, Laurent Pinchart wrote:
The OMAP IOMMU driver supports both the OMAP1 and OMAP2+ IOMMU variants
by splitting the driver into a core module
Hi Ohad,
On 09/23/2014 09:16 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Mon, Sep 15, 2014 at 10:39 PM, Suman Anna s-a...@ti.com wrote:
These processors need to use their internal RAM for loading, which is
not for generic usage by the kernel, so defining a CMA block for this
memory doesn't make
Hi Ohad,
On 09/16/2014 10:08 AM, Ohad Ben-Cohen wrote:
On Wed, Sep 10, 2014 at 12:10 AM, Kevin Hilman khil...@kernel.org wrote:
What I think you need to do (and what I've recommended at least once in
earlier reviews) put all the (non-rproc) wkup_m3 IPC into into one
driver and create a
consuming up
unreasonable memory.
NOTE: The number of buffers is already assumed to be symmetrical
in each direction, and that logic is not unchanged.
Signed-off-by: Suman Anna s-a...@ti.com
---
v2 changes:
- add upper limit on buffers and update comments
- revise patch description
drivers/rpmsg
the usecase details for the change
summary (Patch1)
- Fixed a minor checkpatch warning (Patch 2).
regards
Suman
v1:
http://marc.info/?l=linux-omapm=140483657604924w=2
Suman Anna (2):
remoteproc: use a flag to detect the presence of IOMMU
remoteproc: add support to handle internal memories
-off-by: Robert Tivy rt...@ti.com
Signed-off-by: Suman Anna s-a...@ti.com
---
v2:
- fixed a minor checkpatch warning
drivers/remoteproc/remoteproc_core.c | 83 +++-
include/linux/remoteproc.h | 43 ++-
2 files changed, 124 insertions(+), 2
as well to properly
configure the newly added rproc field.
Cc: Robert Tivy rt...@ti.com
Cc: Linus Walleij linus.wall...@linaro.org
Signed-off-by: Suman Anna s-a...@ti.com
---
v2:
- set the field explicitly in all existing remoteproc platform drivers
- update patch description
drivers/remoteproc
Hi Ohad,
On Tue, Jul 29, 2014 at 10:33 PM, Suman Anna s-a...@ti.com wrote:
We currently have two usecases. The primary usecase is the WkupM3
processor on TI Sitara AM335x/AM437x SoCs used for suspend/resume
management. This series is a dependency for the WkupM3 remoteproc driver
that Dave
-off-by: Suman Anna s-a...@ti.com
---
Documentation/hwspinlock.txt | 26
drivers/hwspinlock/hwspinlock_core.c | 122 +++
include/linux/hwspinlock.h | 15 -
3 files changed, 160 insertions(+), 3 deletions(-)
diff --git a/Documentation
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
Herring robh...@kernel.org
Signed-off-by: Suman Anna s-a...@ti.com
---
.../devicetree/bindings/hwlock/hwlock.txt | 55 ++
1 file changed, 55 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwlock/hwlock.txt
diff --git a/Documentation/devicetree
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
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
DT parse support to OMAP hwspinlock driver
- Add OMAP4 DT node and bindings information
http://marc.info/?l=linux-omapm=137823082308009w=2
---
Suman Anna (5):
Documentation: dt: add common bindings for hwspinlock
Documentation: dt: add the omap hwspinlock bindings document
hwspinlock/core
=linux-arm-kernelm=141055363113881w=2
[3] http://marc.info/?l=linux-arm-kernelm=139968477508013w=2
Suman Anna (3):
hwspinlock/core: prepare unregister code to support reserved locks
hwspinlock/core: prepare core to support reserved locks
hwspinlock/core: add support for reserved locks
of reserved locks. A new element is added to struct hwspinlock
to identify whether it is reserved to be allocated using the
hwspin_lock_request_specific() API or available for dynamic
allocation. A new tag name, HWSPINLOCK_RESERVED, is introduced
to mark the reserved locks as such.
Signed-off-by: Suman
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
the
hwspin_lock_request_specific() API for DT boots.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/hwspinlock/hwspinlock_core.c | 61 ++--
1 file changed, 59 insertions(+), 2 deletions(-)
diff --git a/drivers/hwspinlock/hwspinlock_core.c
b/drivers
-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-a...@ti.com
Acked-by: Pavel
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
://marc.info/?l=linux-omapm=140668054422693w=2
[2] http://marc.info/?l=linux-omapm=140511512208519w=2
[3] http://www.spinics.net/lists/linux-omap/msg108574.html
Suman Anna (2):
Documentation: dt: add omap mailbox bindings
mailbox/omap: add support for parsing dt devices
.../devicetree/bindings
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
=140668054422693w=2
[2] http://marc.info/?l=linux-omapm=141037688814464w=2
Suman Anna (1):
ARM: dts: OMAP2+: Add sub mailboxes device node information
arch/arm/boot/dts/am33xx.dtsi | 4
arch/arm/boot/dts/am4372.dtsi | 4
arch/arm/boot/dts/omap2420.dtsi | 8
arch/arm/boot/dts/omap2430
+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
://marc.info/?l=linux-omapm=140668054422693w=2
[2] https://lkml.org/lkml/2014/8/1/200
[3] http://marc.info/?l=linux-omapm=141037688814464w=2
[4] http://marc.info/?l=linux-omapm=141037727114587w=2
Suman Anna (2):
mailbox/omap: adapt to the new mailbox framework
ARM: dts: OMAP2+: Add #mbox-cells
2 will be removed when
the OMAP mailbox driver is adapted to runtime_pm. The other exported
API omap_mbox_request_channel will be removed once OMAP3 becomes DT-boot
only.
Cc: Jassi Brar jassisinghb...@gmail.com
Cc: Ohad Ben-Cohen o...@wizery.com
Signed-off-by: Suman Anna s-a...@ti.com
Hi Tony,
On 09/08/2014 09:52 PM, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [140908 16:21]:
* Suman Anna s-a...@ti.com [140729 17:37]:
Hi,
This is an updated version of the OMAP Mailbox framework adoption
DT support series, refreshed to work with the v9 version of the mailbox
Hi Ohad,
On 09/09/2014 05:31 AM, Ohad Ben-Cohen wrote:
On Tue, Sep 9, 2014 at 1:30 AM, Kevin Hilman khil...@linaro.org wrote:
To me, it's not terribly clear how you made the split between this PM
core code an the remoteproc code. In the changelog for the remoteproc
patch, it states it's to
Hi Laurent,
On 09/09/2014 10:45 AM, Laurent Pinchart wrote:
The OMAP IOMMU driver supports both the OMAP1 and OMAP2+ IOMMU variants
by splitting the driver into a core module and a thin arch-specific
operations module.
(In practice only the OMAP2+ module omap-iommu2 is implemented, but
Hi Laurent,
On 09/09/2014 10:45 AM, Laurent Pinchart wrote:
The owner field is never set. Remove it.
Thanks, this seems to have been dead code since the days OMAP IOMMU has
been converted from building as modules to built-in as part of the IOMMU
API adoption. So,
Acked-by: Suman Anna s
Hi Laurent,
On Tuesday 09 September 2014 16:33:11 Suman Anna wrote:
On 09/09/2014 10:45 AM, Laurent Pinchart wrote:
The OMAP IOMMU driver supports both the OMAP1 and OMAP2+ IOMMU variants
by splitting the driver into a core module and a thin arch-specific
operations module.
(In practice
Hi Laurent,
On Wednesday 03 September 2014 18:58:31 Suman Anna wrote:
Any device requiring to be attached to an iommu_domain must have
valid archdata containing the necessary iommu information, which
is SoC-specific. Add a check in the omap_iommu_attach_dev to make
sure that the device has
Hi Laurent,
On Wednesday 03 September 2014 18:58:32 Suman Anna wrote:
A device is tied to an iommu through its archdata field. The archdata
is allocated on the fly for DT-based devices automatically through the
.add_device iommu ops. The current logic incorrectly assigned the name
Hi,
This is an updated series addressing Laurent's review comments on
Patch1. Patch2 is unchanged from the previous series.
Patches are based on 3.17-rc3.
v1:
http://marc.info/?l=linux-omapm=140978874026176w=2
Suman Anna (2):
iommu/omap: Check for valid archdata in attach_dev
iommu/omap
by the attach logic. Fix this issue so that DT-based devices
can attach successfully to an IOMMU domain.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap
. This prevents a
NULL pointer dereference on any misconfigured devices.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap-iommu.c
index 02ef0ac..ea6e59d 100644
of the archdata. This prevents a
NULL pointer dereference on any misconfigured devices.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap-iommu.c
index 02ef0ac..f245d51 100644
devices.
The kernel does not yet have any OMAP IOMMU users represented in DT, so
this failure is not currently seen, but will be seen when users like OMAP3
ISP or OMAP4 remoteprocs are converted to DT.
regards
Suman
Suman Anna (2):
iommu/omap: Check for valid archdata in attach_dev
iommu/omap: Fix
by the attach logic. Fix this issue so that DT-based devices
can attach successfully to an IOMMU domain.
Signed-off-by: Suman Anna s-a...@ti.com
---
drivers/iommu/omap-iommu.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap
Hi Ohad,
On 08/13/2014 08:40 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Tue, Aug 12, 2014 at 7:19 PM, Suman Anna s-a...@ti.com wrote:
Yes, I was playing around with using less buffers in the remoteproc
resource table for the vrings. The remoteproc virtio code creates the
vrings using
Hi Ohad,
On 08/12/2014 10:30 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 11:53 PM, Suman Anna s-a...@ti.com wrote:
The buffers to be used for communication are allocated during
the rpmsg virtio driver's probe, and the number of buffers is
currently hard-coded to 512. Remove
On 08/04/2014 06:50 AM, Ohad Ben-Cohen wrote:
On Tue, Jul 29, 2014 at 7:10 PM, Suman Anna s-a...@ti.com wrote:
We are trying to add a remoteproc driver for a small Cortex M3 called
the WkupM3 used for suspend/resume management on TI AM335/AM437x SoCs.
This processor does not have an MMU. Same
On 07/29/2014 03:59 AM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140624 17:45]:
Hi,
This patch series is mainly a cleanup of the current OMAP mailbox drivers
in preparation for adding DT support and adoption to the upcoming mailbox
framework from Jassi Brar [1]. It removes the OMAP1
Hi Ohad,
On 07/29/2014 05:57 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Tue, Jul 8, 2014 at 7:22 PM, Suman Anna s-a...@ti.com wrote:
The remoteproc driver core currently relies on iommu_present() on
the bus the device is on, to perform MMU management. However, this
logic doesn't scale
Hi Ohad,
On 07/29/2014 06:00 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Tue, Jul 8, 2014 at 7:22 PM, Suman Anna s-a...@ti.com wrote:
A remote processor may need to load certain firmware sections into
internal memories (eg: RAM at L1 or L2 levels) for performance or
other reasons.
Can you
/cgit/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v3.17/mailbox
[5] http://www.spinics.net/lists/linux-omap/msg109331.html
Suman Anna (5):
Documentation: dt: add omap mailbox bindings
mailbox/omap: add support for parsing dt devices
ARM: dts: OMAP2+: Add sub mailboxes device node
+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
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
...@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 | 346 -
drivers/remoteproc/omap_remoteproc.c
-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-a...@ti.com
---
drivers/mailbox
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
Hi Ohad,
On 07/24/2014 08:45 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 2:00 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
On 07/23/2014 04:24 AM, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [140716 00:10]:
* Suman Anna s-a...@ti.com [140715 09:59]:
Hi Tony,
On 07/15/2014 08:30 AM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140711 14:47]:
Add the hwmod data for the 13 instances of the system
Hi Lokesh,
On 07/22/2014 11:06 PM, Vutla, Lokesh wrote:
Hi Nishanth,
On Tuesday 22 July 2014 10:15 PM, Nishanth Menon wrote:
On 07/16/2014 03:36 AM, Lokesh Vutla wrote:
This series add seperate ocp interface lists that are specific to dra74x
and dra72x, and moving USB OTG SS4 to dra74x only
On 07/16/2014 03:36 AM, Vutla, Lokesh wrote:
From: Rajendra Nayak rna...@ti.com
Use the corresponding compatibles to identify the devices.
Signed-off-by: Rajendra Nayak rna...@ti.com
Signed-off-by: Lokesh Vutla lokeshvu...@ti.com
---
arch/arm/mach-omap2/soc.h |7 +++
1 file
Hi Dan,
On 07/17/2014 11:45 AM, Murphy, Dan wrote:
Describe the TI reset DT entries for TI SoC's.
The document definitely needs some cleanup. Here are comments from a
quick glance. In any case, I think this binding will change as you
address Tony's comments.
Signed-off-by: Dan Murphy
Hi Dan,
On 07/17/2014 11:45 AM, Murphy, Dan wrote:
Add the prcm_resets node to the prcm parent node.
Add the am33xx_resets file to define the
am33xx reset lines that are handled by this reset
framework.
Signed-off-by: Dan Murphy dmur...@ti.com
---
v3 - No changes
Hi Dan,
On 07/17/2014 11:45 AM, Murphy, Dan wrote:
Add the prcm_resets node to the prcm parent node.
Add the am34xx_resets file to define the
am34xx reset lines that are handled by this reset
framework.
Signed-off-by: Dan Murphy dmur...@ti.com
---
v3 - No changes
Hi Dan,
On 07/17/2014 11:45 AM, Murphy, Dan wrote:
Add the prcm_resets node to the prm parent node.
Add the draxx_resets file to define the
dra7xx reset lines that are handled by this reset
framework.
Signed-off-by: Dan Murphy dmur...@ti.com
---
v3 - No changes
Hi Dan,
On 07/17/2014 11:45 AM, Murphy, Dan wrote:
Add the prm_resets node to the prm parent node.
Add the omap54xx_resets file to define the
omap5 reset lines that are handled by this reset
framework.
Signed-off-by: Dan Murphy dmur...@ti.com
---
v3 - No changes
Hi Dan,
On 07/17/2014 11:45 AM, Murphy, Dan wrote:
The TI SoC reset controller support utilizes the
reset controller framework to give device drivers or
function drivers a common set of APIs to call to reset
a module.
The reset-ti is a common interface to the reset framework.
The
On 07/18/2014 05:50 AM, Laurent Pinchart wrote:
Hi Suman,
Thank you for the review.
On Thursday 17 July 2014 10:53:03 Suman Anna wrote:
On 07/17/2014 06:09 AM, Laurent Pinchart wrote:
The OMAP3 ISP driver was the only user of the OMAP IOVMM API. Now that
is has been ported to the DMA API
in the entire series,
Acked-by: Suman Anna s-a...@ti.com
regards
Suman
I'd like to get at least the first patch merged in v3.17. To avoid splitting
the series across three kernel versions, it would be nice to also merge at
least the second patch for v3.17. If there's no risk of conflict
Hi Laurent,
On 07/17/2014 06:09 AM, Laurent Pinchart wrote:
The OMAP3 ISP driver was the only user of the OMAP IOVMM API. Now that
is has been ported to the DMA API, remove the unused virtual memory
manager.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
Joerg,
be moved out of staging. Until someone can
put in the work to make the driver work again and move it out of
staging, remove it from the kernel.
Signed-off-by: Kristina Martšenko kristina.martse...@gmail.com
Cc: Omar Ramirez Luna omar.rami...@copitl.com
Cc: Suman Anna s-a...@ti.com
Cc: Felipe
: Suman Anna s-a...@ti.com
Cc: Felipe Contreras felipe.contre...@gmail.com
Acked-by: Suman Anna s-a...@ti.com
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
Hi Markus,
On 07/16/2014 03:50 PM, Markus Mayer wrote:
If I may nit-pick here for a minute...
On 11 July 2014 15:04, Suman Anna s-a...@ti.com wrote:
Logic has been added to the OMAP2+ mailbox code to parse the
mailbox dt nodes and construct the different sub-mailboxes
associated
Hi Tony,
On 07/15/2014 08:30 AM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140711 14:47]:
Add the hwmod data for the 13 instances of the system mailbox
IP in DRA7 SoC. The patch is needed for performing a soft-reset
while configuring the respective mailbox instance, otherwise is
a non
Hi Markus,
On 07/11/2014 06:15 PM, Markus Mayer wrote:
On 11 July 2014 15:04, Suman Anna s-a...@ti.com wrote:
Hi,
This is a refresh of the OMAP Mailbox framework adoption DT support
series [1], to work with the revised OMAP mailbox DT/hwmod cleanup
series [2].
The series has one less
Hi Dave,
On 07/14/2014 09:41 AM, Santosh Shilimkar wrote:
On Thursday 10 July 2014 10:55 PM, Dave Gerlach wrote:
Add the device tree bindings document for am3353 wkup_m3.
Signed-off-by: Dave Gerlach d-gerl...@ti.com
CC: Ohad Ben-Cohen o...@wizery.com
CC: Benoit Cousson bcous...@baylibre.com
Hi Dave,
On 07/10/2014 09:55 PM, Dave Gerlach wrote:
Use pdata-quirks to reset the wkup_m3 during boot.
Signed-off-by: Dave Gerlach d-gerl...@ti.com
---
arch/arm/mach-omap2/pdata-quirks.c| 12
include/linux/platform_data/wkup_m3.h | 17 +
2 files changed,
Hi Dave,
I have a few more comments in addition to Santosh's..
On 07/14/2014 09:54 AM, Santosh Shilimkar wrote:
On Thursday 10 July 2014 10:55 PM, Dave Gerlach wrote:
Add a remoteproc driver to load the firmware for and boot the wkup_m3
present on am33xx. The wkup_m3 is an integrated Cortex
Hi Markus,
There are couple of dependent preparatory series. You probably missed
the following in the cover letter.
The series depends on the OMAP mailbox cleanup series [5] and the
refreshed OMAP mailbox DT/hwmod cleanup series [2].
As long as you pick the two dependent series, they apply
The mailbox DT node for AM4372 is enabled and is corrected to
remove some 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-a...@ti.com
---
arch/arm/boot/dts
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
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.
Acked-by: Paul Walmsley p...@pwsan.com
Signed-off-by: Suman Anna s-a...@ti.com
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 | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts
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 | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 7e26d22..69408b5 100644
--- a/arch
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.
Acked-by: Paul Walmsley p...@pwsan.com
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2
=140366093024233w=2
Suman Anna (10):
ARM: dts: OMAP2+: Add mailbox fifo and user information
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 hwmod data
attribute data through the
.num_fifos and .num_users fields previously.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap2420.dtsi | 2 ++
arch/arm/boot/dts/omap2430.dtsi | 2 ++
arch/arm/boot/dts/omap3.dtsi| 2 ++
arch/arm/boot/dts/omap5.dtsi| 2 ++
4 files changed, 8
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
to the remaining 12 mailboxes.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 117
1 file changed, 117 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index c29945e..99c40d4 100644
--- a/arch
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
/view/s2KGKGeFre
[1] http://www.spinics.net/lists/linux-omap/msg108595.html
[2] http://marc.info/?l=linux-omapm=140511512208519w=2
[3] https://lkml.org/lkml/2014/7/11/174
[4] http://www.spinics.net/lists/linux-omap/msg109331.html
[5] http://www.spinics.net/lists/linux-omap/msg108574.html
Suman Anna
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
201 - 300 of 639 matches
Mail list logo
