All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: Hal Feng <hal.feng@starfivetech.com>,
	Conor Dooley <conor.dooley@microchip.com>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Ben Dooks <ben.dooks@sifive.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>,
	Emil Renner Berthing <emil.renner.berthing@canonical.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/19] Basic clock, reset & device tree support for StarFive JH7110 RISC-V SoC
Date: Wed, 8 Mar 2023 13:36:41 +0000	[thread overview]
Message-ID: <4c071642-e3c8-4716-a580-5b42e25efb1c@spud> (raw)
In-Reply-To: <ZAh/UeSlUeGoKxki@tom-HP-ZBook-Fury-15-G7-Mobile-Workstation>


[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]

On Wed, Mar 08, 2023 at 01:28:01PM +0100, Tommaso Merciai wrote:
> On Tue, Mar 07, 2023 at 06:08:53PM +0800, Hal Feng wrote:

> > The above two methods can fix the problem. Here are my test results.
> > The VisionFive board can boot up successfully if and only if all above
> > two applied.
> > The VisionFive 2 board can boot up successfully if I merge Linus's new
> > changes.
> 
> Tested also on my side. Hope this can be helpfull.
> 
> > Hope your fix will be merged in rc2. Thank you for your reply.
> 
> Fully agree.

If you only have a VisionFive 2, it shouldn't matter to you, as you
don't need to fix up any SiFive errata (at the moment at least).
Linus' fix is already in his tree, so should be in -rc2!
The fix for the VisionFive was applied to Palmer's RISC-V fixes tree
last night:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/?h=fixes&id=bf89b7ee52af5a5944fa3539e86089f72475055b

Thanks,
Conor.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: Hal Feng <hal.feng@starfivetech.com>,
	Conor Dooley <conor.dooley@microchip.com>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Ben Dooks <ben.dooks@sifive.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>,
	Emil Renner Berthing <emil.renner.berthing@canonical.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/19] Basic clock, reset & device tree support for StarFive JH7110 RISC-V SoC
Date: Wed, 8 Mar 2023 13:36:41 +0000	[thread overview]
Message-ID: <4c071642-e3c8-4716-a580-5b42e25efb1c@spud> (raw)
In-Reply-To: <ZAh/UeSlUeGoKxki@tom-HP-ZBook-Fury-15-G7-Mobile-Workstation>

[-- Attachment #1: Type: text/plain, Size: 959 bytes --]

On Wed, Mar 08, 2023 at 01:28:01PM +0100, Tommaso Merciai wrote:
> On Tue, Mar 07, 2023 at 06:08:53PM +0800, Hal Feng wrote:

> > The above two methods can fix the problem. Here are my test results.
> > The VisionFive board can boot up successfully if and only if all above
> > two applied.
> > The VisionFive 2 board can boot up successfully if I merge Linus's new
> > changes.
> 
> Tested also on my side. Hope this can be helpfull.
> 
> > Hope your fix will be merged in rc2. Thank you for your reply.
> 
> Fully agree.

If you only have a VisionFive 2, it shouldn't matter to you, as you
don't need to fix up any SiFive errata (at the moment at least).
Linus' fix is already in his tree, so should be in -rc2!
The fix for the VisionFive was applied to Palmer's RISC-V fixes tree
last night:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/?h=fixes&id=bf89b7ee52af5a5944fa3539e86089f72475055b

Thanks,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-03-08 13:37 UTC|newest]

