From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
vkoul@kernel.org
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
sanyog.r.kale@intel.com, yung-chuan.liao@linux.intel.com
Subject: Re: [PATCH 3/3] soundwire: qcom: add clock stop via runtime pm support
Date: Wed, 3 Mar 2021 11:46:07 +0000 [thread overview]
Message-ID: <75a7a05c-d34d-aa3f-e8e8-4bbb89e1beca@linaro.org> (raw)
In-Reply-To: <2899ca9e-2938-4d8d-5e56-49eba8cdb920@linux.intel.com>
Thanks Pierre for reviewing this in detail!
On 26/02/2021 17:41, Pierre-Louis Bossart wrote:
...
>> return 0;
>> err_master_add:
>> @@ -1214,6 +1261,47 @@ static int qcom_swrm_remove(struct
>> platform_device *pdev)
>> return 0;
>> }
>> +static int swrm_runtime_resume(struct device *dev)
>> +{
>> + struct qcom_swrm_ctrl *ctrl = dev_get_drvdata(dev);
>> +
>> + reinit_completion(&ctrl->enumeration);
>> + clk_prepare_enable(ctrl->hclk);
>> + ctrl->reg_write(ctrl, SWRM_COMP_SW_RESET, 0x01);
>> + qcom_swrm_get_device_status(ctrl);
>> + sdw_handle_slave_status(&ctrl->bus, ctrl->status);
>> + qcom_swrm_init(ctrl);
>> + wait_for_completion_timeout(&ctrl->enumeration,
>> + msecs_to_jiffies(TIMEOUT_MS));
>> + usleep_range(100, 105);
>> +
>> + pm_runtime_mark_last_busy(dev);
>
> Humm, what 'clock stop' are we talking about here?
>
> In SoundWire 1.x devices, you can stop the BUS clock and not have to
> redo any enumeration on resume, devices are required to save their
> context. You have to also follow the pattern of preparing and
> broadcasting the CLOCK STOP NOW message.
>
> It looks like you are stopping something else, and completely resetting
> the hardware. It's fine, it's just a reset but not clock stop support as
> defined in the SoundWire spec.
>
This is clock stop that Soundwire Spec refers to.
However I think I messed up this patch! :-)
>> +
>> + return 0;
>> +}
>> +
>> +static int __maybe_unused swrm_runtime_suspend(struct device *dev)
>> +{
>> + struct qcom_swrm_ctrl *ctrl = dev_get_drvdata(dev);
>> +
>> + /* Mask bus clash interrupt */
>> + ctrl->intr_mask &= ~SWRM_INTERRUPT_STATUS_MASTER_CLASH_DET;
>> + ctrl->reg_write(ctrl, SWRM_INTERRUPT_MASK_ADDR, ctrl->intr_mask);
>> + ctrl->reg_write(ctrl, SWRM_INTERRUPT_CPU_EN, ctrl->intr_mask);
>> + /* clock stop sequence */
>> + qcom_swrm_cmd_fifo_wr_cmd(ctrl, 0x2, 0xF, SDW_SCP_CTRL);
>
> Humm, this looks like writing in SCP_CTRL::ClockStopNow, so why is
> enumeration required on restart?
>
One of the controller instance needed a full reset so there is a mix of
code for both clock stop and reset here!
Am working on cleaning up this in a better way!
I will also address the runtime pm comments that you have noticed in
next version!
--srini
> If you take down the bus and reset everything, you don't need to do this
> sequence. a hardware reset will do...
>
>> +
>> + clk_disable_unprepare(ctrl->hclk);
>> +
>> + usleep_range(100, 105);
>> +
>> + return 0;
>> +}
>> +
>> +static const struct dev_pm_ops swrm_dev_pm_ops = {
>> + SET_RUNTIME_PM_OPS(swrm_runtime_suspend, swrm_runtime_resume, NULL)
>> +};
>> +
>> static const struct of_device_id qcom_swrm_of_match[] = {
>> { .compatible = "qcom,soundwire-v1.3.0", .data = &swrm_v1_3_data },
>> { .compatible = "qcom,soundwire-v1.5.1", .data = &swrm_v1_5_data },
>> @@ -1228,6 +1316,7 @@ static struct platform_driver qcom_swrm_driver = {
>> .driver = {
>> .name = "qcom-soundwire",
>> .of_match_table = qcom_swrm_of_match,
>> + .pm = &swrm_dev_pm_ops,
>> }
>> };
>> module_platform_driver(qcom_swrm_driver);
>>
prev parent reply other threads:[~2021-03-03 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 17:02 [PATCH 0/3] soundwire: qcom: add Clock Stop and Auto Enumeration support Srinivas Kandagatla
2021-02-26 17:02 ` [PATCH 1/3] soundwire: export sdw_compare_devid() and sdw_extract_slave_id() Srinivas Kandagatla
2021-02-26 17:02 ` [PATCH 2/3] soundwire: qcom: add auto enumeration support Srinivas Kandagatla
2021-02-26 17:44 ` Pierre-Louis Bossart
2021-03-02 10:33 ` Srinivas Kandagatla
2021-03-02 14:34 ` Pierre-Louis Bossart
2021-03-03 9:38 ` Srinivas Kandagatla
2021-03-03 16:35 ` Pierre-Louis Bossart
2021-03-05 10:39 ` Srinivas Kandagatla
2021-03-05 16:19 ` Pierre-Louis Bossart
2021-03-05 16:57 ` Srinivas Kandagatla
2021-02-26 17:02 ` [PATCH 3/3] soundwire: qcom: add clock stop via runtime pm support Srinivas Kandagatla
2021-02-26 17:41 ` Pierre-Louis Bossart
2021-03-03 11:46 ` Srinivas Kandagatla [this message]
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=75a7a05c-d34d-aa3f-e8e8-4bbb89e1beca@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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
Powered by JetHome