All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Hiroshi DOYU <hdoyu@nvidia.com>
Cc: swarren@wwwdotorg.org, linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, Felipe Balbi <balbi@ti.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	Rob Landley <rob@landley.net>, Colin Cross <ccross@android.com>,
	Olof Johansson <olof@lixom.net>,
	Russell King <linux@arm.linux.org.uk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv5 1/3] ARM: tegra: Add Tegra AHB driver
Date: Mon, 7 May 2012 08:04:28 +0000	[thread overview]
Message-ID: <201205070804.29154.arnd@arndb.de> (raw)
In-Reply-To: <1336373032-16881-1-git-send-email-hdoyu@nvidia.com>

On Monday 07 May 2012, Hiroshi DOYU wrote:
> Tegra 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.
> 
> Some of configuration params could be passed from DT too if needed.
> 
> Signed-off-by: Hiroshi DOYU <hdoyu@nvidia.com>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Arnd Bergmann <arnd@arndb.de>

Acked-by: Arnd Bergmann <arnd@arndb.de>

for the driver, but please fix the issue pointed out by Russell.

	Arnd


WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 1/3] ARM: tegra: Add Tegra AHB driver
Date: Mon, 7 May 2012 08:04:28 +0000	[thread overview]
Message-ID: <201205070804.29154.arnd@arndb.de> (raw)
In-Reply-To: <1336373032-16881-1-git-send-email-hdoyu@nvidia.com>

On Monday 07 May 2012, Hiroshi DOYU wrote:
> Tegra 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.
> 
> Some of configuration params could be passed from DT too if needed.
> 
> Signed-off-by: Hiroshi DOYU <hdoyu@nvidia.com>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Arnd Bergmann <arnd@arndb.de>

Acked-by: Arnd Bergmann <arnd@arndb.de>

for the driver, but please fix the issue pointed out by Russell.

	Arnd

  parent reply	other threads:[~2012-05-07  8:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07  6:43 [PATCHv5 1/3] ARM: tegra: Add Tegra AHB driver Hiroshi DOYU
2012-05-07  6:43 ` Hiroshi DOYU
2012-05-07  6:43 ` Hiroshi DOYU
     [not found] ` <1336373032-16881-1-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-05-07  6:43   ` [PATCHv5 2/3] ARM: tegra: Add SMMU enabler in AHB Hiroshi DOYU
2012-05-07  6:43     ` Hiroshi DOYU
2012-05-07  6:43     ` Hiroshi DOYU
2012-05-07  6:43   ` [PATCHv5 3/3] ARM: dt: tegra: Add device tree support for AHB Hiroshi DOYU
2012-05-07  6:43     ` Hiroshi DOYU
2012-05-07  6:43     ` Hiroshi DOYU
2012-05-07  7:42   ` [PATCHv5 1/3] ARM: tegra: Add Tegra AHB driver Russell King - ARM Linux
2012-05-07  7:42     ` Russell King - ARM Linux
2012-05-07  7:42     ` Russell King - ARM Linux
     [not found]     ` <20120507074228.GK26481-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2012-05-07  7:52       ` Hiroshi Doyu
2012-05-07  7:52         ` Hiroshi Doyu
2012-05-07  7:52         ` Hiroshi Doyu
     [not found]         ` <20120507.105254.1899925115243585929.hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-05-07  8:59           ` Arnd Bergmann
2012-05-07  8:59             ` Arnd Bergmann
2012-05-07  8:59             ` Arnd Bergmann
2012-05-07  9:23             ` Hiroshi Doyu
2012-05-07  9:23               ` Hiroshi Doyu
2012-05-07  9:23               ` Hiroshi Doyu
2012-05-07 10:24               ` Arnd Bergmann
2012-05-07 10:24                 ` Arnd Bergmann
2012-05-07 10:24                 ` Arnd Bergmann
     [not found]                 ` <201205071024.48958.arnd-r2nGTMty4D4@public.gmane.org>
2012-05-07 11:36                   ` Hiroshi Doyu
2012-05-07 11:36                     ` Hiroshi Doyu
2012-05-07 11:36                     ` Hiroshi Doyu
2012-05-07 11:36                     ` Hiroshi Doyu
2012-05-07 15:47                     ` Stephen Warren
2012-05-07 15:47                       ` Stephen Warren
2012-05-07 15:47                       ` Stephen Warren
2012-05-07 18:36                     ` gregkh
2012-05-07 18:36                       ` gregkh
2012-05-07 18:36                       ` gregkh at linuxfoundation.org
2012-05-08  5:12                       ` Hiroshi Doyu
2012-05-08  5:12                         ` Hiroshi Doyu
2012-05-08  5:12                         ` Hiroshi Doyu
     [not found]                     ` <20120507.143647.508182574757518311.hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-05-08 19:45                       ` Stephen Warren
2012-05-08 19:45                         ` Stephen Warren
2012-05-08 19:45                         ` Stephen Warren
2012-05-07  8:04 ` Arnd Bergmann [this message]
2012-05-07  8:04   ` Arnd Bergmann

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=201205070804.29154.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=balbi@ti.com \
    --cc=ccross@android.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdoyu@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=linville@tuxdriver.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=ohad@wizery.com \
    --cc=olof@lixom.net \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=swarren@wwwdotorg.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 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.