From: Prabhakar Kushwaha <prabhakar@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Varun Sethi <Varun.Sethi@freescale.com>,
linuxppc-dev@lists.ozlabs.org,
Poonam Aggrwal <poonam.aggrwal@freescale.com>,
Priyanka Jain <Priyanka.Jain@freescale.com>
Subject: Re: [PATCH 1/2][v7] powerpc/mpc85xx:Add initial device tree support of T104x
Date: Wed, 2 Oct 2013 18:01:52 +0530 [thread overview]
Message-ID: <524C1238.1060001@freescale.com> (raw)
In-Reply-To: <1380657408.10618.52.camel@snotra.buserror.net>
On 10/02/2013 01:26 AM, Scott Wood wrote:
> On Tue, 2013-10-01 at 08:56 +0530, Prabhakar Kushwaha wrote:
>> On 10/01/2013 01:17 AM, Scott Wood wrote:
>>> On Mon, 2013-09-30 at 12:24 +0530, Prabhakar Kushwaha wrote:
>>>> - Removed l2switch. It will be added later
>>> Why?
>> I am not aware of bindings required for l2switch as we are not working
>> on the driver.
>> Earlier I thought of putting a place holder. but as you suggested to put
>> bindings in documentation.
>> It will be good if it is put by actual driver owner.
> Is there a reason to believe the binding will be complicated?
>
> Does any such "driver owner" exist yet?
I don't know, as I am unaware of l2switch driver.
>
>>>> +sata@220000 {
>>>> + fsl,iommu-parent = <&pamu0>;
>>>> + fsl,liodn-reg = <&guts 0x550>; /* SATA1LIODNR */
>>>> +};
>>>> +/include/ "qoriq-sata2-1.dtsi"
>>>> +sata@221000 {
>>>> + fsl,iommu-parent = <&pamu0>;
>>>> + fsl,liodn-reg = <&guts 0x554>; /* SATA2LIODNR */
>>>> +};
>>> Whitespace
>> do we have any scripts which check for whitespace as checkpatch never
>> give any warning/error.
>> it is a very silly mistake which I am doing continuously :(
> checkpatch doesn't check dts files.
Manual check :(
>>>> +/include/ "t1040si-post.dtsi"
>>> Should at least have a comment indicating that eventually this should
>>> hold the l2 switch node.
>> yes. Ideally it should be.
>> but if I put a comment then I believe this patch will not be completed.
>> it will think as a RFC.
>> as I believe putting of TODO is generally for RFC patches.
> As is, one would wonder why the separate file exists at all.
>
> The TODO is there whether you have a comment acknowledging it or
> not. :-)
>
>
I agree. I will add a comments.
Regards,
Prabhakar
next prev parent reply other threads:[~2013-10-02 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 6:54 [PATCH 1/2][v7] powerpc/mpc85xx:Add initial device tree support of T104x Prabhakar Kushwaha
2013-09-30 19:47 ` Scott Wood
2013-10-01 3:26 ` Prabhakar Kushwaha
2013-10-01 19:56 ` Scott Wood
2013-10-02 12:31 ` Prabhakar Kushwaha [this message]
2013-10-03 9:35 ` Vlad Bogdan-BOGVLAD1
2013-10-01 3:49 ` Prabhakar Kushwaha
2013-10-04 3:16 ` Timur Tabi
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=524C1238.1060001@freescale.com \
--to=prabhakar@freescale.com \
--cc=Priyanka.Jain@freescale.com \
--cc=Varun.Sethi@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=poonam.aggrwal@freescale.com \
--cc=scottwood@freescale.com \
/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.