All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: tegra: emc: correction of ram-code parsing from dt
Date: Mon, 20 May 2013 14:06:09 +0400	[thread overview]
Message-ID: <5199F591.80409@gmail.com> (raw)
In-Reply-To: <5196C2EF.2060408-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

18.05.2013 03:53, Stephen Warren пишет:
> On 05/12/2013 02:26 PM, Dmitry Osipenko wrote:
>> Change tegra_emc_ramcode_devnode() to get ram-code from child node instead of
>> parent.
> 
> I've applied this to Tegra's for-3.11/soc branch.
> 

Thanks.

>> For me it looks like it should be better to place ram-code inside of table
>> nodes, so num_tables will be incremented if table has valid ram-code and table
>> with invalid ram-code will be skipped on getting table params loop. This avoids
>> placing of #address-cells and #size-cells in nodes with ram-code.
>> If it looks ok, I may send new patch.
> 
> That would be a change to the DT binding. DT bindings are supposed to be
> a stable ABI, so we wouldn't want to change the binding unless there was
> a strong reason. I don't think there is one here.
> 

Ok.

      parent reply	other threads:[~2013-05-20 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12 20:26 [PATCH] ARM: tegra: emc: correction of ram-code parsing from dt Dmitry Osipenko
     [not found] ` <1368390409-14156-1-git-send-email-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-17 23:53   ` Stephen Warren
     [not found]     ` <5196C2EF.2060408-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-20 10:06       ` Dmitry Osipenko [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=5199F591.80409@gmail.com \
    --to=digetx-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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.