linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/7] ARM: DT: tegra114: add APB DMA controller DT entry
Date: Tue, 29 Jan 2013 21:01:29 -0700	[thread overview]
Message-ID: <51089B19.8060204@wwwdotorg.org> (raw)
In-Reply-To: <5108998B.4040809@nvidia.com>

On 01/29/2013 08:54 PM, Laxman Dewangan wrote:
> On Tuesday 29 January 2013 11:12 PM, Stephen Warren wrote:
>> On 01/29/2013 05:56 AM, Laxman Dewangan wrote:
>>> NVIDIA's Tegra114 has 32 channels APB DMA controller. Add DT entry for
>>> APB DMA controllers and make it compatible with
>>> "nvidia,tegra114-apbdma".
>> The APB DMA controller node needs a clocks property. The same goes for
>> I2C and KBC. I'd like to avoid merging those 3 patches until the
>> Tegra114 clock patches are present, since the nodes won't be useful
>> until then anyway. I expect the clock patches will be merged in 3.10.
> 
> I think clock patches can be posted on top of this as Peter is working.
> Although, the driver will fail in clk_get() but still I think this can
> be apply to populate the dts file with controller specific information.

While it would be physically possible for me to apply these patches now
and rely on Peter to add the clocks properties later, there's no point
in doing so, since as you say the drivers won't work with just these
patches. There will be less churn if we simply wait for the Tegra114
clock driver first, and then apply patches to add complete and working
DT nodes for all the devices.

  reply	other threads:[~2013-01-30  4:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 12:56 [PATCH 0/7] ARM: DT: tegra114: add dt entry for gpio/pinmux/dma/i2c/serial/kbc Laxman Dewangan
2013-01-29 12:56 ` [PATCH 1/7] ARM: tegra114: select PINCTRL for Tegra114 SoC Laxman Dewangan
2013-01-29 12:56 ` [PATCH 2/7] ARM: DT: tegra114: add GPIO DT entry Laxman Dewangan
2013-01-29 12:56 ` [PATCH 3/7] ARM: DT: tegra114: add APB DMA controller " Laxman Dewangan
2013-01-29 17:42   ` Stephen Warren
2013-01-30  3:54     ` Laxman Dewangan
2013-01-30  4:01       ` Stephen Warren [this message]
2013-01-29 12:56 ` [PATCH 4/7] ARM: DT: tegra114: add pinmux " Laxman Dewangan
2013-01-29 12:56 ` [PATCH 5/7] ARM: DT: tegra114: Add i2c controller " Laxman Dewangan
2013-01-29 12:56 ` [PATCH 6/7] ARM: DT: tegra114:add aliases and DMA requestor for serial controller Laxman Dewangan
2013-01-29 18:10   ` Stephen Warren
2013-01-29 12:56 ` [PATCH 7/7] ARM: DT: tegra114: add KBC controller DT entry Laxman Dewangan

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=51089B19.8060204@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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).