From: Dmitry Osipenko <digetx@gmail.com>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Matt Merhar <mattmerhar@protonmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Bob Ham <rah@settrans.net>, Leonardo Bras <leobras.c@gmail.com>,
Michael Brougham <jusplainmike@gmail.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ARM: tegra: Add device-tree for Ouya
Date: Wed, 16 Sep 2020 19:09:02 +0300 [thread overview]
Message-ID: <c92a457d-9829-99ce-8d7c-29fe5395728c@gmail.com> (raw)
In-Reply-To: <CAMdYzYrKHBrh47PMrj=TP_FPttFOkRO2J_wrDr7oEyBNnyexAA@mail.gmail.com>
16.09.2020 17:57, Peter Geis пишет:
> On Wed, Sep 16, 2020 at 10:17 AM Dmitry Osipenko <digetx@gmail.com> wrote:
>>
>> 16.09.2020 15:22, Peter Geis пишет:
>>> The Ouya was the sole device produced by Ouya Inc in 2013.
>>> It was a game console originally running Android 5 on top of Linux 3.1.10.
>>>
>>> This patch adds the device tree supporting the Ouya.
>>> It has been tested on the original variant with Samsung ram.
>>>
>>> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
>>> ---
>>> arch/arm/boot/dts/Makefile | 3 +-
>>> arch/arm/boot/dts/tegra30-ouya.dts | 4498 ++++++++++++++++++++++++++++
>>> 2 files changed, 4500 insertions(+), 1 deletion(-)
>>> create mode 100644 arch/arm/boot/dts/tegra30-ouya.dts
>>
>> Hello, Peter! Very nice work!
>
> Thanks!
>
>>
>> Could you please clarify how many variants of the board exist?
>
> It is unknown how many exist in reality.
> At least three RAM variants are supported in the downstream kernel,
> Samsung, Hynix M, and Hynix A.
> Two variants in storage capacity, the original had 8GB eMMC while the
> new variant had 16GB eMMC.
>
>>
>> What are the differences between the variants?
>
> Aside from the RAM and storage changes there should be no functional
> differences.
> It is unknown at which point the RAM changes were cut in with the eMMC change.
>
>>
>> Is this device-tree suitable for all variants?
>
> This device tree should support all variants, but I haven't been able
> to locate anyone with the newer variants who can test it yet.
>
>>
>> How user could determine the board's variant?
>
> On upstream:
> The tegra emc driver will output the RAM code detected in the kernel log:
> tegra30-emc 7000f400.memory-controller: got 6 timings for RAM code 0
> (min 25MHz max 800MHz)
> The mmc-core will output the storage capacity in the kernel log:
> mmcblk1: mmc1:0001 MMC08G 7.19 GiB
>
> On downstream:
> The ram variant is output in the kernel log:
> DDR Strap Pin AD4: 0
> DDR Strap Pin AD5: 0
> Init DFS table for Samsung DDR
> The mmc-core outputs the storage capacity in the kernel log:
> mmcblk0: mmc0:0001 MMC08G 7.18 GiB
>
I was thinking that maybe it could be necessary to separate the DT per
board variant, like we did it for Nexus 7, but it shouldn't be needed
given yours answer.
So far looks good to me!
next prev parent reply other threads:[~2020-09-16 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 12:22 [PATCH 0/3] Support NVIDIA Tegra-based Ouya game console Peter Geis
2020-09-16 12:22 ` [PATCH 1/3] ARM: tegra: Add device-tree for Ouya Peter Geis
2020-09-16 14:17 ` Dmitry Osipenko
2020-09-16 14:57 ` Peter Geis
2020-09-16 16:09 ` Dmitry Osipenko [this message]
2020-09-23 15:46 ` Rob Herring
2020-09-23 20:30 ` Peter Geis
2020-09-16 12:22 ` [PATCH 2/3] dt-bindings: Add vendor prefix for Ouya Inc Peter Geis
2020-09-23 15:46 ` Rob Herring
2020-09-16 12:22 ` [PATCH 3/3] dt-bindings: ARM: tegra: Add Ouya game console Peter Geis
2020-09-23 15:46 ` Rob Herring
2020-09-16 17:43 ` [PATCH 0/3] Support NVIDIA Tegra-based " Leonardo Bras
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=c92a457d-9829-99ce-8d7c-29fe5395728c@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=jusplainmike@gmail.com \
--cc=leobras.c@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=pgwipeout@gmail.com \
--cc=rah@settrans.net \
--cc=robh+dt@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).