linux-kernel - Re: [PATCH 00/12] mips: ralink: introduce '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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Tue, 14 Mar 2023 17:21:18 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Sergio Paracuellos <sergio.paracuellos@...il.com>
Cc:     linux-mips@...r.kernel.org, john@...ozen.org,
        linux-kernel@...r.kernel.org, git@...nthomson.fastmail.com.au
Subject: Re: [PATCH 00/12] mips: ralink: introduce 'soc_device' initialization

On Mon, Feb 27, 2023 at 11:57:54AM +0100, Sergio Paracuellos wrote:
> This series align old SoCs ralink code with current mt7621 code refactoring
> SoC related information into more readable functions as well as introducing
> 'soc_device' for all of them. This allows to be able to distinc SoC info
> from driver code without using architecture dependent includes. 
> 
> I am also planning to extract from ralink code current clock related stuff 
> into proper clk drivers at some time and be able to distinc SoC in this way
> let me to mark future drivers to be easily marked for COMPILE_TEST target.
> 
> Changes have been compile tested for:
> - RT2880
> - RT3883
> - MT7620
> 
> Changes have been properly tested in RT5350 SoC based board (ALL5003 board)
> resulting in a working platform.
> 
> Thanks in advance for your time.
> 
> Best regards,
>     Sergio Paracuellos
> 
> Sergio Paracuellos (12):
>   mips: ralink: rt305x: define RT305X_SYSC_BASE with __iomem
>   mips: ralink: rt305x: soc queries and tests as functions
>   mips: ralink: rt305x: introduce 'soc_device' initialization
>   mips: ralink: rt3883: define RT3883_SYSC_BASE with __iomem
>   mips: ralink: rt3883: soc queries and tests as functions
>   mips: ralink: rt3883: introduce 'soc_device' initialization
>   mips: ralink: rt288x: define RT2880_SYSC_BASE with __iomem
>   mips: ralink: rt288x: soc queries and tests as functions
>   mips: ralink: rt288x: introduce 'soc_device' initialization
>   mips: ralink: mt7620: define MT7620_SYSC_BASE with __iomem
>   mips: ralink: mt7620: soc queries and tests as functions
>   mips: ralink: mt7620: introduce 'soc_device' initialization
> 
>  arch/mips/include/asm/mach-ralink/mt7620.h |   3 +-
>  arch/mips/include/asm/mach-ralink/rt288x.h |   3 +-
>  arch/mips/include/asm/mach-ralink/rt305x.h |   3 +-
>  arch/mips/include/asm/mach-ralink/rt3883.h |   4 +-
>  arch/mips/ralink/Kconfig                   |   4 +
>  arch/mips/ralink/mt7620.c                  | 145 ++++++++++++++++----
>  arch/mips/ralink/rt288x.c                  |  94 ++++++++++---
>  arch/mips/ralink/rt305x.c                  | 147 +++++++++++++++++----
>  arch/mips/ralink/rt3883.c                  |  94 ++++++++++---
>  9 files changed, 410 insertions(+), 87 deletions(-)
> 
> -- 
> 2.25.1

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]