From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: linux-mips@vger.kernel.org, john@phrozen.org,
linux-kernel@vger.kernel.org, git@johnthomson.fastmail.com.au
Subject: Re: [PATCH 00/12] mips: ralink: introduce 'soc_device' initialization
Date: Tue, 14 Mar 2023 17:21:18 +0100 [thread overview]
Message-ID: <20230314162118.GD18446@alpha.franken.de> (raw)
In-Reply-To: <20230227105806.2394101-1-sergio.paracuellos@gmail.com>
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 ]
prev parent reply other threads:[~2023-03-14 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:57 [PATCH 00/12] mips: ralink: introduce 'soc_device' initialization Sergio Paracuellos
2023-02-27 10:57 ` [PATCH 01/12] mips: ralink: rt305x: define RT305X_SYSC_BASE with __iomem Sergio Paracuellos
2023-02-27 10:57 ` [PATCH 02/12] mips: ralink: rt305x: soc queries and tests as functions Sergio Paracuellos
2023-02-27 10:57 ` [PATCH 03/12] mips: ralink: rt305x: introduce 'soc_device' initialization Sergio Paracuellos
2023-02-27 10:57 ` [PATCH 04/12] mips: ralink: rt3883: define RT3883_SYSC_BASE with __iomem Sergio Paracuellos
2023-02-27 10:57 ` [PATCH 05/12] mips: ralink: rt3883: soc queries and tests as functions Sergio Paracuellos
2023-02-27 10:58 ` [PATCH 06/12] mips: ralink: rt3883: introduce 'soc_device' initialization Sergio Paracuellos
2023-02-27 10:58 ` [PATCH 07/12] mips: ralink: rt288x: define RT2880_SYSC_BASE with __iomem Sergio Paracuellos
2023-02-27 10:58 ` [PATCH 08/12] mips: ralink: rt288x: soc queries and tests as functions Sergio Paracuellos
2023-02-27 10:58 ` [PATCH 09/12] mips: ralink: rt288x: introduce 'soc_device' initialization Sergio Paracuellos
2023-02-27 10:58 ` [PATCH 10/12] mips: ralink: mt7620: define MT7620_SYSC_BASE with __iomem Sergio Paracuellos
2023-02-27 10:58 ` [PATCH 11/12] mips: ralink: mt7620: soc queries and tests as functions Sergio Paracuellos
2023-02-27 10:58 ` [PATCH 12/12] mips: ralink: mt7620: introduce 'soc_device' initialization Sergio Paracuellos
2023-03-14 16:21 ` Thomas Bogendoerfer [this message]
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=20230314162118.GD18446@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=git@johnthomson.fastmail.com.au \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=sergio.paracuellos@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.