From: Thierry Reding <thierry.reding@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 2/2] memory: tegra: Add DLA clients for Tegra234
Date: Fri, 28 Oct 2022 16:23:57 +0200 [thread overview]
Message-ID: <Y1vl/cyDUVFWzz1z@orome> (raw)
In-Reply-To: <4a4c2b3d-79e5-1f34-a031-77d1d1941000@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 3229 bytes --]
On Fri, Oct 28, 2022 at 09:07:28AM -0400, Krzysztof Kozlowski wrote:
> On 28/10/2022 09:05, Jon Hunter wrote:
> >
> > On 28/10/2022 13:52, Krzysztof Kozlowski wrote:
> >> On 28/10/2022 08:51, Jon Hunter wrote:
> >>>
> >>> On 28/10/2022 13:46, Krzysztof Kozlowski wrote:
> >>>> On 28/10/2022 08:37, Jon Hunter wrote:
> >>>>> Add the memory clients on Tegra234 which are needed for initialising the
> >>>>> SMMU for the Deep Learning Accelerator (DLA).
> >>>>>
> >>>>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> >>>>> ---
> >>>>> drivers/memory/tegra/tegra234.c | 160 ++++++++++++++++++++++++++++++++
> >>>>> 1 file changed, 160 insertions(+)
> >>>>>
> >>>>> diff --git a/drivers/memory/tegra/tegra234.c b/drivers/memory/tegra/tegra234.c
> >>>>> index a9e8fd99730f..9bdaf8af8c97 100644
> >>>>> --- a/drivers/memory/tegra/tegra234.c
> >>>>> +++ b/drivers/memory/tegra/tegra234.c
> >>>>> @@ -170,6 +170,166 @@ static const struct tegra_mc_client tegra234_mc_clients[] = {
> >>>>> .security = 0x504,
> >>>>> },
> >>>>> },
> >>>>> + }, {
> >>>>> + .id = TEGRA234_MEMORY_CLIENT_DLA0RDA,
> >>>>> + .name = "dla0rda",
> >>>>> + .sid = TEGRA234_SID_NVDLA0,
> >>>>
> >>>> This is now not applicable because you sent dependencies separate, mixed
> >>>> with other subsystems... Split pieces based on subsystems.
> >>>
> >>> Sorry I don't understand. This patch is dependent upon the first. I have
> >>> not sent anything separate.
> >>
> >> You sent mixed between subsystems patches adding TEGRA234_SID_NVDLA0.
> >> That one should have been sent separate so maintainers can pick it up.
> >
> > The original patch [0] I sent had no dependencies and so Thierry picked
> > this up. However, when adding patch 2/2 here, I noticed a typo in the
> > definition for TEGRA234_MEMORY_CLIENT_DLA0WRB so thought I would fix
> > this up while I am at it.
> >
> >> Now, it's not possible for me to pick this patch.
> >
> > Yes now you cannot simply pick this up. We have had similar problems
> > before. I am not sure if it is easiest for Thierry to pick these up.
> >
>
> And there is simple solution as I said - split the patches per
> subsystem. Why the dependency was combining multiple subsystems into one?
Splitting per subsystem doesn't really work in this case. The main
problem is that the dt-bindings headers are used by multiple subsystems,
and the content is not generated in a git-friendly way. So even if we
were to split things up, at some point there would be conflicts between
the various branches that these changes end up in.
The easiest solution for this is to simply take this through a single
tree. Normally this wouldn't be a problem because the symbols defined in
these headers are only used in device trees. However, for the memory
clients it is slightly complicated by the fact that the memory
controller driver also needs access to these symbols, so it creates an
interdependency between the dt-bindings, DT and memory controller
branches.
One of the reasons why Jon originally sent the larger patch, adding all
the missing IDs in one go, was precisely so we could avoid this hassle
in the future.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-10-28 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 12:37 [PATCH 1/2] dt-bindings: memory: Fix typos and definitions for Tegra Jon Hunter
2022-10-28 12:37 ` [PATCH 2/2] memory: tegra: Add DLA clients for Tegra234 Jon Hunter
2022-10-28 12:46 ` Krzysztof Kozlowski
2022-10-28 12:51 ` Jon Hunter
2022-10-28 12:52 ` Krzysztof Kozlowski
2022-10-28 13:05 ` Jon Hunter
2022-10-28 13:07 ` Krzysztof Kozlowski
2022-10-28 14:23 ` Thierry Reding [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=Y1vl/cyDUVFWzz1z@orome \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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