[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3a23d0b4e1e11c9b71848e0345777cd4163f185@8b5064a13e22126c1b9329f0dc35b8915774b7c3.invalid>
Date: Fri, 4 Dec 2015 21:29:55 -0000
From: "Simon Arlott" <simon@...e.lp0.eu>
To: "Jonas Gorski" <jogo@...nwrt.org>,
"Brian Norris" <computersforpeace@...il.com>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"David Woodhouse" <dwmw2@...radead.org>,
"MTD Maling List" <linux-mtd@...ts.infradead.org>,
"Rob Herring" <robh+dt@...nel.org>,
"Pawel Moll" <pawel.moll@....com>,
"Mark Rutland" <mark.rutland@....com>,
"Ian Campbell" <ijc+devicetree@...lion.org.uk>,
"Kumar Gala" <galak@...eaurora.org>,
"bcm-kernel-feedback-list" <bcm-kernel-feedback-list@...adcom.com>,
"Florian Fainelli" <f.fainelli@...il.com>,
"Kamal Dasu" <kdasu.kdev@...il.com>
Subject: Re: [PATCH 1/3] mtd: brcmnand: Add brcm,bcm6368-nand device tree
binding
On Fri, December 4, 2015 16:04, Jonas Gorski wrote:
> On Thu, Dec 3, 2015 at 12:41 AM, Simon Arlott <simon@...e.lp0.eu> wrote:
>> + * "brcm,nand-bcm6368"
>> + - compatible: should contain "brcm,nand-bcm<soc>", "brcm,nand-bcm6368"
>> + - reg: (required) the 'NAND_INTR_BASE' register range, with combined status
>> + and enable registers, and boot address registers
>> + - reg-names: (required) "nand-intr-base"
>
> Can't we use the same name as bcm63138, i.e. nand-int-base?
Brian,
Before I change this, is there anything else in the patch series that needs to
be changed?
(I'll keep the comment referring to "NAND_INTR_BASE" the same because that's the name
in the original #define for this hardware.)
--
Simon Arlott
--
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