All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL 4/4] sgx soc glue changes for omaps for v5.4
Date: Wed, 4 Sep 2019 17:27:37 +0200	[thread overview]
Message-ID: <CAK8P3a1s2go50eYiWQw5DCUEajy2QozKKfs4_Uo6xWUKL3eyrA@mail.gmail.com> (raw)
In-Reply-To: <pull-1567016893-318461@atomide.com-4>

On Wed, Aug 28, 2019 at 8:35 PM Tony Lindgren <tony@atomide.com> wrote:
> SoC glue layer changes for SGX on omap variants for v5.4
>
> For a while we've had omap4 sgx glue layer defined in dts and probed
> with ti-sysc driver. This allows idling the sgx module for PM, and
> removes the need for custom platform glue layer code for any further
> driver changes.
>
> We first drop the unused legacy platform data for omap4 sgx. Then for
> omap5, we need add the missing clkctrl clock data so we can configure
> sgx. And we configure sgx for omap34xx, omap36xx and am3517.
>
> For am335x, we still have a dependency for rstctrl reset driver changes,
> so that will be added later on.
>
> Note that this branch is based on earlier ti-sysc branch for omap36xx
> glue layer quirk handling.

Pulled into arm/late, thanks!

        Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL 4/4] sgx soc glue changes for omaps for v5.4
Date: Wed, 4 Sep 2019 17:27:37 +0200	[thread overview]
Message-ID: <CAK8P3a1s2go50eYiWQw5DCUEajy2QozKKfs4_Uo6xWUKL3eyrA@mail.gmail.com> (raw)
In-Reply-To: <pull-1567016893-318461@atomide.com-4>

On Wed, Aug 28, 2019 at 8:35 PM Tony Lindgren <tony@atomide.com> wrote:
> SoC glue layer changes for SGX on omap variants for v5.4
>
> For a while we've had omap4 sgx glue layer defined in dts and probed
> with ti-sysc driver. This allows idling the sgx module for PM, and
> removes the need for custom platform glue layer code for any further
> driver changes.
>
> We first drop the unused legacy platform data for omap4 sgx. Then for
> omap5, we need add the missing clkctrl clock data so we can configure
> sgx. And we configure sgx for omap34xx, omap36xx and am3517.
>
> For am335x, we still have a dependency for rstctrl reset driver changes,
> so that will be added later on.
>
> Note that this branch is based on earlier ti-sysc branch for omap36xx
> glue layer quirk handling.

Pulled into arm/late, thanks!

        Arnd

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

  reply	other threads:[~2019-09-04 15:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 18:34 [GIT PULL 1/4] soc changes for omap variants for v5.4 Tony Lindgren
2019-08-28 18:34 ` Tony Lindgren
2019-08-28 18:34 ` [GIT PULL 2/4] more ti-sysc driver changes " Tony Lindgren
2019-08-28 18:34   ` Tony Lindgren
2019-09-04 15:26   ` Arnd Bergmann
2019-09-04 15:26     ` Arnd Bergmann
2019-08-28 18:34 ` [GIT PULL 3/4] drop more legacy pdata for omaps " Tony Lindgren
2019-08-28 18:34   ` Tony Lindgren
2019-09-04 15:27   ` Arnd Bergmann
2019-09-04 15:27     ` Arnd Bergmann
2019-08-28 18:34 ` [GIT PULL 4/4] sgx soc glue changes " Tony Lindgren
2019-08-28 18:34   ` Tony Lindgren
2019-09-04 15:27   ` Arnd Bergmann [this message]
2019-09-04 15:27     ` Arnd Bergmann
2019-09-03 12:25 ` [GIT PULL 1/4] soc changes for omap variants " Arnd Bergmann
2019-09-03 12:25   ` Arnd Bergmann

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=CAK8P3a1s2go50eYiWQw5DCUEajy2QozKKfs4_Uo6xWUKL3eyrA@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=soc@kernel.org \
    --cc=tony@atomide.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.