public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Ashish Mhetre <amhetre@nvidia.com>,
	jonathanh@nvidia.com, digetx@gmail.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, dmitry.osipenko@collabora.com,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	devicetree@vger.kernel.org, vdumpa@nvidia.com, Snikam@nvidia.com
Subject: Re: [Patch v9 1/4] memory: tegra: Add memory controller channels support
Date: Fri, 29 Apr 2022 10:30:20 +0200	[thread overview]
Message-ID: <YmuiHHcdrtI6zry9@orome> (raw)
In-Reply-To: <2f600411-d40e-c4e7-fd54-bd15546bf71f@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

On Fri, Apr 29, 2022 at 09:11:59AM +0200, Krzysztof Kozlowski wrote:
> On 26/04/2022 09:38, Ashish Mhetre wrote:
> > From tegra186 onwards, memory controller support multiple channels.
> > Add support for mapping address spaces of these channels.
> > Add number of channels supported by tegra186, tegra194 and tegra234.
> > In case of old bindings, channels won't be present. If channels are not
> > present then print warning and continue so that backward compatibility
> > will be preserved in driver.
> > During error interrupts from memory controller, appropriate registers
> > from these channels need to be accessed for logging error info.
> > 
> > Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> > Signed-off-by: Ashish Mhetre <amhetre@nvidia.com>
> > ---
> >  drivers/memory/tegra/mc.c       |  6 ++++++
> >  drivers/memory/tegra/tegra186.c | 34 +++++++++++++++++++++++++++++++++
> >  drivers/memory/tegra/tegra194.c |  1 +
> >  drivers/memory/tegra/tegra234.c |  1 +
> 
> This does not apply, neither on my mem-ctrl-next, nor on master.
> Probably because tegra234 is somewhere else (Thierry?). Either you send
> it without tegra234 or it goes via Thierry's tree.

Yeah, I can apply these on top of my tree and then forward the whole
batch to you or ARM SoC next week.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-04-29  8:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  7:38 [Patch v9 0/4] memory: tegra: Add MC channels and error logging Ashish Mhetre
2022-04-26  7:38 ` [Patch v9 1/4] memory: tegra: Add memory controller channels support Ashish Mhetre
2022-04-29  7:11   ` Krzysztof Kozlowski
2022-04-29  8:30     ` Thierry Reding [this message]
2022-04-29  8:50   ` Dmitry Osipenko
2022-04-29 10:47     ` Ashish Mhetre
2022-04-26  7:38 ` [Patch v9 2/4] memory: tegra: Add MC error logging on tegra186 onward Ashish Mhetre
2022-04-26  7:38 ` [Patch v9 3/4] dt-bindings: memory: tegra: Update validation for reg and reg-names Ashish Mhetre
2022-04-26  7:38 ` [Patch v9 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=YmuiHHcdrtI6zry9@orome \
    --to=thierry.reding@gmail.com \
    --cc=Snikam@nvidia.com \
    --cc=amhetre@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=dmitry.osipenko@collabora.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=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