From: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: <agross@kernel.org>, <lgirdwood@gmail.com>, <broonie@kernel.org>,
<robh+dt@kernel.org>, <quic_plai@quicinc.com>,
<bgoswami@quicinc.com>, <perex@perex.cz>, <tiwai@suse.com>,
<srinivas.kandagatla@linaro.org>, <quic_rohkumar@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<swboyd@chromium.org>, <judyhsiao@chromium.org>,
Linus Walleij <linus.walleij@linaro.org>,
<linux-gpio@vger.kernel.org>,
Venkata Prasad Potturu <quic_potturu@quicinc.com>
Subject: Re: [PATCH 2/2] pinctrl: qcom: sc7280: Add lpi pinctrl variant data structure for adsp based targets
Date: Wed, 1 Jun 2022 15:26:44 +0530 [thread overview]
Message-ID: <26bfd089-46d6-d08d-efac-71ffc04f674c@quicinc.com> (raw)
In-Reply-To: <YoJrGGg0RviVn2Xj@ripper>
On 5/16/2022 8:47 PM, Bjorn Andersson wrote:
Thanks for Your time Bjorn!!!
> On Wed 04 May 06:56 PDT 2022, Srinivasa Rao Mandadapu wrote:
>
>> Add compatible string and lpi pinctrl variant data structure for adsp enabled
>> sc7280 platforms.
> This says what the change does, but gives no clue to what this
> compatible represents and why the clock is not optional.
>
> Could you please describe here what scenario this compatible is to be
> used for etc, so that when someone else adds support for the next
> platform they can use the git history to understand which case to
> follow.
>
> Thanks,
> Bjorn
Okay. Will update the commit message.
>
>> Signed-off-by: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
>> Co-developed-by: Venkata Prasad Potturu <quic_potturu@quicinc.com>
>> Signed-off-by: Venkata Prasad Potturu <quic_potturu@quicinc.com>
>> ---
>> drivers/pinctrl/qcom/pinctrl-sc7280-lpass-lpi.c | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/drivers/pinctrl/qcom/pinctrl-sc7280-lpass-lpi.c b/drivers/pinctrl/qcom/pinctrl-sc7280-lpass-lpi.c
>> index 2add9a4..c9e85d9 100644
>> --- a/drivers/pinctrl/qcom/pinctrl-sc7280-lpass-lpi.c
>> +++ b/drivers/pinctrl/qcom/pinctrl-sc7280-lpass-lpi.c
>> @@ -134,6 +134,16 @@ static const struct lpi_function sc7280_functions[] = {
>> LPI_FUNCTION(wsa_swr_data),
>> };
>>
>> +static const struct lpi_pinctrl_variant_data sc7280_adsp_lpi_data = {
>> + .pins = sc7280_lpi_pins,
>> + .npins = ARRAY_SIZE(sc7280_lpi_pins),
>> + .groups = sc7280_groups,
>> + .ngroups = ARRAY_SIZE(sc7280_groups),
>> + .functions = sc7280_functions,
>> + .nfunctions = ARRAY_SIZE(sc7280_functions),
>> + .is_clk_optional = false,
>> +};
>> +
>> static const struct lpi_pinctrl_variant_data sc7280_lpi_data = {
>> .pins = sc7280_lpi_pins,
>> .npins = ARRAY_SIZE(sc7280_lpi_pins),
>> @@ -149,6 +159,10 @@ static const struct of_device_id lpi_pinctrl_of_match[] = {
>> .compatible = "qcom,sc7280-lpass-lpi-pinctrl",
>> .data = &sc7280_lpi_data,
>> },
>> + {
>> + .compatible = "qcom,sc7280-lpass-adsp-lpi-pinctrl",
>> + .data = &sc7280_adsp_lpi_data,
>> + },
>> { }
>> };
>> MODULE_DEVICE_TABLE(of, lpi_pinctrl_of_match);
>> --
>> 2.7.4
>>
prev parent reply other threads:[~2022-06-01 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 13:56 [PATCH 0/2] Add pinctrl support adsp based platforms Srinivasa Rao Mandadapu
2022-05-04 13:56 ` [PATCH 1/2] dt-bindings: pinctrl: qcom: sc7280: Add compatible string for " Srinivasa Rao Mandadapu
2022-05-05 17:28 ` Rob Herring
2022-05-04 13:56 ` [PATCH 2/2] pinctrl: qcom: sc7280: Add lpi pinctrl variant data structure for adsp based targets Srinivasa Rao Mandadapu
2022-05-16 15:17 ` Bjorn Andersson
2022-06-01 9:56 ` Srinivasa Rao Mandadapu [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=26bfd089-46d6-d08d-efac-71ffc04f674c@quicinc.com \
--to=quic_srivasam@quicinc.com \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@quicinc.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=judyhsiao@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_plai@quicinc.com \
--cc=quic_potturu@quicinc.com \
--cc=quic_rohkumar@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.org \
--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
all inboxes | Powered by JetHome®