All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ohad Ben-Cohen <ohad@wizery.com>
To: Suman Anna <s-anna@ti.com>
Cc: Dave Gerlach <d-gerlach@ti.com>, Robert Tivy <rtivy@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v3 1/2] remoteproc: use a flag to detect the presence of IOMMU
Date: Thu, 12 Mar 2015 11:04:03 +0200	[thread overview]
Message-ID: <CAK=WgbawMvc5Td-1+eEv3+BJWCUwHeZskJwDTPUaD66RT6EOxw@mail.gmail.com> (raw)
In-Reply-To: <1420838519-15669-2-git-send-email-s-anna@ti.com>

On Fri, Jan 9, 2015 at 11:21 PM, Suman Anna <s-anna@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 for multi-arch, especially for processors that
> do not have an IOMMU. Replace this logic instead by using a h/w
> capability flag for the presence of IOMMU in the rproc structure.
>
> This issue is seen on OMAP platforms when 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 is the case with another processor subsystem
> PRU-ICSS on AM335/AM437x. All these are platform devices, and the
> current iommu_present check will not scale for the same kernel image
> to support OMAP4/OMAP5 and AM335/AM437x.
>
> The existing platform implementation drivers - OMAP remoteproc, STE
> Modem remoteproc and DA8xx remoteproc, are updated as well to properly
> configure the newly added rproc field.
>
> Cc: Robert Tivy <rtivy@ti.com>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Suman Anna <s-anna@ti.com>

Applied to remoteproc's for-next branch.

Thanks,
Ohad.

WARNING: multiple messages have this Message-ID (diff)
From: ohad@wizery.com (Ohad Ben-Cohen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] remoteproc: use a flag to detect the presence of IOMMU
Date: Thu, 12 Mar 2015 11:04:03 +0200	[thread overview]
Message-ID: <CAK=WgbawMvc5Td-1+eEv3+BJWCUwHeZskJwDTPUaD66RT6EOxw@mail.gmail.com> (raw)
In-Reply-To: <1420838519-15669-2-git-send-email-s-anna@ti.com>

On Fri, Jan 9, 2015 at 11:21 PM, Suman Anna <s-anna@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 for multi-arch, especially for processors that
> do not have an IOMMU. Replace this logic instead by using a h/w
> capability flag for the presence of IOMMU in the rproc structure.
>
> This issue is seen on OMAP platforms when 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 is the case with another processor subsystem
> PRU-ICSS on AM335/AM437x. All these are platform devices, and the
> current iommu_present check will not scale for the same kernel image
> to support OMAP4/OMAP5 and AM335/AM437x.
>
> The existing platform implementation drivers - OMAP remoteproc, STE
> Modem remoteproc and DA8xx remoteproc, are updated as well to properly
> configure the newly added rproc field.
>
> Cc: Robert Tivy <rtivy@ti.com>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Suman Anna <s-anna@ti.com>

Applied to remoteproc's for-next branch.

Thanks,
Ohad.

  reply	other threads:[~2015-03-12  9:04 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 21:21 [PATCH v3 0/2] couple of generic remoteproc enhancements Suman Anna
2015-01-09 21:21 ` Suman Anna
2015-01-09 21:21 ` Suman Anna
2015-01-09 21:21 ` [PATCH v3 1/2] remoteproc: use a flag to detect the presence of IOMMU Suman Anna
2015-01-09 21:21   ` Suman Anna
2015-01-09 21:21   ` Suman Anna
2015-03-12  9:04   ` Ohad Ben-Cohen [this message]
2015-03-12  9:04     ` Ohad Ben-Cohen
2015-03-13 23:35     ` Suman Anna
2015-03-13 23:35       ` Suman Anna
2015-01-09 21:21 ` [PATCH v3 2/2] remoteproc: add support to handle internal memories Suman Anna
2015-01-09 21:21   ` Suman Anna
2015-01-09 21:21   ` Suman Anna
2015-02-10 10:10   ` Ohad Ben-Cohen
2015-02-10 10:10     ` Ohad Ben-Cohen
2015-02-11 20:57     ` Tony Lindgren
2015-02-11 20:57       ` Tony Lindgren
2015-02-11 20:57       ` Tony Lindgren
2015-02-11 22:28       ` Suman Anna
2015-02-11 22:28         ` Suman Anna
2015-02-11 22:48         ` Tony Lindgren
2015-02-11 22:48           ` Tony Lindgren
2015-02-12  0:01           ` Suman Anna
2015-02-12  0:01             ` Suman Anna
2015-02-12  0:18             ` Tony Lindgren
2015-02-12  0:18               ` Tony Lindgren
2015-02-12  1:07               ` Suman Anna
2015-02-12  1:07                 ` Suman Anna
2015-02-12  9:09       ` Ohad Ben-Cohen
2015-02-12  9:09         ` Ohad Ben-Cohen
2015-02-12 20:54         ` Suman Anna
2015-02-12 20:54           ` Suman Anna
2015-02-13  5:20           ` Ohad Ben-Cohen
2015-02-13  5:20             ` Ohad Ben-Cohen
2015-02-13 16:13             ` Suman Anna
2015-02-13 16:13               ` Suman Anna
2015-02-13 18:35               ` Tony Lindgren
2015-02-13 18:35                 ` Tony Lindgren
2015-01-22 21:52 ` [PATCH v3 0/2] couple of generic remoteproc enhancements Suman Anna
2015-01-22 21:52   ` Suman Anna
2015-01-22 21:52   ` Suman Anna
2015-02-03 20:55   ` Suman Anna
2015-02-03 20:55     ` Suman Anna
2015-02-03 20:55     ` Suman Anna
2015-02-05 15:11     ` Ohad Ben-Cohen
2015-02-05 15:11       ` Ohad Ben-Cohen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK=WgbawMvc5Td-1+eEv3+BJWCUwHeZskJwDTPUaD66RT6EOxw@mail.gmail.com' \
    --to=ohad@wizery.com \
    --cc=d-gerlach@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rtivy@ti.com \
    --cc=s-anna@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.