devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Georgi Djakov <georgi.djakov@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [RFC 2/2] dt-bindings: firmware: tegra186-bpmp: Document interconnects property
Date: Tue, 28 Jan 2020 22:27:00 +0300	[thread overview]
Message-ID: <d56618e1-8940-65ae-381e-796e44bcf537@gmail.com> (raw)
In-Reply-To: <20200127122115.GA2117209@ulmo>

27.01.2020 15:21, Thierry Reding пишет:
> On Tue, Jan 21, 2020 at 11:12:11PM +0300, Dmitry Osipenko wrote:
>> 21.01.2020 18:54, Thierry Reding пишет:
>>> On Tue, Jan 21, 2020 at 05:18:43PM +0200, Georgi Djakov wrote:
>>>> On 1/21/20 16:10, Thierry Reding wrote:
> [...]
>>>>> I'm not sure if that TEGRA_ICC_EMEM makes a lot of sense. It's always
>>>>> going to be the same and it's arbitrarily defined, so it's effectively
>>>>> useless. But other than that it looks good.
>>>>
>>>> Well, in most cases the target would be the EMEM, so that's fine. I have seen
>>>> that other vendors that may have an additional internal memory, especially
>>>> dedicated to some DSPs and in such cases the bandwidth needs are different for
>>>> the two paths (to internal memory and DDR).
>>>
>>> Most chips have a small internal memory that can be used, though it
>>> seldomly is. However, in that case I would expect the target to be a
>>> completely different device, so it'd look more like this:
>>>
>>> 	interconnects = <&mc TEGRA186_MEMORY_CLIENT_BPMPR &iram>,
>>> 			...;
>>>
>>> I don't think EMEM has any "downstream" other than external memory.
>>
>> The node ID should be mandatory in terms of interconnect, even if it's a
>> single node. EMC (provider) != EMEM (endpoint).
> 
> I don't understand why. An ID only makes sense if you've got multiple
> endpoints. For example, a regulator is a provider with a single endpoint
> so we don't specify an ID.

Because this is how ICC binding is defined, unless I'm missing something.

> By its very definition an ID is used to identify something and we use it
> with a phandle to create a unique pair that identifies a resource within
> whatever the phandle represents, with the goal to differentiate it from
> other resources within the same provider. However, if there's only one
> such resource, the ID becomes redundant because the phandle without an
> ID is already unique and there's no need to differentiate with an extra
> ID.

Georgi, do you think it is possible to support what Thierry is asking for?

  reply	other threads:[~2020-01-28 19:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 18:15 [PATCH 1/2] dt-bindings: firmware: Convert Tegra186 BPMP bindings to json-schema Thierry Reding
2020-01-14 18:15 ` [RFC 2/2] dt-bindings: firmware: tegra186-bpmp: Document interconnects property Thierry Reding
2020-01-17 15:23   ` Georgi Djakov
2020-01-20 15:06     ` Thierry Reding
2020-01-21  6:53       ` Dmitry Osipenko
2020-01-21 14:10         ` Thierry Reding
2020-01-21 15:18           ` Georgi Djakov
2020-01-21 15:54             ` Thierry Reding
2020-01-21 20:12               ` Dmitry Osipenko
2020-01-26 21:56                 ` Dmitry Osipenko
2020-01-26 22:03                   ` Dmitry Osipenko
2020-01-27 12:52                     ` Thierry Reding
2020-01-27 12:49                   ` Thierry Reding
2020-02-05 21:34                     ` Dmitry Osipenko
2020-01-27 12:21                 ` Thierry Reding
2020-01-28 19:27                   ` Dmitry Osipenko [this message]
2020-01-29  9:36                     ` Thierry Reding
2020-01-29 16:02                       ` Dmitry Osipenko
2020-01-29 16:13                         ` Georgi Djakov
2020-01-29 16:16                           ` Dmitry Osipenko
2020-01-16 19:28 ` [PATCH 1/2] dt-bindings: firmware: Convert Tegra186 BPMP bindings to json-schema Rob Herring

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=d56618e1-8940-65ae-381e-796e44bcf537@gmail.com \
    --to=digetx@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=georgi.djakov@linaro.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@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).