mbox series

[v3,0/9] mips: Support for RTL9302C

Message ID 20240627043317.3751996-1-chris.packham@alliedtelesis.co.nz (mailing list archive)
Headers show
Series mips: Support for RTL9302C | expand

Message

Chris Packham June 27, 2024, 4:33 a.m. UTC
This series adds basic support for the RTL9302C reference board. Currently the
focus is on the CPU block stuff. I hope to get around to the DSA switch driver
eventually but this is a small start that lets me boot a mainline kernel on the
board I have. I initialiy started with code from openwrt but have paired it
down to just the clocksource driver and devicetree.

The first two patches in this series are fixing some complaints from make
dtbs_check for some existing realtek dts files. They can be applied on their
own if desired.

Chris Packham (9):
  mips: dts: realtek: use "serial" instead of "uart" in node name
  mips: dts: realtek: add device_type property to cpu node
  dt-bindings: vendor-prefixes: Add Cameo Communications
  dt-bindings: mips: realtek: Add rtl930x-soc compatible
  dt-bindings: timer: Add schema for realtek,otto-timer
  dt-bindings: interrupt-controller: realtek,rtl-intc: Add rtl9300-intc
  clocksource: realtek: Add timer driver for rtl-otto platforms
  mips: generic: add fdt fixup for Realtek reference board
  mips: dts: realtek: Add RTL9302C board

 .../realtek,rtl-intc.yaml                     |  18 +-
 .../devicetree/bindings/mips/realtek-rtl.yaml |   4 +
 .../bindings/timer/realtek,otto-timer.yaml    |  63 ++++
 .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
 arch/mips/boot/dts/realtek/Makefile           |   1 +
 .../cameo-rtl9302c-2x-rtl8224-2xge.dts        |  73 +++++
 arch/mips/boot/dts/realtek/rtl838x.dtsi       |   1 +
 arch/mips/boot/dts/realtek/rtl83xx.dtsi       |   4 +-
 arch/mips/boot/dts/realtek/rtl930x.dtsi       |  79 +++++
 arch/mips/generic/Makefile                    |   1 +
 arch/mips/generic/board-realtek.c             |  81 +++++
 drivers/clocksource/Kconfig                   |  10 +
 drivers/clocksource/Makefile                  |   1 +
 drivers/clocksource/timer-rtl-otto.c          | 287 ++++++++++++++++++
 include/linux/cpuhotplug.h                    |   1 +
 15 files changed, 623 insertions(+), 3 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/timer/realtek,otto-timer.yaml
 create mode 100644 arch/mips/boot/dts/realtek/cameo-rtl9302c-2x-rtl8224-2xge.dts
 create mode 100644 arch/mips/boot/dts/realtek/rtl930x.dtsi
 create mode 100644 arch/mips/generic/board-realtek.c
 create mode 100644 drivers/clocksource/timer-rtl-otto.c

Comments

Rob Herring (Arm) June 27, 2024, 2:42 p.m. UTC | #1
On Wed, Jun 26, 2024 at 10:33 PM Chris Packham
<chris.packham@alliedtelesis.co.nz> wrote:
>
> This series adds basic support for the RTL9302C reference board. Currently the
> focus is on the CPU block stuff. I hope to get around to the DSA switch driver
> eventually but this is a small start that lets me boot a mainline kernel on the
> board I have. I initialiy started with code from openwrt but have paired it
> down to just the clocksource driver and devicetree.

Your emails are being sent as quoted-printable encoding which is
generally preferred to be avoided on maillists (as is base64).
git-send-email should normally use 8-bit encoding, but the man page
indicates QP may be used if there are carriage returns (there
shouldn't be).

Rob
Chris Packham June 30, 2024, 11:43 p.m. UTC | #2
On 28/06/24 02:42, Rob Herring wrote:
> On Wed, Jun 26, 2024 at 10:33 PM Chris Packham
> <chris.packham@alliedtelesis.co.nz> wrote:
>> This series adds basic support for the RTL9302C reference board. Currently the
>> focus is on the CPU block stuff. I hope to get around to the DSA switch driver
>> eventually but this is a small start that lets me boot a mainline kernel on the
>> board I have. I initialiy started with code from openwrt but have paired it
>> down to just the clocksource driver and devicetree.
> Your emails are being sent as quoted-printable encoding which is
> generally preferred to be avoided on maillists (as is base64).
> git-send-email should normally use 8-bit encoding, but the man page
> indicates QP may be used if there are carriage returns (there
> shouldn't be).

Hmm here's the output from when I sent this series.

Subject: [PATCH v3 0/9] mips: Support for RTL9302C
Date: Thu, 27 Jun 2024 16:33:08 +1200
Message-ID: <20240627043317.3751996-1-chris.packham@alliedtelesis.co.nz>
X-Mailer: git-send-email 2.45.2
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

All the patches are also 8bit. So I think git chose the right thing.

I do keep needing to convince Thunderbird to send my replies as plain 
text. Occasionally I forget and vger complains at me.
Chris Packham July 1, 2024, 3:26 a.m. UTC | #3
On 1/07/24 11:43, Chris Packham wrote:
>
> On 28/06/24 02:42, Rob Herring wrote:
>> On Wed, Jun 26, 2024 at 10:33 PM Chris Packham
>> <chris.packham@alliedtelesis.co.nz> wrote:
>>> This series adds basic support for the RTL9302C reference board. 
>>> Currently the
>>> focus is on the CPU block stuff. I hope to get around to the DSA 
>>> switch driver
>>> eventually but this is a small start that lets me boot a mainline 
>>> kernel on the
>>> board I have. I initialiy started with code from openwrt but have 
>>> paired it
>>> down to just the clocksource driver and devicetree.
>> Your emails are being sent as quoted-printable encoding which is
>> generally preferred to be avoided on maillists (as is base64).
>> git-send-email should normally use 8-bit encoding, but the man page
>> indicates QP may be used if there are carriage returns (there
>> shouldn't be).
>
> Hmm here's the output from when I sent this series.
>
> Subject: [PATCH v3 0/9] mips: Support for RTL9302C
> Date: Thu, 27 Jun 2024 16:33:08 +1200
> Message-ID: <20240627043317.3751996-1-chris.packham@alliedtelesis.co.nz>
> X-Mailer: git-send-email 2.45.2
> MIME-Version: 1.0
> Content-Transfer-Encoding: 8bit
>
> All the patches are also 8bit. So I think git chose the right thing.
>
> I do keep needing to convince Thunderbird to send my replies as plain 
> text. Occasionally I forget and vger complains at me.

I did a bit of digging. My replies are indeed being sent as 
quoted-printable and get base64 encoded by the time they hit lore e.g. 
https://lore.kernel.org/all/68a574c0-2775-4275-b590-b7f362ae3885@alliedtelesis.co.nz/raw 
(not sure where that's happening).

There are some suggestions for older versions of Thunderbird but none of 
the options exist for me. It seems I'm not the only one with an issue 
https://www.reddit.com/r/Thunderbird/comments/18drd4p/how_to_set_contenttransferencoding/

I'll keep looking but if anyone knows how to tame Thunderbird that'd be 
a great help.