All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: realview: basic device tree implementation
Date: Thu, 22 May 2014 15:36:01 +0200	[thread overview]
Message-ID: <5376959.IId6jNFDDg@wuerfel> (raw)
In-Reply-To: <CACRpkdaqsVUDA+6NC=EQmxcnDAnJEfPNYoptrEv=nq=eZEbA_g@mail.gmail.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Marc Zyngier <marc.zyngier-5wv7dgnIgG8@public.gmane.org>,
	Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Subject: Re: [PATCH v2] ARM: realview: basic device tree implementation
Date: Thu, 22 May 2014 15:36:01 +0200	[thread overview]
Message-ID: <5376959.IId6jNFDDg@wuerfel> (raw)
In-Reply-To: <CACRpkdaqsVUDA+6NC=EQmxcnDAnJEfPNYoptrEv=nq=eZEbA_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.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

  reply	other threads:[~2014-05-22 13:36 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 22:08 [PATCH v2] ARM: realview: basic device tree implementation Linus Walleij
2014-05-08 22:08 ` Linus Walleij
2014-05-09 10:44 ` Arnd Bergmann
2014-05-09 10:44   ` Arnd Bergmann
2014-05-22  7:41   ` Linus Walleij
2014-05-22  7:41     ` Linus Walleij
2014-05-22  8:31     ` Arnd Bergmann
2014-05-22  8:31       ` Arnd Bergmann
2014-05-22 13:04       ` Linus Walleij
2014-05-22 13:04         ` Linus Walleij
2014-05-22 13:38         ` Arnd Bergmann
2014-05-22 13:38           ` Arnd Bergmann
2014-05-22 14:45       ` Catalin Marinas
2014-05-22 14:45         ` Catalin Marinas
2014-05-22 15:49         ` Arnd Bergmann
2014-05-22 15:49           ` Arnd Bergmann
2014-05-22 16:09           ` Catalin Marinas
2014-05-22 16:09             ` Catalin Marinas
2014-05-22 18:09           ` Nicolas Pitre
2014-05-22 18:09             ` Nicolas Pitre
2014-05-22 18:26             ` Arnd Bergmann
2014-05-22 18:26               ` Arnd Bergmann
2014-05-22 18:39               ` Nicolas Pitre
2014-05-22 18:39                 ` Nicolas Pitre
2014-05-22 20:25                 ` Arnd Bergmann
2014-05-22 20:25                   ` Arnd Bergmann
2014-05-22 18:52           ` Linus Walleij
2014-05-22 18:52             ` Linus Walleij
2014-05-22 20:35             ` Arnd Bergmann
2014-05-22 20:35               ` Arnd Bergmann
2014-05-29  9:38               ` Linus Walleij
2014-05-29  9:38                 ` Linus Walleij
2014-05-22 22:34     ` Sebastian Hesselbarth
2014-05-22 22:34       ` Sebastian Hesselbarth
2014-05-29  9:44       ` Linus Walleij
2014-05-29  9:44         ` Linus Walleij
2014-05-29 10:10         ` Sebastian Hesselbarth
2014-05-29 10:10           ` Sebastian Hesselbarth
2014-05-29 14:13           ` Linus Walleij
2014-05-29 14:13             ` Linus Walleij
2014-05-29 14:47             ` Sebastian Hesselbarth
2014-05-29 14:47               ` Sebastian Hesselbarth
2014-05-22 13:17 ` Rob Herring
2014-05-22 13:17   ` Rob Herring
2014-05-22 13:30   ` Linus Walleij
2014-05-22 13:30     ` Linus Walleij
2014-05-22 13:36     ` Arnd Bergmann [this message]
2014-05-22 13:36       ` Arnd Bergmann
2014-05-28 22:47       ` Rob Herring
2014-05-22 13:41 ` Jason Cooper
2014-05-22 13:41   ` Jason Cooper

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=5376959.IId6jNFDDg@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.