From: Tali Perry <tali.perry1@gmail.com>
To: avifishman70@gmail.com, tmaimon77@gmail.com, venture@google.com,
yuenn@google.com, brendanhiggins@google.com,
mturquette@baylibre.com, sboyd@kernel.org
Cc: openbmc@lists.ozlabs.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, Tali Perry <tali.perry1@gmail.com>,
Wei Yongjun <weiyongjun1@huawei.com>
Subject: [PATCH v1 0/1] clk: npcm7xx: get fixed clocks from DT
Date: Wed, 5 Dec 2018 21:47:01 +0200 [thread overview]
Message-ID: <20181205194702.257430-2-tali.perry1@gmail.com> (raw)
In-Reply-To: <20181205194702.257430-1-tali.perry1@gmail.com>
Nuvoton NPCM7XX Clock Controller
The npcm7xx clock module includes 4 PLLs and then a tree of muxes and dividers.
All muxes and dividers are preset before Linux boots. The presetting can change
according to the board.
Linux drivers need to know what the frequencies are, but they cannot change it,
so this whole driver is intended as read only mechanism for clocks.
Before this change PLLs input clk value was defined inside the driver.
With this fix clock will be on the DT.
Signed-off-by: Tali Perry <tali.perry1@gmail.com>
Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
---
Tali Perry (1):
clk: npcm: get fixed input clks from DT
drivers/clk/clk-npcm7xx.c | 64 +++++++++++++++++++++++++++++++++++++++--------
1 file changed, 53 insertions(+), 11 deletions(-)
--
2.14.1
next prev parent reply other threads:[~2018-12-05 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 19:47 clk: npcm7xx: get fixed input clks " Tali Perry
2018-12-05 19:47 ` Tali Perry [this message]
2018-12-05 19:47 ` [PATCH v1 1/1] clk: npcm: " Tali Perry
2018-12-05 20:42 ` Stephen Boyd
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=20181205194702.257430-2-tali.perry1@gmail.com \
--to=tali.perry1@gmail.com \
--cc=avifishman70@gmail.com \
--cc=brendanhiggins@google.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=openbmc@lists.ozlabs.org \
--cc=sboyd@kernel.org \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=weiyongjun1@huawei.com \
--cc=yuenn@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®