From: Oleg Verych <olecom@gmail.com>
To: linux-sunxi@lists.linux.dev (open list:ARM/Allwinner sunXi SoC support)
Cc: "Oleg Verych" <olecom@gmail.com>,
"Emilio López" <emilio@elopez.com.ar>,
"Maxime Ripard" <mripard@kernel.org>,
"Chen-Yu Tsai" <wens@csie.org>,
"Jernej Skrabec" <jernej.skrabec@siol.net>,
linux-sunxi <linux-sunxi@googlegroups.com>
Subject: [PATCH] doc sunxi: update CCU wiki page link in clocks.rst
Date: Tue, 17 Jan 2023 02:22:09 +0300 [thread overview]
Message-ID: <20230116232209.4744-1-olecom@gmail.com> (raw)
In-Reply-To: <20230107083749.2419-1-olecom@gmail.com>
Update wiki page link to the Allwinner sunXi SoC Clock Control Module.
Signed-off-by: Oleg Verych <olecom@gmail.com>
---
Hi!
Can I ask additional question to those in the file?
How is it possible to setup PLL7 to particular frequency and select
it as a source to CSI0 via CCM_CSI0_CLK[1]?
Is it possible to put such device tree example in documentation?
Thanks!
[1] https://linux-sunxi.org/Clock_Control_Module#CCM_CSI0_CLK
Documentation/arm/sunxi/clocks.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/arm/sunxi/clocks.rst b/Documentation/arm/sunxi/clocks.rst
index 23bd03f3e..f435bdd70 100644
--- a/Documentation/arm/sunxi/clocks.rst
+++ b/Documentation/arm/sunxi/clocks.rst
@@ -49,7 +49,7 @@ Q: Were can I learn more about the sunxi clocks?
A: The linux-sunxi wiki contains a page documenting the clock registers,
you can find it at
- http://linux-sunxi.org/A10/CCM
+ https://linux-sunxi.org/Clock_Control_Module
The authoritative source for information at this time is the ccmu driver
released by Allwinner, you can find it at
--
2.20.1
prev parent reply other threads:[~2023-01-16 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 8:37 [PATCH] media: sun4i-csi: Fix 'Unbalanced pm_runtime_enable!' Oleg Verych
2023-01-09 20:24 ` [PATCH] media: sun4i-csi: Use CSI_INT_STA_REG name, fix typo in a comment Oleg Verych
2023-01-16 19:07 ` Sakari Ailus
2023-01-16 23:03 ` Oleg Verych
2023-01-16 23:22 ` Oleg Verych [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=20230116232209.4744-1-olecom@gmail.com \
--to=olecom@gmail.com \
--cc=emilio@elopez.com.ar \
--cc=jernej.skrabec@siol.net \
--cc=linux-sunxi@googlegroups.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=wens@csie.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 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.