From: Sascha Hauer <s.hauer@pengutronix.de>
To: Tim Sander <tim@krieglstein.org>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
Steffen Trumtrar <s.trumtrar@pengutronix.de>,
Trent Piepho <tpiepho@kymetacorp.com>
Subject: Re: [PATCH v3] Terasic DE0-Nano-SoC: add support
Date: Tue, 2 Feb 2016 15:15:42 +0100 [thread overview]
Message-ID: <20160202141542.GF4118@pengutronix.de> (raw)
In-Reply-To: <2242913.yZc50JEAEz@virgo>
Hi Tim,
On Tue, Feb 02, 2016 at 02:48:49PM +0100, Tim Sander wrote:
> On Monday 01 February 2016 19:31:53 Trent Piepho wrote:
> > On Mon, 2016-02-01 at 15:07 +0100, Tim Sander wrote:
> >
> > > v3: forgot to amend my changes in v2.
> > >
> > > +
> > > +static int socfpga_console_init(void)
> > > +{
> > > + if (!of_machine_is_compatible("altr,socfpga-cyclone5"))
> > > + return 0;
> >
> >
> > Seems like this should be a board specific check instead of a generic
> > one, since it's programming board specific phy timing values to a board
> > specific PHY.
> I am not sure, but as outlined below i think this is also due to the
> compatible string of the coresponding dts within the linux kernel.
> At least i first tried a more specific dts compatible string and that failed
> to boot.
You need to match for a board specific compatible here because this
function shall be executed for this board only, not for other boards.
This means you have to add a board specific compatible to the device
tree.
> > > +#include <arm/socfpga_cyclone5_de0_nano_soc.dts>
> > > +#include "socfpga.dtsi"
> > > +
> > > +/ {
> > > + model = "Terasic DE0-Nano-SoC (Atlas)";
> > > + compatible = "altr,socfpga-cyclone5", "altr,socfpga";
> >
> >
> > Wouldn't the right thing to do here be to have a compatible entry for
> > this board type? Like the existing "terasic,sockit" or something more
> > specific.
> Well the problem at this point is that due to the boardspecs the compatible
> string has to be AFAIK the same as the one used in the linux kernel.
> Unfortunatly the coresponding dts file also has no more specific compatible
> string.
The kernel matches for "altr,socfpga". You can add as many compatibles
before that as you like, just like the "altr,socfpga-cyclone5" string
which is present already and ignored by the kernel.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2016-02-02 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 11:23 [PATCH] Terasic DE0 NANO-SoC: " Tim Sander
2016-02-01 12:06 ` Steffen Trumtrar
2016-02-01 12:48 ` Antony Pavlov
2016-02-01 12:51 ` Tim Sander
2016-02-01 13:03 ` Steffen Trumtrar
2016-02-01 13:26 ` Tim Sander
2016-02-01 13:45 ` Steffen Trumtrar
2016-02-01 14:04 ` [PATCH v2] Terasic DE0-Nano-SoC: " Tim Sander
2016-02-01 14:07 ` [PATCH v3] " Tim Sander
2016-02-01 19:31 ` Trent Piepho
2016-02-02 13:48 ` Tim Sander
2016-02-02 14:15 ` Sascha Hauer [this message]
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=20160202141542.GF4118@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.trumtrar@pengutronix.de \
--cc=tim@krieglstein.org \
--cc=tpiepho@kymetacorp.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