From: Jernej Skrabec <jernej.skrabec@siol.net>
To: maxime.ripard@bootlin.com, wens@csie.org
Cc: jernej.skrabec@siol.net, sboyd@kernel.org,
mturquette@baylibre.com, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] clk: sunxi-ng: H6 related clock fixes
Date: Wed, 3 Apr 2019 17:14:02 +0200 [thread overview]
Message-ID: <20190403151404.26542-1-jernej.skrabec@siol.net> (raw)
During linux-next testing on Allwinner H6, I found several issues with
clock driver. This patch series fixes them.
Patch 1 allows video and vpu related clocks to set parent rate.
Patch 2 adds a comment with short explanation why zero width check is
needed.
Please take a look.
Best regards,
Jernej
Changes from v1:
- removed already applied patches
- fixed commit message
- added new patch which adds comment with explanation why zero width
check is needed
Jernej Skrabec (2):
clk: sunxi-ng: h6: Allow video & vpu clocks to change parent rate
clk: sunxi-ng: nkmp: Explain why zero width check is needed
drivers/clk/sunxi-ng/ccu-sun50i-h6.c | 6 +++---
drivers/clk/sunxi-ng/ccu_nkmp.c | 6 ++++++
2 files changed, 9 insertions(+), 3 deletions(-)
--
2.21.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-04-03 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 15:14 Jernej Skrabec [this message]
2019-04-03 15:14 ` [PATCH v2 1/2] clk: sunxi-ng: h6: Allow video & vpu clocks to change parent rate Jernej Skrabec
2019-04-03 15:14 ` [PATCH v2 2/2] clk: sunxi-ng: nkmp: Explain why zero width check is needed Jernej Skrabec
2019-04-04 7:32 ` [PATCH v2 0/2] clk: sunxi-ng: H6 related clock fixes Maxime Ripard
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=20190403151404.26542-1-jernej.skrabec@siol.net \
--to=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox