From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH v2] ARM: realview: basic device tree implementation Date: Thu, 22 May 2014 15:36:01 +0200 Message-ID: <5376959.IId6jNFDDg@wuerfel> References: <1399586896-16906-1-git-send-email-linus.walleij@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Linus Walleij Cc: Rob Herring , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Pawel Moll , Mark Rutland , Marc Zyngier , Will Deacon , Thomas Gleixner List-Id: devicetree@vger.kernel.org On Thursday 22 May 2014 15:30:39 Linus Walleij wrote: > >> + parent = soc_device_to_device(soc_dev); > > > > We really need to standardize this soc device stuff so that platforms > > always have a parent soc device or not. > > Arnds position is that the entire platform/board should not be > a "soc device" and that seems correct since the board is no SoC. > > So I will spin this off into a SoC driver and push under > drivers/soc and bind to the SoC node in the device tree. To be clear, this has nothing to do with whether this is strictly a SoC or not. I would still want to see all the internal components of the main chip under the soc node, and probably anything that is attached to one of its interfaces under those nodes. The parts that should not be under /soc are the ones that are not in the device hierarchy, such as external clock generators. Arnd -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html