From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Chen-Yu Tsai <wens@csie.org>, Stephen Boyd <sboyd@codeaurora.org>,
Mike Turquette <mturquette@baylibre.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v2] clk: sunxi: Add Kconfig options
Date: Thu, 21 Mar 2019 10:02:21 +0100 [thread overview]
Message-ID: <20190321090220.u6itbl4fhnhrn7e2@flea> (raw)
In-Reply-To: <155302433780.20095.8306789134509103174@swboyd.mtv.corp.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 892 bytes --]
On Tue, Mar 19, 2019 at 12:38:57PM -0700, Stephen Boyd wrote:
> Quoting Maxime Ripard (2019-03-19 07:37:59)
> > We used to have a clock framework that isn't really used these days, except
> > for a few clocks and/or SoCs. Most of the time, the new framework and
> > drivers (sunxi-ng) will provide everything needed for the customer devices
> > to operate properly.
> >
> > Since we're not needing it that much, it might make sense to disable those
> > drivers, for example when we want to reduce the kernel size. Let's add
> > options in Kconfig that can be disabled if needed, but are still on by
> > default to keep the same features in the standard case.
> >
> > Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
> >
> > ---
>
> Acked-by: Stephen Boyd <sboyd@kernel.org>
Applied, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-03-21 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 14:37 [PATCH v2] clk: sunxi: Add Kconfig options Maxime Ripard
2019-03-19 19:38 ` Stephen Boyd
2019-03-21 9:02 ` Maxime Ripard [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=20190321090220.u6itbl4fhnhrn7e2@flea \
--to=maxime.ripard@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--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