devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: barnabas.czeman@mainlining.org
To: Georgi Djakov <djakov@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	Vladimir Lypak <vladimir.lypak@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 2/2] interconnect: qcom: Add MSM8953 driver
Date: Fri, 28 Jun 2024 20:46:16 +0200	[thread overview]
Message-ID: <a4b6cff7ac6ae69ff8bfe76ab72544c3@mainlining.org> (raw)
In-Reply-To: <f0f09455-5bfd-4dbc-b393-dbef75441e8a@kernel.org>

On 2024-06-28 20:39, Georgi Djakov wrote:
> Hi Barnabás,
> 
> Thank you for the patches!
> 
> On 28.06.24 17:01, Barnabás Czémán wrote:
>> From: Vladimir Lypak <vladimir.lypak@gmail.com>
>> 
>> Add driver for interconnect busses found in MSM8953 based platforms.
>> The topology consists of four NoCs that are partially controlled by a
>> RPM processor.
>> 
>> Note that one of NoCs (System NoC) has a counterpart (System NoC MM)
>> that is modelled as child device to avoid resource conflicts, since it
>> uses same MMIO space for configuration.
>> 
>> Signed-off-by: Vladimir Lypak <vladimir.lypak@gmail.com>
>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
>> ---
>>   drivers/interconnect/qcom/Kconfig   |    9 +
>>   drivers/interconnect/qcom/Makefile  |    2 +
>>   drivers/interconnect/qcom/msm8953.c | 1321 
>> +++++++++++++++++++++++++++++++++++
>>   3 files changed, 1332 insertions(+)
> [..]
>> +++ b/drivers/interconnect/qcom/msm8953.c
> [..]
>> +static const struct of_device_id msm8953_noc_of_match[] = {
>> +	{ .compatible = "qcom,msm8953-bimc", .data = &msm8953_bimc },
>> +	{ .compatible = "qcom,msm8953-pcnoc", .data = &msm8953_pcnoc },
>> +	{ .compatible = "qcom,msm8953-snoc", .data = &msm8953_snoc },
>> +	{ .compatible = "qcom,msm8953-snoc-mm", .data = &msm8953_snoc_mm },
>> +	{ }
>> +};
>> +
>> +static struct platform_driver msm8953_noc_driver = {
>> +	.probe = qnoc_probe,
>> +	.remove_new = qnoc_remove,
>> +	.driver = {
>> +		.name = "qnoc-msm8953",
>> +		.of_match_table = msm8953_noc_of_match,
> 
> Why no .sync_state?
Because there is no cpufreq upstreamed
> 
> BR,
> Georgi

      reply	other threads:[~2024-06-28 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 14:01 [PATCH v3 0/2] Add interconnect driver for MSM8953/SDM450/SDM632 Barnabás Czémán
2024-06-28 14:01 ` [PATCH v3 1/2] dt-bindings: interconnect: qcom: Add Qualcomm MSM8953 NoC Barnabás Czémán
2024-06-28 14:01 ` [PATCH v3 2/2] interconnect: qcom: Add MSM8953 driver Barnabás Czémán
2024-06-28 18:39   ` Georgi Djakov
2024-06-28 18:46     ` barnabas.czeman [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=a4b6cff7ac6ae69ff8bfe76ab72544c3@mainlining.org \
    --to=barnabas.czeman@mainlining.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=vladimir.lypak@gmail.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).