All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>, arm@kernel.org
Cc: linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [GIT PULL 3/8] memory: tegra: Changes for v5.5-rc1
Date: Mon, 4 Nov 2019 18:34:47 +0300	[thread overview]
Message-ID: <2f1c8899-ffda-51f0-64f4-48aa23dc1823@gmail.com> (raw)
In-Reply-To: <20191102144521.3863321-3-thierry.reding@gmail.com>

02.11.2019 17:45, Thierry Reding пишет:
> Hi ARM SoC maintainers,
> 
> The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
> 
>   Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.5-memory
> 
> for you to fetch changes up to 8b04225c4464422f185e62c2cedfb9e234423814:
> 
>   memory: tegra: Consolidate registers definition into common header (2019-11-01 10:57:37 +0100)
> 
> Thanks,
> Thierry
> 
> ----------------------------------------------------------------
> memory: tegra: Changes for v5.5-rc1
> 
> This contains a couple of fixes and adds support for EMC frequency
> scaling on Tegra30.
> 
> ----------------------------------------------------------------
> Dmitry Osipenko (11):
>       clk: tegra: Add Tegra20/30 EMC clock implementation
>       memory: tegra: Don't set EMC rate to maximum on probe for Tegra20
>       memory: tegra: Adapt for Tegra20 clock driver changes
>       memory: tegra: Include io.h instead of iopoll.h
>       memory: tegra: Pre-configure debug register on Tegra20
>       memory: tegra: Print a brief info message about EMC timings
>       memory: tegra: Increase handshake timeout on Tegra20
>       memory: tegra: Do not handle error from wait_for_completion_timeout()
>       memory: tegra: Introduce Tegra30 EMC driver
>       memory: tegra: Ensure timing control debug features are disabled
>       memory: tegra: Consolidate registers definition into common header
> 
> Sowjanya Komatineni (1):
>       clk: Add API to get index of the clock parent

Hello Thierry,

I want to point out that it looks like this patch from Sowjanya
shouldn't belong to this pull request because it is unrelated to the
memory patches.

Also, this patch haven't got an ack from the clk maintainers yet and I
assume that it needs an ack.

I'm just wanting to get yours attention in a case if this patch was
added by mistake. If it was intentional, then perhaps it should be okay.

> Thierry Reding (3):
>       Merge branch 'for-5.5/clk'
>       memory: tegra: Set DMA mask based on supported address bits
>       memory: tegra: Add gr2d and gr3d to DRM IOMMU group
> 
>  drivers/clk/clk.c                   |   17 +
>  drivers/clk/tegra/Makefile          |    2 +
>  drivers/clk/tegra/clk-tegra20-emc.c |  293 +++++++++
>  drivers/clk/tegra/clk-tegra20.c     |   55 +-
>  drivers/clk/tegra/clk-tegra30.c     |   38 +-
>  drivers/clk/tegra/clk.h             |    3 +
>  drivers/memory/tegra/Kconfig        |   10 +
>  drivers/memory/tegra/Makefile       |    1 +
>  drivers/memory/tegra/mc.c           |   52 +-
>  drivers/memory/tegra/mc.h           |   74 ++-
>  drivers/memory/tegra/tegra114.c     |   10 +-
>  drivers/memory/tegra/tegra124.c     |   30 +-
>  drivers/memory/tegra/tegra20-emc.c  |  134 ++--
>  drivers/memory/tegra/tegra30-emc.c  | 1232 +++++++++++++++++++++++++++++++++++
>  drivers/memory/tegra/tegra30.c      |   34 +-
>  include/linux/clk-provider.h        |    1 +
>  include/linux/clk/tegra.h           |   11 +
>  include/soc/tegra/mc.h              |    2 +-
>  18 files changed, 1797 insertions(+), 202 deletions(-)
>  create mode 100644 drivers/clk/tegra/clk-tegra20-emc.c
>  create mode 100644 drivers/memory/tegra/tegra30-emc.c
> 


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-11-04 15:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02 14:45 [GIT PULL 1/8] dt-bindings: Changes for v5.5-rc1 Thierry Reding
2019-11-02 14:45 ` Thierry Reding
2019-11-02 14:45 ` [GIT PULL 2/8] firmware: tegra: " Thierry Reding
2019-11-02 14:45   ` Thierry Reding
2019-11-02 14:45 ` [GIT PULL 3/8] memory: " Thierry Reding
2019-11-02 14:45   ` Thierry Reding
2019-11-04  1:33   ` Olof Johansson
2019-11-04  1:33     ` Olof Johansson
2019-11-04 15:34   ` Dmitry Osipenko [this message]
2019-11-07 15:32     ` Thierry Reding
2019-11-11 14:38   ` [GIT PULL v2 " Thierry Reding
2019-11-11 14:38     ` Thierry Reding
2019-11-02 14:45 ` [GIT PULL 4/8] soc/tegra: " Thierry Reding
2019-11-02 14:45   ` Thierry Reding
2019-11-02 14:45 ` [GIT PULL 5/8] ARM: tegra: Core changes " Thierry Reding
2019-11-02 14:45   ` Thierry Reding
2019-11-02 14:45 ` [GIT PULL 6/8] ARM: tegra: Device tree " Thierry Reding
2019-11-02 14:45   ` Thierry Reding
2019-11-02 14:45 ` [GIT PULL 7/8] ARM: tegra: Default configuration " Thierry Reding
2019-11-02 14:45   ` Thierry Reding
2019-11-02 14:45 ` [GIT PULL 8/8] arm64: tegra: Device tree " Thierry Reding
2019-11-02 14:45   ` Thierry Reding

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=2f1c8899-ffda-51f0-64f4-48aa23dc1823@gmail.com \
    --to=digetx@gmail.com \
    --cc=arm@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.