From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Walmsley Subject: Re: [PATCHv2 3/3] Documentation: DT bindings: Tegra AHB: note base address change Date: Thu, 19 Mar 2015 15:26:06 +0000 (UTC) Message-ID: References: <20150317083221.32662.14647.stgit@baseline> <20150317083221.32662.96822.stgit@baseline> <20150317103806.GU8656@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: <20150317103806.GU8656@n2100.arm.linux.org.uk> Sender: linux-kernel-owner@vger.kernel.org To: Russell King - ARM Linux Cc: linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Mark Rutland , Alexandre Courbot , Pawel Moll , Ian Campbell , Stephen Warren , linux-kernel@vger.kernel.org, Eduardo Valentin , devicetree@vger.kernel.org, Rob Herring , Thierry Reding , Paul Walmsley , Kumar Gala , Hiroshi DOYU List-Id: linux-tegra@vger.kernel.org On Tue, 17 Mar 2015, Russell King - ARM Linux wrote: > On Tue, Mar 17, 2015 at 01:32:21AM -0700, Paul Walmsley wrote: > > Required properties: > > - compatible : For Tegra20, must contain "nvidia,tegra20-ahb". For > > - Tegra30, must contain "nvidia,tegra30-ahb". Otherwise, must contain > > - '"nvidia,-ahb", "nvidia,tegra30-ahb"' where is tegra124, > > - tegra132, or tegra210. > > -- reg : Should contain 1 register ranges(address and length) > > + Tegra30, must contain "nvidia,tegra30-ahb". For Tegra114 and Tegra124, must > > + contain '"nvidia,-ahb", "nvidia,tegra30-ahb"' where is tegra114 > > + or tegra124. For Tegra132, the compatible string must contain > > + "nvidia,tegra132-ahb". > > + > > +- reg : Should contain 1 register ranges(address and length). On Tegra20, > > + Tegra30, Tegra114, and Tegra124 chips, the low byte of the physical base > > + address of the IP block must end in 0x04. On DT files for later chips, the > > + actual hardware base address of the IP block should be used. > > You could check that in the driver. If you can check it in the driver, > you can also decide to ignore it if it were offset by 0x04 (possibly > printing a warning.) That opens up the ability to fix the older Tegra > DT files going forward while still remaining compatible with existing > DT files, and avoiding the need for a complex note about this. That's fine, I'll do that and drop this patch. - Paul From mboxrd@z Thu Jan 1 00:00:00 1970 From: paul@pwsan.com (Paul Walmsley) Date: Thu, 19 Mar 2015 15:26:06 +0000 (UTC) Subject: [PATCHv2 3/3] Documentation: DT bindings: Tegra AHB: note base address change In-Reply-To: <20150317103806.GU8656@n2100.arm.linux.org.uk> References: <20150317083221.32662.14647.stgit@baseline> <20150317083221.32662.96822.stgit@baseline> <20150317103806.GU8656@n2100.arm.linux.org.uk> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, 17 Mar 2015, Russell King - ARM Linux wrote: > On Tue, Mar 17, 2015 at 01:32:21AM -0700, Paul Walmsley wrote: > > Required properties: > > - compatible : For Tegra20, must contain "nvidia,tegra20-ahb". For > > - Tegra30, must contain "nvidia,tegra30-ahb". Otherwise, must contain > > - '"nvidia,-ahb", "nvidia,tegra30-ahb"' where is tegra124, > > - tegra132, or tegra210. > > -- reg : Should contain 1 register ranges(address and length) > > + Tegra30, must contain "nvidia,tegra30-ahb". For Tegra114 and Tegra124, must > > + contain '"nvidia,-ahb", "nvidia,tegra30-ahb"' where is tegra114 > > + or tegra124. For Tegra132, the compatible string must contain > > + "nvidia,tegra132-ahb". > > + > > +- reg : Should contain 1 register ranges(address and length). On Tegra20, > > + Tegra30, Tegra114, and Tegra124 chips, the low byte of the physical base > > + address of the IP block must end in 0x04. On DT files for later chips, the > > + actual hardware base address of the IP block should be used. > > You could check that in the driver. If you can check it in the driver, > you can also decide to ignore it if it were offset by 0x04 (possibly > printing a warning.) That opens up the ability to fix the older Tegra > DT files going forward while still remaining compatible with existing > DT files, and avoiding the need for a complex note about this. That's fine, I'll do that and drop this patch. - Paul