From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 05/12] memory: Add NVIDIA Tegra memory controller support
Date: Wed, 12 Nov 2014 16:09:42 +0100 [thread overview]
Message-ID: <20141112150940.GE26488@ulmo> (raw)
In-Reply-To: <20141112150233.GW10744@8bytes.org>
On Wed, Nov 12, 2014 at 04:02:34PM +0100, Joerg Roedel wrote:
> On Wed, Nov 12, 2014 at 03:47:16PM +0100, Thierry Reding wrote:
> > The SMMU is part of a larger IP block that's also a memory controller.
> > Having it in drivers/iommu would mean that we need to provide a
> > mechanism to synchronize between the two drivers. They also share a
> > number of data tables, so that would need to be shared somehow as well.
> > By keeping both in the same directory we don't have to expose any of
> > this publicly.
>
> Since these parts are in different files you export the interfaces
> anyway through non-static symbols and those dependencys also exist for
> other IOMMU drivers. So I prefer this file to live in drivers/iommu.
But we don't export symbols to the global symbol table since it's all
built as a single module. Moving one part to drivers/iommu will mean
that I need to provide a public header with the symbols. And I'd need
to actually EXPORT_SYMBOL them because technically there's nothing
preventing these drivers to be built as modules.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141112/9fcf82a7/attachment.sig>
prev parent reply other threads:[~2014-11-12 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 16:00 [PATCH v6 00/12] NVIDIA Tegra memory controller and IOMMU support Thierry Reding
2014-11-07 16:00 ` [PATCH v6 01/12] clk: tegra: Implement memory-controller clock Thierry Reding
2014-11-07 16:00 ` [PATCH v6 02/12] amba: Add Kconfig file Thierry Reding
2014-11-07 16:00 ` [PATCH v6 03/12] ARM: tegra: Move AHB Kconfig to drivers/amba Thierry Reding
2014-11-07 16:00 ` [PATCH v6 04/12] of: Add NVIDIA Tegra memory controller binding Thierry Reding
2014-11-07 16:00 ` [PATCH v6 06/12] ARM: tegra: Add memory controller support for Tegra30 Thierry Reding
2014-11-07 16:00 ` [PATCH v6 07/12] ARM: tegra: Add memory controller support for Tegra114 Thierry Reding
2014-11-07 16:00 ` [PATCH v6 08/12] ARM: tegra: Add memory controller support for Tegra124 Thierry Reding
2014-11-07 16:01 ` [PATCH v6 09/12] ARM: tegra: Enable IOMMU for display controllers on Tegra30 Thierry Reding
2014-11-07 16:01 ` [PATCH v6 10/12] ARM: tegra: Enable IOMMU for display controllers on Tegra114 Thierry Reding
2014-11-07 16:01 ` [PATCH v6 11/12] ARM: tegra: Enable IOMMU for display controllers on Tegra124 Thierry Reding
2014-11-07 16:01 ` [PATCH v6 12/12] memory: tegra: Add Tegra132 support Thierry Reding
2014-11-10 9:53 ` [PATCH v6 00/12] NVIDIA Tegra memory controller and IOMMU support Alexandre Courbot
[not found] ` <1415376063-17205-6-git-send-email-thierry.reding@gmail.com>
2014-11-12 14:21 ` [PATCH v6 05/12] memory: Add NVIDIA Tegra memory controller support Joerg Roedel
2014-11-12 14:47 ` Thierry Reding
2014-11-12 15:02 ` Joerg Roedel
2014-11-12 15:09 ` Thierry Reding [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=20141112150940.GE26488@ulmo \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).