Thread overview: 143+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21  2:46 [PATCH v4 00/19] Basic clock, reset & device tree support for StarFive JH7110 RISC-V SoC Hal Feng
2023-02-21  2:46 ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 01/19] clk: starfive: Factor out common JH7100 and JH7110 code Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 02/19] clk: starfive: Rename clk-starfive-jh7100.h to clk-starfive-jh71x0.h Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 03/19] clk: starfive: Rename "jh7100" to "jh71x0" for the common code Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 04/19] reset: Create subdirectory for StarFive drivers Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 05/19] reset: starfive: Factor out common JH71X0 reset code Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 17:10   ` Conor Dooley
2023-02-21 17:10     ` Conor Dooley
2023-02-21  2:46 ` [PATCH v4 06/19] reset: starfive: Extract the " Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 17:13   ` Conor Dooley
2023-02-21 17:13     ` Conor Dooley
2023-02-21  2:46 ` [PATCH v4 07/19] reset: starfive: Rename "jh7100" to "jh71x0" for the common code Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 17:17   ` Conor Dooley
2023-02-21 17:17     ` Conor Dooley
2023-02-21  2:46 ` [PATCH v4 08/19] reset: starfive: jh71x0: Use 32bit I/O on 32bit registers Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 09/19] dt-bindings: clock: Add StarFive JH7110 system clock and reset generator Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 17:23   ` Conor Dooley
2023-02-21 17:23     ` Conor Dooley
2023-02-23  3:40     ` Hal Feng
2023-02-23  3:40       ` Hal Feng
2023-02-22  9:13   ` Krzysztof Kozlowski
2023-02-22  9:13     ` Krzysztof Kozlowski
2023-02-22 10:40     ` Conor Dooley
2023-02-22 10:40       ` Conor Dooley
2023-02-23 10:22       ` Hal Feng
2023-02-23 10:22         ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 10/19] dt-bindings: clock: Add StarFive JH7110 always-on " Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 17:26   ` Conor Dooley
2023-02-21 17:26     ` Conor Dooley
2023-02-23  5:52     ` Hal Feng
2023-02-23  5:52       ` Hal Feng
2023-03-09 14:22   ` Geert Uytterhoeven
2023-03-09 14:22     ` Geert Uytterhoeven
2023-03-13  2:29     ` Hal Feng
2023-03-13  2:29       ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 11/19] clk: starfive: Add StarFive JH7110 system clock driver Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 15:12   ` Conor Dooley
2023-02-21 15:12     ` Conor Dooley
2023-02-23  6:17     ` Hal Feng
2023-02-23  6:17       ` Hal Feng
2023-02-26 16:07   ` Emil Renner Berthing
2023-02-26 16:07     ` Emil Renner Berthing
2023-02-28  2:30     ` Hal Feng
2023-02-28  2:30       ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 12/19] clk: starfive: Add StarFive JH7110 always-on " Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-26 17:34   ` Emil Renner Berthing
2023-02-26 17:34     ` Emil Renner Berthing
2023-02-28  2:42     ` Hal Feng
2023-02-28  2:42       ` Hal Feng
2023-03-09  9:43       ` Hal Feng
2023-03-09  9:43         ` Hal Feng
2023-03-09 14:06         ` Emil Renner Berthing
2023-03-09 14:06           ` Emil Renner Berthing
2023-03-09 18:11           ` Conor Dooley
2023-03-09 18:11             ` Conor Dooley
2023-03-09 18:19             ` Emil Renner Berthing
2023-03-09 18:19               ` Emil Renner Berthing
2023-03-09 19:32               ` Palmer Dabbelt
2023-03-09 19:32                 ` Palmer Dabbelt
2023-02-21  2:46 ` [PATCH v4 13/19] reset: starfive: Add StarFive JH7110 reset driver Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 15:33   ` Emil Renner Berthing
2023-02-21 15:33     ` Emil Renner Berthing
2023-02-21 16:34     ` Conor Dooley
2023-02-21 16:34       ` Conor Dooley
2023-02-23  6:48       ` Hal Feng
2023-02-23  6:48         ` Hal Feng
2023-02-23  6:29     ` Hal Feng
2023-02-23  6:29       ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 14/19] dt-bindings: timer: Add StarFive JH7110 clint Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 15/19] dt-bindings: interrupt-controller: Add StarFive JH7110 plic Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 16/19] dt-bindings: riscv: Add SiFive S7 compatible Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 11:38   ` Krzysztof Kozlowski
2023-02-21 11:38     ` Krzysztof Kozlowski
2023-02-21 15:10   ` Conor Dooley
2023-02-21 15:10     ` Conor Dooley
2023-02-21  2:46 ` [PATCH v4 17/19] riscv: dts: starfive: Add initial StarFive JH7110 device tree Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 17:03   ` Conor Dooley
2023-02-21 17:03     ` Conor Dooley
2023-02-23  7:16     ` Hal Feng
2023-02-23  7:16       ` Hal Feng
2023-02-27 18:10       ` Conor Dooley
2023-02-27 18:10         ` Conor Dooley
2023-02-21  2:46 ` [PATCH v4 18/19] riscv: dts: starfive: Add StarFive JH7110 pin function definitions Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21  2:46 ` [PATCH v4 19/19] riscv: dts: starfive: Add StarFive JH7110 VisionFive 2 board device tree Hal Feng
2023-02-21  2:46   ` Hal Feng
2023-02-21 15:03   ` Emil Renner Berthing
2023-02-21 15:03     ` Emil Renner Berthing
2023-02-23  8:50     ` Hal Feng
2023-02-23  8:50       ` Hal Feng
2023-02-27 18:12       ` Conor Dooley
2023-02-27 18:12         ` Conor Dooley
2023-02-27 20:00         ` Conor Dooley
2023-02-27 20:00           ` Conor Dooley
2023-02-28  2:58           ` Hal Feng
2023-02-28  2:58             ` Hal Feng
2023-02-22 15:00 ` [PATCH v4 00/19] Basic clock, reset & device tree support for StarFive JH7110 RISC-V SoC patchwork-bot+linux-riscv
2023-02-22 15:00   ` patchwork-bot+linux-riscv
2023-02-22 15:35   ` Conor Dooley
2023-03-03 19:08 ` Tommaso Merciai
2023-03-03 19:08   ` Tommaso Merciai
2023-03-06  3:29   ` Hal Feng
2023-03-06  3:29     ` Hal Feng
2023-03-06 10:22     ` Tommaso Merciai
2023-03-06 10:22       ` Tommaso Merciai
2023-03-07  8:36 ` Hal Feng
2023-03-07  8:36   ` Hal Feng
2023-03-07  8:51   ` Conor Dooley
2023-03-07  8:51     ` Conor Dooley
2023-03-07 10:08     ` Hal Feng
2023-03-07 10:08       ` Hal Feng
2023-03-08 12:28       ` Tommaso Merciai
2023-03-08 12:28         ` Tommaso Merciai
2023-03-08 13:36         ` Conor Dooley [this message]
2023-03-08 13:36           ` Conor Dooley
2023-03-09 16:49           ` Tommaso Merciai
2023-03-09 16:49             ` Tommaso Merciai
2023-03-09 17:52             ` Conor Dooley
2023-03-09 17:52               ` Conor Dooley
2023-03-09 18:58               ` Tommaso Merciai
2023-03-09 18:58                 ` Tommaso Merciai
2023-03-09 19:03                 ` Conor Dooley
2023-03-09 19:03                   ` Conor Dooley
2023-03-10  7:48                   ` Tommaso Merciai
2023-03-10  7:48                     ` Tommaso Merciai

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=4c071642-e3c8-4716-a580-5b42e25efb1c@spud \
    --to=conor@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=ben.dooks@sifive.com \
    --cc=conor.dooley@microchip.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=emil.renner.berthing@canonical.com \
    --cc=hal.feng@starfivetech.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tomm.merciai@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.