From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
iommu@lists.linux-foundation.org,
Linux-sh list <linux-sh@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH 2/5] iommu/ipmmu-vmsa: Add device tree bindings documentation
Date: Mon, 31 Mar 2014 12:18:04 +0200 [thread overview]
Message-ID: <2135036.3YMfppXtgo@avalon> (raw)
In-Reply-To: <CAMuHMdUF6MmH_eK=SbG-q6Kai_q+5ufm-Vsd8z-bYKGj7Z-Spw@mail.gmail.com>
Hi Geert,
On Monday 31 March 2014 10:39:48 Geert Uytterhoeven wrote:
> On Sat, Mar 29, 2014 at 12:36 AM, Laurent Pinchart wrote:
> > +Required Properties:
> > +
> > + - compatible: Must contain "renesas,ipmmu-vmsa".
> > + - reg: Base address and size of the IPMMU registers.
> > + - interrupts: Specifier for the MMU fault interrupt.
>
> Does it make sense to have a property for the number of micro-TLBs,
> or is this handled transparently?
>
> E.g. ipmmu_mx has 24 micro-TLBs, but ipmmu_mp has 30.
The IPMMU driver doesn't need to know the number of micro-TLBs, so we should
be fine without specifying it in DT. The micro-TLBs are configured when a bus
master device is attached or detached, and at that point the device provides
its micro-TLB number.
The only reason I can foresee why the number of micro-TLBs would be useful is
to iterate over micro-TLBs when the driver probes the device to disable them
all. A mask would probably be better than a number in that case, and I think
we can always add that later if we find a need for it.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-03-31 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 23:36 [PATCH 0/5] Renesas VMSA-compatible IPMMU DT support Laurent Pinchart
2014-03-28 23:36 ` [PATCH 2/5] iommu/ipmmu-vmsa: Add device tree bindings documentation Laurent Pinchart
2014-03-29 15:50 ` Sergei Shtylyov
2014-04-01 13:57 ` Laurent Pinchart
[not found] ` <1396049781-12941-3-git-send-email-laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-03-31 8:39 ` Geert Uytterhoeven
2014-03-31 10:18 ` Laurent Pinchart [this message]
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=2135036.3YMfppXtgo@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=iommu@lists.linux-foundation.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).