[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120425083747.466f5c98330af8964d980b8c@nvidia.com>
Date: Wed, 25 Apr 2012 08:37:47 +0300
From: Hiroshi Doyu <hdoyu@...dia.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
CC: "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"Felipe Balbi" <balbi@...com>, Arnd Bergmann <arnd@...db.de>,
Colin Cross <ccross@...roid.com>,
Olof Johansson <olof@...om.net>,
Stephen Warren <swarren@...dotorg.org>,
Grant Likely <grant.likely@...retlab.ca>,
"Rob Herring" <rob.herring@...xeda.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>
Subject: Re: [PATCH v2 1/3] ARM: tegra: Add AHB driver
On Tue, 24 Apr 2012 21:56:45 +0200
Russell King - ARM Linux <linux@....linux.org.uk> wrote:
> On Tue, Apr 24, 2012 at 03:05:14PM +0300, Hiroshi DOYU wrote:
> > The AHB Bus conforms to the AMBA Specification (Rev 2.0) Advanced
> > High-performance Bus (AHB) architecture.
> >
> > The AHB Arbiter controls AHB bus master arbitration. This effectively
> > forms a second level of arbitration for access to the memory
> > controller through the AHB Slave Memory device. The AHB pre-fetch
> > logic can be configured to enhance performance for devices doing
> > sequential access. Each AHB master is assigned to either the high or
> > low priority bin. Both Tegra20/30 have this AHB bus.
> >
> > Signed-off-by: Hiroshi DOYU <hdoyu@...dia.com>
> > Cc: Felipe Balbi <balbi@...com>
> > Cc: Arnd Bergmann <arnd@...db.de>
> > ---
> > Update:
> > - Use platform_device to get info from dt dynamically.(Felipe/Arnd)
> > ---
> > arch/arm/mach-tegra/Makefile | 1 +
> > arch/arm/mach-tegra/tegra-ahb.c | 285 +++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 286 insertions(+), 0 deletions(-)
>
> 1. I thought we weren't going to have any more drivers under
> arch/arm
Can this driver be located under "drivers/misc"? Or is there any better place?
> 2. From the way you describe it above, this sounds like it should be some
> kind of generic driver, which obtains the necessary settings to be
> programmed into registers from (eg) DT.
Agree.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists