From: Ashish Mhetre <amhetre@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
krzysztof.kozlowski@linaro.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org
Cc: vdumpa@nvidia.com, Snikam@nvidia.com
Subject: Re: [Patch v6 1/4] memory: tegra: Add memory controller channels support
Date: Mon, 11 Apr 2022 11:50:14 +0530 [thread overview]
Message-ID: <eac41cf0-6057-2f52-26fd-50a0fbecd7a8@nvidia.com> (raw)
In-Reply-To: <bf23e357-1e74-6bbe-7f37-11147654e5fc@gmail.com>
On 4/10/2022 8:34 PM, Dmitry Osipenko wrote:
> External email: Use caution opening links or attachments
>
>
> 06.04.2022 08:24, Ashish Mhetre пишет:
>> diff --git a/include/soc/tegra/mc.h b/include/soc/tegra/mc.h
>> index 1066b1194a5a..c3c121fbfbb7 100644
>> --- a/include/soc/tegra/mc.h
>> +++ b/include/soc/tegra/mc.h
>> @@ -13,6 +13,9 @@
>> #include <linux/irq.h>
>> #include <linux/reset-controller.h>
>> #include <linux/types.h>
>> +#include <linux/platform_device.h>
>> +
>> +#define MC_MAX_CHANNELS 16
>>
>> struct clk;
>> struct device;
>> @@ -181,6 +184,7 @@ struct tegra_mc_ops {
>> int (*resume)(struct tegra_mc *mc);
>> irqreturn_t (*handle_irq)(int irq, void *data);
>> int (*probe_device)(struct tegra_mc *mc, struct device *dev);
>> + int (*map_regs)(struct tegra_mc *mc, struct platform_device *pdev);
>> };
>>
>> struct tegra_mc_soc {
>> @@ -194,6 +198,7 @@ struct tegra_mc_soc {
>> unsigned int atom_size;
>>
>> u8 client_id_mask;
>> + u8 num_channels;
>>
>> const struct tegra_smmu_soc *smmu;
>>
>> @@ -212,6 +217,8 @@ struct tegra_mc {
>> struct tegra_smmu *smmu;
>> struct gart_device *gart;
>> void __iomem *regs;
>> + void __iomem *bcast_ch_regs;
>> + void __iomem *ch_regs[MC_MAX_CHANNELS];
>
> Why not to allocate ch_regs at runtime?
Yes, we can do that. I'll make necessary changes in v7.
next prev parent reply other threads:[~2022-04-11 6:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 5:24 [Patch v6 0/4] memory: tegra: Add MC channels and error logging Ashish Mhetre
2022-04-06 5:24 ` [Patch v6 1/4] memory: tegra: Add memory controller channels support Ashish Mhetre
2022-04-10 14:18 ` Dmitry Osipenko
2022-04-11 6:05 ` Ashish Mhetre
2022-04-11 6:33 ` Dmitry Osipenko
2022-04-11 7:28 ` Ashish Mhetre
2022-04-11 7:35 ` Dmitry Osipenko
2022-04-11 9:18 ` Ashish Mhetre
2022-04-11 11:13 ` Dmitry Osipenko
2022-04-10 15:01 ` Dmitry Osipenko
2022-04-11 6:18 ` Ashish Mhetre
2022-04-10 15:04 ` Dmitry Osipenko
2022-04-11 6:20 ` Ashish Mhetre [this message]
2022-04-06 5:24 ` [Patch v6 2/4] memory: tegra: Add MC error logging on tegra186 onward Ashish Mhetre
2022-04-10 14:55 ` Dmitry Osipenko
2022-04-11 6:17 ` Ashish Mhetre
2022-04-06 5:24 ` [Patch v6 3/4] dt-bindings: memory: Update reg maxitems for tegra186 Ashish Mhetre
2022-04-10 14:21 ` Dmitry Osipenko
2022-04-11 6:09 ` Ashish Mhetre
2022-04-11 15:02 ` Ashish Mhetre
2022-04-11 15:29 ` Dmitry Osipenko
2022-04-11 15:41 ` Ashish Mhetre
2022-04-11 22:28 ` Dmitry Osipenko
2022-04-12 4:11 ` Ashish Mhetre
2022-04-06 5:24 ` [Patch v6 4/4] arm64: tegra: Add memory controller channels Ashish Mhetre
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=eac41cf0-6057-2f52-26fd-50a0fbecd7a8@nvidia.com \
--to=amhetre@nvidia.com \
--cc=Snikam@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@nvidia.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