lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 16 May 2020 15:01:00 +0300
From:   Dmitry Osipenko <>
To:     Michał Mirosław <>
Cc:     Rob Herring <>,
        Thierry Reding <>,
        Jonathan Hunter <>,
        David Heidelberg <>,
        Peter Geis <>,
        Stephen Warren <>,
        Nicolas Chauvet <>,
        Pedro Ângelo <>,
        Matt Merhar <>,
        Zack Pearsall <>,,,
Subject: Re: [PATCH v8 2/6] ARM: tegra: Add device-tree for ASUS Google Nexus

15.05.2020 21:18, Michał Mirosław пишет:
> On Fri, May 15, 2020 at 12:36:50AM +0300, Dmitry Osipenko wrote:
>> There are few hardware variants of NVIDIA Tegra30-based Nexus 7 device:
>> 1. WiFi-only (named Grouper)
>> 2. GSM (named Tilapia)
>> 3. Using Maxim PMIC (E1565 board ID)
>> 4. Using Ti PMIC (PM269 board ID)
> Hi,
> I've briefly looked at the PM269 devicetree (PMIC part) and it looks very
> similar, if not the same, to what I deduced from the TF300T kernel.

Hello Michał,

Definitely there are board parts that are reused by different devices.
This is not surprising since most of the boards are designed by the same

> Those devices don't look to differ much from original Cardhu tablet
> devkit, so maybe the trees can base off of that?

I don't think it's really possible in a case of Nexus 7 because in
overall the used hardware components differ a bit too much. It shouldn't
worth the effort, IMO.

> I would also guess that because of this 'ram-code', memory timings would
> be duplicated between devices. I can see small differences between
> ram-code=1 timings of Grouper and TF300T, though they look like arbiter
> tuning differences. I'll have to test if my TF300T works with Grouper's
> settings. In case they work, could you split the memory timings to another
> dtsi file?

Yes, perhaps this could be done. The memory timings on Grouper and
Tilapia are pretty much the same as well. As you noticed, there are some
tuning differences of TF300T in comparison to the Nexus 7, the same
applies to the Grouper and Tilapia variants.

> BTW, shouldn't EMC timing set match MC? I see more frequencies listed in
> MC than EMC nodes.

The MC timings are exactly the same on Grouper and Tilapia, but EMC
timings have a very minor differences, and thus, the common.dtsi misses
these differentiating EMC timings, they are defined in grouper.dtsi and

I guess we indeed could try to select the lowest common denominator
timing and re-use it. I'll consider this change for v9, thank you very
much for the suggestion.

Powered by blists - more mailing lists