linux-kernel - Re: [PATCH 2/2] arm64: dts: renesas: r8a77961: ulcb-kf: Initial device tree

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 30 Oct 2020 10:07:28 +0100
From:   Eugeniu Rosca <erosca@...adit-jv.com>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
CC:     Eugeniu Rosca <erosca@...adit-jv.com>,
        Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
        Magnus Damm <magnus.damm@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Steffen Pengel <spengel@...adit-jv.com>,
        Eugeniu Rosca <roscaeugeniu@...il.com>
Subject: Re: [PATCH 2/2] arm64: dts: renesas: r8a77961: ulcb-kf: Initial
 device tree

Hi Geert,

On Thu, Oct 29, 2020 at 07:23:53PM +0100, Geert Uytterhoeven wrote:
> On Thu, Oct 29, 2020 at 5:34 PM Eugeniu Rosca <erosca@...adit-jv.com> wrote:

[..]

> I don't think we want to add new compatible string to describe each
> combo. Just add "renesas,r8a77961" to the last enum?

I'm afraid I misinterpreted your request. I've pushed your proposal to
https://lore.kernel.org/linux-renesas-soc/20201030083051.18752-4-erosca@de.adit-jv.com/

> > IMHO one thing which is certainly worth clarifying and fixing is the
> > KF revision currently documented in renesas.yaml, i.e. M03.
> >
> > Shimafuji released at least M04, M05 and M06 revisions of KF (nicely
> > compared at https://elinux.org/R-Car/Boards/Kingfisher#Change_point).
> >
> > The question is, does the community intend to support M03 through M06
> > (in which case all of them might need an entry in the documentation) or
> > anything which is earlier than M06 has to be considered deprecated (in
> > which case renesas.yaml would need a simple s/M03/M06/ update)?
> 
> I'm not that familiar with KingFisher and the various revisions.
> Do these differences have an impact on the software side?
> The diodes and filters probably don't.

I personally no longer use KF M03, since its major limitation is not
being able to update the contents of Hyperflash using Lauterbach if
ULCB is stacked on the expansion board (unplugging ULCB each time
it is flashed is absolutely not practical).

I've heard from audio engineers that recent revisions are more suitable
for audio use-cases, but I don't know the full details.

> The I2C repeaters are PCA9548ADB on M03, hence they use a Linux
> driver. By what have they been replaced?
> What's the nature of the MOST ↔ GPS Function select register change?

I will try to collect more information and, if I succeed, I will come
back with feedback. Thank you for your patience.

-- 
Best regards,
Eugeniu Rosca