From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] MMC: meson: initial support for GXBB platforms
Date: Wed, 7 Sep 2016 18:18:25 -0700 [thread overview]
Message-ID: <20160908011825.GA19921@codeaurora.org> (raw)
In-Reply-To: <7hy433qpoo.fsf@baylibre.com>
On 09/07, Kevin Hilman wrote:
> Stephen Boyd <sboyd@codeaurora.org> writes:
> > On 08/03, Kevin Hilman wrote:
> >> + host->mux.hw.init = &init;
> >> +
> >> + host->mux_clk = devm_clk_register(host->dev, &host->mux.hw);
> >
> > Hmm I was hoping to get rid of devm_clk_register() and replace it
> > with devm_clk_hw_register() instead. All part of my grand plan to
> > split providers from consumers, but this driver is different in
> > the sense that it registers clks to provide to itself. Maybe we
> > should make __clk_create_clk() into a real clk provider API so
> > that we can use devm_clk_hw_register() here and then generate a
> > clk for this device from the hw structure.
>
> So is there something else I should do here, or can we rework this later
> after you rework the framework a bit?
>
That can wait for later. If nobody takes care of it I'll do it
when I get around to it.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-09-08 1:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 23:18 [PATCH v2 1/2] ARM64: dts: meson-gxbb: add MMC support Kevin Hilman
2016-08-03 23:18 ` [PATCH v2 2/2] MMC: meson: initial support for GXBB platforms Kevin Hilman
2016-08-23 1:21 ` Stephen Boyd
2016-09-07 23:02 ` Kevin Hilman
2016-09-08 1:18 ` Stephen Boyd [this message]
2016-08-24 11:53 ` Ulf Hansson
2016-09-13 15:53 ` Kevin Hilman
2016-08-04 18:15 ` [PATCH v2 1/2] ARM64: dts: meson-gxbb: add MMC support Rob Herring
2016-08-04 22:58 ` Kevin Hilman
2016-08-05 2:45 ` Rob Herring
[not found] ` <20160805034623.GA1883@excalibur.cnev.de>
2016-08-05 15:22 ` Kevin Hilman
2016-08-14 5:25 ` kbuild test robot
2016-08-15 21:33 ` Kevin Hilman
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=20160908011825.GA19921@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).