From: Jerome Brunet <jbrunet@baylibre.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 1/2] clk: honor CLK_MUX_ROUND_CLOSEST in generic clk mux
Date: Wed, 25 Apr 2018 11:59:56 +0200 [thread overview]
Message-ID: <1524650396.4026.55.camel@baylibre.com> (raw)
In-Reply-To: <CAAEAJfDgGYu9WR5+qA-trQUTkb--bam=LLbhH+1N2OdrtBGLzA@mail.gmail.com>
On Tue, 2018-04-24 at 11:04 -0300, Ezequiel Garcia wrote:
> > }
> > +EXPORT_SYMBOL_GPL(clk_mux_determine_rate_flags);
> >
>
> Why do we need to export this?
Because any driver implementing some type of mux may use this function, and the
driver could be a module. I have one in the pipe right now.
It is the same as __clk_determine_rate(), __clk_mux_determine_rate_closest()
WARNING: multiple messages have this Message-ID (diff)
From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/2] clk: honor CLK_MUX_ROUND_CLOSEST in generic clk mux
Date: Wed, 25 Apr 2018 11:59:56 +0200 [thread overview]
Message-ID: <1524650396.4026.55.camel@baylibre.com> (raw)
In-Reply-To: <CAAEAJfDgGYu9WR5+qA-trQUTkb--bam=LLbhH+1N2OdrtBGLzA@mail.gmail.com>
On Tue, 2018-04-24 at 11:04 -0300, Ezequiel Garcia wrote:
> > }
> > +EXPORT_SYMBOL_GPL(clk_mux_determine_rate_flags);
> >
>
> Why do we need to export this?
Because any driver implementing some type of mux may use this function, and the
driver could be a module. I have one in the pipe right now.
It is the same as __clk_determine_rate(), __clk_mux_determine_rate_closest()
next prev parent reply other threads:[~2018-04-25 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 13:59 [PATCH 0/2] clk: honor CLK_MUX_ROUND_CLOSEST in mux Jerome Brunet
2018-04-09 13:59 ` Jerome Brunet
2018-04-09 13:59 ` [PATCH 1/2] clk: honor CLK_MUX_ROUND_CLOSEST in generic clk mux Jerome Brunet
2018-04-09 13:59 ` Jerome Brunet
2018-04-24 14:04 ` Ezequiel Garcia
2018-04-24 14:04 ` Ezequiel Garcia
2018-04-24 14:04 ` Ezequiel Garcia
2018-04-25 9:59 ` Jerome Brunet [this message]
2018-04-25 9:59 ` Jerome Brunet
2018-04-25 9:59 ` Jerome Brunet
2018-04-09 13:59 ` [PATCH 2/2] clk: meson: honor CLK_MUX_ROUND_CLOSEST in clk_regmap Jerome Brunet
2018-04-09 13:59 ` Jerome Brunet
2018-04-16 16:24 ` [PATCH 0/2] clk: honor CLK_MUX_ROUND_CLOSEST in mux Stephen Boyd
2018-04-16 16:24 ` Stephen Boyd
2018-04-16 16:24 ` 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=1524650396.4026.55.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=sboyd@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.