netdev - Re: [PATCHv4 2/3] net: dsa: mt7530: support the 7530 switch on the Mediatek MT7621 SoC

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]

Message-ID: <d030fb8f-c707-9aa2-5ebc-e8100188a5c2@gmail.com>
Date:   Tue, 29 Jan 2019 19:39:27 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     gerg@...nel.org, sean.wang@...iatek.com,
        linux-mediatek@...ts.infradead.org, bjorn@...k.no, andrew@...n.ch,
        vivien.didelot@...oirfairelinux.com, netdev@...r.kernel.org
Cc:     rene@...rst.com, john@...ozen.org, neil@...wn.name
Subject: Re: [PATCHv4 2/3] net: dsa: mt7530: support the 7530 switch on the
 Mediatek MT7621 SoC



On 1/29/19 5:24 PM, gerg@...nel.org wrote:
> From: Greg Ungerer <gerg@...nel.org>
> 
> The MediaTek MT7621 SoC device contains a 7530 switch, and the existing
> linux kernel 7530 DSA switch driver can be used with it.
> 
> The bulk of the changes required stem from the 7621 having different
> regulator and pad setup. The existing setup of these in the 7530
> driver appears to be very specific to its implemtation in the Mediatek
> 7623 SoC. (Not entirely surprising given the 7623 is a quad core ARM
> based SoC, and the 7621 is a dual core, dual thread MIPS based SoC).
> 
> Create a new devicetree type, "mediatek,mt7621", to support the 7530
> switch in the 7621 SoC. There appears to be no usable ID register to
> distinguish it from a 7530 in other hardware at runtime. This is used
> to carry out the appropriate configuration and setup.
> 
> Signed-off-by: Greg Ungerer <gerg@...nel.org>
> Reviewed-by: Andrew Lunn <andrew@...n.ch>

Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
-- 
Florian