From: Joerg Roedel <joro@8bytes.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: iommu@lists.linux-foundation.org,
laurent.pinchart+renesas@ideasonboard.com,
geert+renesas@glider.be, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, horms+renesas@verge.net.au
Subject: Re: [PATCH v2 2/3] iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48
Date: Fri, 27 Jan 2017 12:47:24 +0100 [thread overview]
Message-ID: <20170127114724.GI27598@8bytes.org> (raw)
In-Reply-To: <148517162908.13306.2467186615655446796.sendpatchset@little-apple>
On Mon, Jan 23, 2017 at 08:40:29PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> Bump up the maximum numbers of micro-TLBS to 48.
>
> Each IPMMU device instance get micro-TLB assignment via
> the "iommus" property in DT. Older SoCs tend to use a
> maximum number of 32 micro-TLBs per IPMMU instance however
> newer SoCs such as r8a7796 make use of up to 48 micro-TLBs.
>
> At this point no SoC specific handling is done to validate
> the maximum number of micro-TLBs, and because of that the
> DT information is assumed to be within correct range for
> each particular SoC.
>
> If needed in the future SoC specific feature flags can be
> added to handle the maximum number of micro-TLBs without
> requiring DT changes, however at this point this does not
> seem necessary.
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
I get a conflict when applying this to v4.10-rc5. What is this based on,
any patches I missed?
Joerg
next prev parent reply other threads:[~2017-01-27 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 11:39 [PATCH v2 0/3] iommu/ipmmu-vmsa: r8a7796 support V2 Magnus Damm
2017-01-23 11:39 ` Magnus Damm
2017-01-23 11:40 ` [PATCH v2 1/3] iommu/ipmmu-vmsa: Add r8a7796 DT binding Magnus Damm
2017-01-23 11:40 ` Magnus Damm
2017-01-23 11:40 ` [PATCH v2 2/3] iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48 Magnus Damm
2017-01-23 11:40 ` Magnus Damm
2017-01-23 12:42 ` Geert Uytterhoeven
2017-01-27 11:47 ` Joerg Roedel [this message]
[not found] ` <20170127114724.GI27598-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-01-30 22:16 ` Magnus Damm
2017-01-30 22:16 ` Magnus Damm
2017-01-23 11:40 ` [PATCH v2 3/3] iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code Magnus Damm
2017-01-23 11:40 ` Magnus Damm
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=20170127114724.GI27598@8bytes.org \
--to=joro@8bytes.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=iommu@lists.linux-foundation.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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.