linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Stephen Boyd <sboyd@kernel.org>, Tony Lindgren <tony@atomide.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Kevin Hilman <khilman@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lee Jones <lee@kernel.org>,
	linux-omap@vger.kernel.org, Roger Quadros <rogerq@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH v2 0/3] mfd: twl: Add clock for TWL6030
Date: Wed, 2 Oct 2024 15:13:41 +0200	[thread overview]
Message-ID: <20241002151341.2c8421bd@akair> (raw)
In-Reply-To: <20241002110718.528337-1-andreas@kemnade.info>

Am Wed,  2 Oct 2024 13:07:15 +0200
schrieb Andreas Kemnade <andreas@kemnade.info>:

> 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.
> 
oh, forgotten the changelog:
Changes in V2:
- cleanup some defines
- no separate ops for 6030
- remove is_prepared()
- update Kconfig

Regards,
Andreas

      parent reply	other threads:[~2024-10-02 13:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 11:07 [PATCH v2 0/3] mfd: twl: Add clock for TWL6030 Andreas Kemnade
2024-10-02 11:07 ` [PATCH v2 1/3] mfd: twl-core: Add a clock subdevice for the TWL6030 Andreas Kemnade
2024-10-02 11:07 ` [PATCH v2 2/3] clk: twl: remove is_prepared Andreas Kemnade
2024-10-02 12:09   ` Roger Quadros
2024-10-02 11:07 ` [PATCH v2 3/3] clk: twl: add TWL6030 support Andreas Kemnade
2024-10-02 12:22   ` Roger Quadros
2024-10-02 13:13 ` Andreas Kemnade [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=20241002151341.2c8421bd@akair \
    --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;
as well as URLs for NNTP newsgroup(s).