public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: lee@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, andi.shyti@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mips@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v9 2/4] mips: dts: realtek: Add syscon-reboot node
Date: Tue, 12 Nov 2024 15:56:10 +0100	[thread overview]
Message-ID: <ZzNsiu+rbYs7l9Wb@alpha.franken.de> (raw)
In-Reply-To: <20241106001835.2725522-3-chris.packham@alliedtelesis.co.nz>

On Wed, Nov 06, 2024 at 01:18:33PM +1300, Chris Packham wrote:
> The board level reset on systems using the RTL9302 can be driven via the
> switch. Use a syscon-reboot node to represent this.
> 
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> 
> Notes:
>     Changes in v9:
>     - None
>     Changes in v8:
>     - None
>     Changes in v7:
>     - None
>     Changes in v6:
>     - Drop wildcard compatible
>     Changes in v5:
>     - Krzysztof did technically give a r-by on v4 but given the changes to
>       the rest of the series I haven't included it.
>     - Use reg instead of offset
>     - Add a rtl9302c.dtsi for the specific chip which pulls in the generic
>       rtl930x.dtsi and updates a few of the compatibles on the way through.
>     - Update Cameo board to use rtl9302c.dtsi
>     Changes in v4:
>     - None
>     Changes in v3:
>     - None
>     Changes in v2:
>     - drop redundant status = "okay"
> 
>  .../dts/realtek/cameo-rtl9302c-2x-rtl8224-2xge.dts  |  2 +-
>  arch/mips/boot/dts/realtek/rtl9302c.dtsi            |  7 +++++++
>  arch/mips/boot/dts/realtek/rtl930x.dtsi             | 13 +++++++++++++
>  3 files changed, 21 insertions(+), 1 deletion(-)
>  create mode 100644 arch/mips/boot/dts/realtek/rtl9302c.dtsi

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 ]

  reply	other threads:[~2024-11-12 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  0:18 [PATCH v9 0/4] RTL9300 support for reboot and i2c Chris Packham
2024-11-06  0:18 ` [PATCH v9 1/4] dt-bindings: mfd: Add Realtek RTL9300 switch peripherals Chris Packham
2024-11-06  1:29   ` Rob Herring (Arm)
2024-11-06  0:18 ` [PATCH v9 2/4] mips: dts: realtek: Add syscon-reboot node Chris Packham
2024-11-12 14:56   ` Thomas Bogendoerfer [this message]
2024-11-06  0:18 ` [PATCH v9 3/4] mips: dts: realtek: Add I2C controllers Chris Packham
2024-11-12 14:56   ` Thomas Bogendoerfer
2024-11-06  0:18 ` [PATCH v9 4/4] i2c: Add driver for the RTL9300 I2C controller Chris Packham
2024-11-06  9:57   ` Andi Shyti
2024-11-06 19:47     ` Chris Packham
2024-11-06 22:51       ` Andi Shyti

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=ZzNsiu+rbYs7l9Wb@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=andi.shyti@kernel.org \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=robh@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox