From: Sameer Pujar <spujar@nvidia.com>
To: perex@perex.cz, tiwai@suse.com, pierre-louis.bossart@linux.intel.com
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com,
rlokhande@nvidia.com, sharadg@nvidia.com, mkumard@nvidia.com,
alsa-devel@alsa-project.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, Sameer Pujar <spujar@nvidia.com>
Subject: [PATCH v2] ALSA: hda/tegra: enable clock during probe
Date: Fri, 25 Jan 2019 16:36:58 +0530 [thread overview]
Message-ID: <1548414418-5785-1-git-send-email-spujar@nvidia.com> (raw)
If CONFIG_PM is disabled or runtime PM calls are forbidden, the clocks
will not be ON. This could cause issue during probe, where hda init
setup is done. This patch enables clocks unconditionally during probe.
Along with above, follwoing changes are done.
* enable runtime PM before exiting from probe work. This helps to avoid
usage of pm_runtime_get_sync/pm_runtime_put() in probe work.
* hda_tegra_disable_clocks() is moved out of CONFIG_PM_SLEEP check.
* runtime PM callbacks moved out of CONFIG_PM check
Signed-off-by: Sameer Pujar <spujar@nvidia.com>
Reviewed-by: Ravindra Lokhande <rlokhande@nvidia.com>
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
---
sound/pci/hda/hda_tegra.c | 26 +++++++++++++++++---------
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git a/sound/pci/hda/hda_tegra.c b/sound/pci/hda/hda_tegra.c
index c8d18dc..ba6175f 100644
--- a/sound/pci/hda/hda_tegra.c
+++ b/sound/pci/hda/hda_tegra.c
@@ -219,7 +219,6 @@ static int hda_tegra_enable_clocks(struct hda_tegra *data)
return rc;
}
-#ifdef CONFIG_PM_SLEEP
static void hda_tegra_disable_clocks(struct hda_tegra *data)
{
clk_disable_unprepare(data->hda2hdmi_clk);
@@ -227,6 +226,7 @@ static void hda_tegra_disable_clocks(struct hda_tegra *data)
clk_disable_unprepare(data->hda_clk);
}
+#ifdef CONFIG_PM_SLEEP
/*
* power management
*/
@@ -257,7 +257,6 @@ static int hda_tegra_resume(struct device *dev)
}
#endif /* CONFIG_PM_SLEEP */
-#ifdef CONFIG_PM
static int hda_tegra_runtime_suspend(struct device *dev)
{
struct snd_card *card = dev_get_drvdata(dev);
@@ -283,7 +282,7 @@ static int hda_tegra_runtime_resume(struct device *dev)
int rc;
rc = hda_tegra_enable_clocks(hda);
- if (rc != 0)
+ if (rc)
return rc;
if (chip && chip->running) {
hda_tegra_init(hda);
@@ -292,7 +291,6 @@ static int hda_tegra_runtime_resume(struct device *dev)
return 0;
}
-#endif /* CONFIG_PM */
static const struct dev_pm_ops hda_tegra_pm = {
SET_SYSTEM_SLEEP_PM_OPS(hda_tegra_suspend, hda_tegra_resume)
@@ -551,9 +549,9 @@ static int hda_tegra_probe(struct platform_device *pdev)
dev_set_drvdata(&pdev->dev, card);
- pm_runtime_enable(hda->dev);
- if (!azx_has_pm_runtime(chip))
- pm_runtime_forbid(hda->dev);
+ err = hda_tegra_enable_clocks(hda);
+ if (err)
+ goto out_free;
schedule_work(&hda->probe_work);
@@ -571,7 +569,6 @@ static void hda_tegra_probe_work(struct work_struct *work)
struct platform_device *pdev = to_platform_device(hda->dev);
int err;
- pm_runtime_get_sync(hda->dev);
err = hda_tegra_first_init(chip, pdev);
if (err < 0)
goto out_free;
@@ -592,8 +589,15 @@ static void hda_tegra_probe_work(struct work_struct *work)
chip->running = 1;
snd_hda_set_power_save(&chip->bus, power_save * 1000);
+ /* set device state as active */
+ if (pm_runtime_set_active(hda->dev) < 0)
+ goto out_free;
+ /* enable runtime PM */
+ pm_runtime_enable(hda->dev);
+ if (!azx_has_pm_runtime(chip))
+ pm_runtime_forbid(hda->dev);
+
out_free:
- pm_runtime_put(hda->dev);
return; /* no error return from async probe */
}
@@ -603,6 +607,10 @@ static int hda_tegra_remove(struct platform_device *pdev)
ret = snd_card_free(dev_get_drvdata(&pdev->dev));
pm_runtime_disable(&pdev->dev);
+ if (!pm_runtime_status_suspended(&pdev->dev)) {
+ hda_tegra_runtime_suspend(&pdev->dev);
+ pm_runtime_set_suspended(&pdev->dev);
+ }
return ret;
}
--
2.7.4
next reply other threads:[~2019-01-25 11:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 11:06 Sameer Pujar [this message]
2019-01-25 11:42 ` [PATCH v2] ALSA: hda/tegra: enable clock during probe Jon Hunter
2019-01-25 12:19 ` Sameer Pujar
2019-01-25 13:15 ` Jon Hunter
2019-01-30 12:45 ` Jon Hunter
2019-01-30 16:40 ` Takashi Iwai
2019-01-31 9:36 ` Sameer Pujar
2019-01-31 11:05 ` Thierry Reding
2019-01-31 11:21 ` Takashi Iwai
2019-01-31 11:46 ` Rafael J. Wysocki
2019-01-31 11:50 ` Rafael J. Wysocki
2019-01-31 11:59 ` Takashi Iwai
2019-01-31 12:10 ` Rafael J. Wysocki
2019-01-31 14:21 ` Sameer Pujar
2019-01-31 14:30 ` Thierry Reding
2019-01-31 23:24 ` Rafael J. Wysocki
2019-02-04 8:16 ` Sameer Pujar
2019-02-04 8:51 ` Thierry Reding
2019-02-04 10:04 ` Jon Hunter
2019-02-04 10:13 ` Takashi Iwai
2019-02-05 11:34 ` Rafael J. Wysocki
2019-02-04 8:45 ` Thierry Reding
2019-02-04 9:53 ` Jon Hunter
2019-02-04 11:05 ` Thierry Reding
2019-02-04 12:03 ` Dmitry Osipenko
2019-02-04 14:00 ` Thierry Reding
2019-02-04 14:28 ` Dmitry Osipenko
2019-02-04 16:17 ` Thierry Reding
2019-02-04 18:46 ` Dmitry Osipenko
2019-02-05 11:52 ` Rafael J. Wysocki
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=1548414418-5785-1-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rlokhande@nvidia.com \
--cc=sharadg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.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).