From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [RFC PATCH 5/6] arm64: dts: ti: Add Support for AM654 SoC Date: Tue, 5 Jun 2018 07:14:30 -0700 Message-ID: <20180605141430.GE5738@atomide.com> References: <20180605060510.32473-1-nm@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring Cc: Nishanth Menon , Santosh Shilimkar , Will Deacon , Catalin Marinas , Greg Kroah-Hartman , Mark Rutland , "open list:SERIAL DRIVERS" , "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Vignesh R , Tero Kristo , Russell King , Sudeep Holla List-Id: linux-serial@vger.kernel.org * Rob Herring [180605 14:08]: > On Tue, Jun 5, 2018 at 1:05 AM, Nishanth Menon wrote: > > + soc0: soc0 { > > + compatible = "simple-bus"; > > + #address-cells = <2>; > > + #size-cells = <2>; > > + ranges; > > Really need 64-bit addresses and sizes? Use ranges to limit the > address space if possible. And in addition to using ranges, please set up separate bus instances for the interconnects. This will then allow you to probe WKUP or similar instance first and the other bus instances after. And that pretty much allows you to get rid of the annoying -EPROBE_DEFER ping pong and allows making clocks proper device drivers ;) Regards, Tony From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Tue, 5 Jun 2018 07:14:30 -0700 Subject: [RFC PATCH 5/6] arm64: dts: ti: Add Support for AM654 SoC In-Reply-To: References: <20180605060510.32473-1-nm@ti.com> Message-ID: <20180605141430.GE5738@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Rob Herring [180605 14:08]: > On Tue, Jun 5, 2018 at 1:05 AM, Nishanth Menon wrote: > > + soc0: soc0 { > > + compatible = "simple-bus"; > > + #address-cells = <2>; > > + #size-cells = <2>; > > + ranges; > > Really need 64-bit addresses and sizes? Use ranges to limit the > address space if possible. And in addition to using ranges, please set up separate bus instances for the interconnects. This will then allow you to probe WKUP or similar instance first and the other bus instances after. And that pretty much allows you to get rid of the annoying -EPROBE_DEFER ping pong and allows making clocks proper device drivers ;) Regards, Tony