From: Andreas Kemnade <andreas@kemnade.info>
To: Tony Lindgren <tony@atomide.com>,
Michael Turquette <mturquette@baylibre.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>, Lee Jones <lee@kernel.org>,
Roger Quadros <rogerq@kernel.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Kevin Hilman <khilman@baylibre.com>,
linux-omap@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>
Cc: Andreas Kemnade <andreas@kemnade.info>
Subject: [PATCH v3 0/3] mfd: twl: Add clock for TWL6030
Date: Sat, 5 Oct 2024 14:47:03 +0200 [thread overview]
Message-ID: <20241005124706.601393-1-andreas@kemnade.info> (raw)
Previously the clock support for only implemented for TWL6032 so add
it also for the TWL6030. There are devices out there where especially
WLAN only works if these clocks are enabled by some patched U-Boot.
This allows to explicitly specify the clock requirements.
Changes in V3:
- use type enum in driver_data and twl_clock_info
- revert back to store device instead of platform_device
Changes in V2:
- cleanup some defines
- no separate ops for 6030
- remove is_prepared()
- update Kconfig
Andreas Kemnade (3):
mfd: twl-core: Add a clock subdevice for the TWL6030
clk: twl: remove is_prepared
clk: twl: add TWL6030 support
drivers/clk/Kconfig | 2 +-
drivers/clk/clk-twl.c | 69 ++++++++++++++++++++++++++----------------
drivers/mfd/twl-core.c | 32 ++++++++++++++------
3 files changed, 66 insertions(+), 37 deletions(-)
--
2.39.5
next reply other threads:[~2024-10-05 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 12:47 Andreas Kemnade [this message]
2024-10-05 12:47 ` [PATCH v3 1/3] mfd: twl-core: Add a clock subdevice for the TWL6030 Andreas Kemnade
2024-10-05 12:47 ` [PATCH v3 2/3] clk: twl: remove is_prepared Andreas Kemnade
2024-10-05 12:47 ` [PATCH v3 3/3] clk: twl: add TWL6030 support Andreas Kemnade
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=20241005124706.601393-1-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=aaro.koskinen@iki.fi \
--cc=khilman@baylibre.com \
--cc=lee@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rogerq@kernel.org \
--cc=sboyd@kernel.org \
--cc=tony@atomide.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