From: Conor Dooley <conor.dooley@microchip.com>
To: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<aou@eecs.berkeley.edu>, <paul.walmsley@sifive.com>,
<palmer@rivosinc.com>
Cc: <daire.mcnamara@microchip.com>, <linux-clk@vger.kernel.org>,
<linux-riscv@lists.infradead.org>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v1 0/3] More PolarFire SoC Fixes for 5.18
Date: Fri, 8 Apr 2022 13:35:41 +0000 [thread overview]
Message-ID: <20220408133543.3537118-1-conor.dooley@microchip.com> (raw)
Hey,
After the clock driver for the PolarFire SoC was accepted I started work
on the onboard RTC & found out that the reference clock for the rtc was
actually missing from the clock driver.
While restructuring the clock driver to add support for the rtc
reference, I noticed that there were some problems with how the FIC
clocks were being used. The FIC clocks are the cpu side inputs to the
AXI fabric interconnections & are not the clocks for any peripherals.
This series fixes the problems I noticed:
- the fic clocks incorrectly had the AHB clock as their parents
- the last fic, named differently to the others, had not been set as
a critical clock
- some peripherals on the fabric side were incorrectly using the cpu
side fic clocks, resulting in incorrect rates.
I added fixes tags to these patches in the hope that they will make it
into 5.18. I kept series separate from [0] as that fixes something that
is broken, while these are only wrong.
Thanks,
Conor.
[0] https://lore.kernel.org/linux-riscv/20220408131352.3421559-1-conor.dooley@microchip.com/T/#u
Conor Dooley (3):
clk: microchip: mpfs: fix parents for FIC clocks
clk: microchip: mpfs: mark CLK_ATHENA as critical
riscv: dts: microchip: fix usage of fic clocks on mpfs
.../dts/microchip/microchip-mpfs-fabric.dtsi | 16 ++++++++++++++--
.../riscv/boot/dts/microchip/microchip-mpfs.dtsi | 2 +-
drivers/clk/microchip/clk-mpfs.c | 16 +++++++++-------
3 files changed, 24 insertions(+), 10 deletions(-)
--
2.35.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-04-08 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 13:35 Conor Dooley [this message]
2022-04-08 13:35 ` [PATCH v1 1/3] clk: microchip: mpfs: fix parents for FIC clocks Conor Dooley
2022-04-08 13:35 ` [PATCH v1 2/3] clk: microchip: mpfs: mark CLK_ATHENA as critical Conor Dooley
2022-04-08 13:35 ` [PATCH v1 3/3] riscv: dts: microchip: fix usage of fic clocks on mpfs Conor Dooley
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=20220408133543.3537118-1-conor.dooley@microchip.com \
--to=conor.dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=daire.mcnamara@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=sboyd@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