From: Paul Kocialkowski <contact@paulk.fr>
To: Jon Hunter <jonathanh@nvidia.com>, linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-tegra@vger.kernel.org, Alexandre Courbot <gnurou@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] ARM: tegra: nyan-big: Include compatible revisions for proper detection
Date: Tue, 20 Sep 2016 19:53:24 +0200 [thread overview]
Message-ID: <1474394004.1215.2.camel@paulk.fr> (raw)
In-Reply-To: <a9485a88-55a5-9dd1-1a1b-a6c0a78ff476@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
Le mardi 20 septembre 2016 à 18:41 +0100, Jon Hunter a écrit :
> On 28/08/16 18:32, Paul Kocialkowski wrote:
> >
> > Depthcharge (the payload used with cros devices) will attempt to detect
> > boards using their revision. This includes all the known revisions for
> > the nyan-big board so that the dtb can be selected preferably.
>
> May be I am missing something here, but for the mainline there is only
> one dtb available and so why is this needed for the mainline?
There is indeed a single dts in mainline, but depthcharge will use the revision
to match the compatible string (e.g. it will look for google,nyan-big-rev5, not
google,nyan-big), so we need to list them all in that single dts. Otherwise,
depthcharge will fall back to the default config, which may or may not be
suitable for nyan.
--
Paul Kocialkowski, developer of low-level free software for embedded devices
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-09-20 17:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 17:32 [PATCH 1/4] ARM: tegra: nyan: Use proper IRQ type definitions Paul Kocialkowski
2016-08-28 17:32 ` [PATCH 2/4] ARM: tegra: nyan: Use external control for bq24735 charger Paul Kocialkowski
2016-09-20 17:40 ` Jon Hunter
2016-09-20 18:02 ` Paul Kocialkowski
2016-09-21 7:30 ` Jon Hunter
2016-09-21 7:56 ` Paul Kocialkowski
2016-09-21 10:10 ` Jon Hunter
2016-09-21 11:03 ` Paul Kocialkowski
2016-08-28 17:32 ` [PATCH 3/4] ARM: tegra: nyan-big: Include compatible revisions for proper detection Paul Kocialkowski
2016-09-20 17:41 ` Jon Hunter
2016-09-20 17:53 ` Paul Kocialkowski [this message]
2016-09-20 17:56 ` Jon Hunter
2016-09-20 18:02 ` Paul Kocialkowski
2016-09-21 7:34 ` Jon Hunter
2016-09-21 7:43 ` Paul Kocialkowski
2016-09-21 9:15 ` Jon Hunter
2016-09-21 9:31 ` Paul Kocialkowski
2016-08-28 17:32 ` [PATCH 4/4] ARM: tegra: nyan-blaze: " Paul Kocialkowski
2016-09-20 17:42 ` Jon Hunter
2016-09-20 17:15 ` [PATCH 1/4] ARM: tegra: nyan: Use proper IRQ type definitions Jon Hunter
2016-09-20 18:14 ` Paul Kocialkowski
2016-09-21 7:52 ` Jon Hunter
2016-09-21 8:26 ` Paul Kocialkowski
2016-09-21 9:06 ` Jon Hunter
2016-09-21 9:31 ` Paul Kocialkowski
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=1474394004.1215.2.camel@paulk.fr \
--to=contact@paulk.fr \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).