From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-clk@vger.kernel.org, x86@kernel.org,
platform-driver-x86@vger.kernel.org, alsa-devel@alsa-project.org,
Michael Turquette <mturquette@baylibre.com>,
Takashi Iwai <tiwai@suse.com>, Mark Brown <broonie@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Vinod Koul <vinod.koul@intel.com>
Subject: Re: [PATCH] clk: x86: add "mclk" alias for Baytrail/Cherrytrail
Date: Tue, 14 Feb 2017 13:23:12 -0600 [thread overview]
Message-ID: <bc29984e-cc58-69ed-d6ca-b4808d6514dc@linux.intel.com> (raw)
In-Reply-To: <20170214190456.GV25384@codeaurora.org>
On 2/14/17 1:04 PM, Stephen Boyd wrote:
> On 02/12, Pierre-Louis Bossart wrote:
>> Due to timing requirements, TI and Conexant manage the audio
>> reference clock from their ASoC codec drivers using the "mclk"
>> string. This patch adds a default alias to "pmc_plt_clk_3" to
>> avoid Intel-specific tests in those codec drivers and use code
>> as-is.
>> "pmc_plt_clk_3" is used exclusively for audio on all known
>> Baytrail/CherryTrail designs and is e.g. routed on the MCLK
>> (pin 26) of the MinnowBoardMAX Turbot LSE connector.
>>
>> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>> ---
>>
>> Notes:
>> This patch only applies on top of linux-next or clk-next, the
>> previous clk-related patches are not yet merged in the audio
>> trees
>>
>> drivers/clk/x86/clk-pmc-atom.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/clk/x86/clk-pmc-atom.c b/drivers/clk/x86/clk-pmc-atom.c
>> index 2b60577..ba00d27 100644
>> --- a/drivers/clk/x86/clk-pmc-atom.c
>> +++ b/drivers/clk/x86/clk-pmc-atom.c
>> @@ -340,6 +340,8 @@ static int plt_clk_probe(struct platform_device *pdev)
>>
>> plt_clk_free_parent_names_loop(parent_names, data->nparents);
>>
>> + clk_add_alias("mclk", dev_name(&pdev->dev), "pmc_plt_clk_3", NULL);
>> +
>
> This leaks an alias when the driver is removed. Honestly,
> clk_add_alias() doesn't work well because of that problem. Can
> you just add another lookup with the pointer you already have
> instead of passing a NULL device to do a global lookup?
This is a builtin driver that cannot be configured as a module, is the
leaked alias problematic?
I don't mind trying something different but I am not familiar enough
with the framework to understand what you are hinting at. Are you
suggesting a change on the last parameter such as:
clk_add_alias("mclk", dev_name(&pdev->dev), "pmc_plt_clk_3", &pdev->dev)
Thanks!
-Pierre
next prev parent reply other threads:[~2017-02-14 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 22:06 [PATCH] clk: x86: add "mclk" alias for Baytrail/Cherrytrail Pierre-Louis Bossart
2017-02-14 19:04 ` Stephen Boyd
2017-02-14 19:23 ` Pierre-Louis Bossart [this message]
2017-02-16 0:56 ` Stephen Boyd
2017-02-16 2:05 ` Andy Shevchenko
2017-02-16 10:31 ` Mark Brown
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=bc29984e-cc58-69ed-d6ca-b4808d6514dc@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=tiwai@suse.com \
--cc=vinod.koul@intel.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox