From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
Cc: "agraf@suse.de" <agraf@suse.de>,
"Andreas Färber" <afaerber@suse.de>,
"Mark Rutland" <Mark.Rutland@arm.com>,
"Thomas Lendacky" <Thomas.Lendacky@amd.com>,
"Joel Schopp" <Joel.Schopp@amd.com>,
"Marc Zyngier" <Marc.Zyngier@arm.com>,
"Catalin Marinas" <Catalin.Marinas@arm.com>,
"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>,
"Will Deacon" <Will.Deacon@arm.com>,
"Rob Herring" <robh+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: amd-seattle: Adding device tree for AMD Seattle platform
Date: Thu, 30 Oct 2014 13:33:36 +0000 [thread overview]
Message-ID: <20141030133335.GK1069@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <544F9525.80304@amd.com>
On Tue, Oct 28, 2014 at 01:07:49PM +0000, Suravee Suthikulanit wrote:
> On 10/27/2014 6:25 PM, Alexander Graf wrote:
> >
> >
> > On 27.10.14 15:29, Suravee Suthikulanit wrote:
> >> On 10/26/2014 9:08 AM, Alexander Graf wrote:
> >>>>> This option doesn't exist in upstream kernels, does it? Why not just
> >>>>>>> make it dtb-y?
> >>>>>
> >>>>> CONFIG_ARCH_SEATTLE is being added one hunk above.:)
> >>> Oops:).
> >>>
> >>> I'm not convinced we need a config option just for the sake of
> >>> compiling a device tree though.
> >>>
> >>>
> >>> Alex
> >>>
> >>
> >> Eventually, we would add other device driver selections when
> >> CONFIG_ARCH_SEATTLE=y. At this point, those drivers are still not ready.
> >
> > Could you please give me some examples of drivers that would depend on
> > CONFIG_ARCH_SEATTLE? I like the current way things work without the need
> > for such an option, where everything's implemented purely as drivers you
> > can opt in our out of.
> >
> > You don't have a CONFIG_ARCH_SB7XX on x86 either, right? ;)
> >
> >
> > Alex
> >
>
> I am not saying that device drivers need to depend on
> CONFIG_ARCH_SEATTLE. I am thinking along the line of an easy way to
> enable SOC without having to manually select each of the required
> drivers to support the SOC. An example is the "ARCH_VEXPRESS".
ARCH_VEXPRESS is an historical artifact and we have discussed a few times
internally in ARM to remove it as it brings no value until some other platform
can't work with the default options comes in.
I agree with Alexander here, I think the device tree should be compiled
in regardless. One reason for it is because it will make it easier to
dis-entangle the .dt{s,b} files from the tree in the future and have them
hosted in a different place.
Best regards,
Liviu
>
> Suravee
>
>
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
next prev parent reply other threads:[~2014-10-30 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 12:20 suravee.suthikulpanit
2014-10-25 23:08 ` Alexander Graf
2014-10-26 12:43 ` Andreas Färber
2014-10-26 14:08 ` Alexander Graf
2014-10-27 14:29 ` Suravee Suthikulanit
2014-10-27 23:25 ` Alexander Graf
2014-10-28 13:07 ` Suravee Suthikulanit
2014-10-28 14:30 ` Alexander Graf
2014-10-30 13:33 ` Liviu Dudau [this message]
2014-10-26 14:09 ` Andreas Färber
2014-10-27 14:30 ` Suravee Suthikulanit
2014-10-27 13:50 ` Mark Rutland
2014-10-27 18:34 ` Suravee Suthikulanit
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=20141030133335.GK1069@e106497-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Joel.Schopp@amd.com \
--cc=Marc.Zyngier@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Thomas.Lendacky@amd.com \
--cc=Will.Deacon@arm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®