From: Sameer Pujar <spujar@nvidia.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH 7/7] ALSA: hda/tegra: add driver flag for runtime PM
Date: Tue, 22 Jan 2019 07:34:21 +0530 [thread overview]
Message-ID: <a963a5be-9efe-226e-5fba-1247c7ba2cce@nvidia.com> (raw)
In-Reply-To: <s5ho989y9xu.wl-tiwai@suse.de>
On 1/22/2019 3:01 AM, Takashi Iwai wrote:
> On Mon, 21 Jan 2019 18:41:37 +0100,
> Sameer Pujar wrote:
>> AZX_DCAPS_PM_RUNTIME flag is added to indicate support for runtime PM.
>> azx_has_pm_runtime() can be called to check if above is enabled. The
>> flag is put under CONFIG_PM check.
>>
>> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
>> Reviewed-by: Ravindra Lokhande <rlokhande@nvidia.com>
>> Reviewed-by: Mohan Kumar D <mkumard@nvidia.com>
> This can be more simply done in hda_controller.h. Namely, a change
> like:
>
> --- a/sound/pci/hda/hda_controller.h
> +++ b/sound/pci/hda/hda_controller.h
> @@ -49,7 +49,11 @@
> #define AZX_DCAPS_4K_BDLE_BOUNDARY (1 << 23) /* BDLE in 4k boundary */
> /* 24 unused */
> #define AZX_DCAPS_COUNT_LPIB_DELAY (1 << 25) /* Take LPIB as delay */
> +#ifdef CONFIG_PM
> #define AZX_DCAPS_PM_RUNTIME (1 << 26) /* runtime PM support */
> +#else
> +#define AZX_DCAPS_PM_RUNTIME 0 /* N/A */
> +#endif
> /* 27 unused */
> #define AZX_DCAPS_CORBRP_SELF_CLEAR (1 << 28) /* CORBRP clears itself after reset */
> #define AZX_DCAPS_NO_MSI64 (1 << 29) /* Stick to 32-bit MSIs */
In one of the patches in the series, I am using azx_has_pm_runtime() to
forbid runtime PM calls.
I can use above as you suggested. Along with this, I would need to
populate chip->driver_caps with
above flag. Something like below,
--- a/sound/pci/hda/hda_tegra.c
+++ b/sound/pci/hda/hda_tegra.c
@@ -521,7 +521,8 @@ MODULE_DEVICE_TABLE(of, hda_tegra_match);
static int hda_tegra_probe(struct platform_device *pdev)
{
- unsigned int driver_flags = AZX_DCAPS_CORBRP_SELF_CLEAR;
+ unsigned int driver_flags = AZX_DCAPS_CORBRP_SELF_CLEAR |
+ AZX_DCAPS_PM_RUNTIME;
struct snd_card *card;
struct azx *chip;
struct hda_tegra *hda;
Thanks,
Sameer.
>
> thanks,
>
> Takashi
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-01-22 2:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 17:41 [PATCH 0/7] Runtime PM support (hda/tegra) Sameer Pujar
2019-01-21 17:41 ` [PATCH 1/7] ALSA: hda/tegra: runtime power management support Sameer Pujar
2019-01-21 17:41 ` [PATCH 2/7] ALSA: hda/tegra: get clock handles early in probe Sameer Pujar
2019-01-21 17:41 ` [PATCH 3/7] ALSA: hda/tegra: add runtime PM callbacks Sameer Pujar
2019-01-21 17:41 ` [PATCH 4/7] ALSA: hda/tegra: remove redundant clock enable API Sameer Pujar
2019-01-21 17:41 ` [PATCH 5/7] ALSA: hda/tegra: implement runtime suspend/resume Sameer Pujar
2019-01-21 17:41 ` [PATCH 6/7] ALSA: hda/tegra: fix kernel panic Sameer Pujar
2019-01-21 21:28 ` Takashi Iwai
2019-01-22 3:41 ` Sameer Pujar
2019-01-22 6:24 ` Takashi Iwai
2019-01-21 17:41 ` [PATCH 7/7] ALSA: hda/tegra: add driver flag for runtime PM Sameer Pujar
2019-01-21 21:31 ` Takashi Iwai
2019-01-22 2:04 ` Sameer Pujar [this message]
2019-01-22 6:31 ` Takashi Iwai
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=a963a5be-9efe-226e-5fba-1247c7ba2cce@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=tiwai@suse.de \
/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