All of lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [GIT PULL] Amlogic 64-bit DT changes for v4.10, round 2
Date: Mon, 28 Nov 2016 10:27:10 -0800	[thread overview]
Message-ID: <m2fumbtq81.fsf@baylibre.com> (raw)
In-Reply-To: <CAFBinCAvziwM4U6qJnTV+nEMKaZH4G9xdTM0pY6O83+Edk=Ovw@mail.gmail.com> (Martin Blumenstingl's message of "Sat, 26 Nov 2016 16:07:21 +0100")

Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:

> Hi Kevin,
>
> On Wed, Nov 23, 2016 at 11:23 PM, Kevin Hilman <khilman@baylibre.com> wrote:
>> Arnd, Olof,
>>
>> Here's a final round of arm64 DT changes for Amlogic family SoCs.
> please note that SCPI is not working due to a change in Sudeep's
> repository which has not made it into the Amlogic tree yet:
> Sudeep's latest pull request indicates that we should use
> "arm,scpi-pre-1.0", while currently we are only using
> "amlogic,meson-gxbb-scpi": [0]

Yes, I had to drop that legacy compatible as it was still under
discsussion.  Now that it's agreed upon, I've just sent a patch to fix
that.

> I fixed that in the Amlogic .dts files in [1] but this patch has not
> been applied yet.
>
> No pressure on this one - I just want to save your time (so you don't
> have to search why SCPI is not working anymore)

Thanks!

Kevin

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-November/470842.html

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Amlogic 64-bit DT changes for v4.10, round 2
Date: Mon, 28 Nov 2016 10:27:10 -0800	[thread overview]
Message-ID: <m2fumbtq81.fsf@baylibre.com> (raw)
In-Reply-To: <CAFBinCAvziwM4U6qJnTV+nEMKaZH4G9xdTM0pY6O83+Edk=Ovw@mail.gmail.com> (Martin Blumenstingl's message of "Sat, 26 Nov 2016 16:07:21 +0100")

Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:

> Hi Kevin,
>
> On Wed, Nov 23, 2016 at 11:23 PM, Kevin Hilman <khilman@baylibre.com> wrote:
>> Arnd, Olof,
>>
>> Here's a final round of arm64 DT changes for Amlogic family SoCs.
> please note that SCPI is not working due to a change in Sudeep's
> repository which has not made it into the Amlogic tree yet:
> Sudeep's latest pull request indicates that we should use
> "arm,scpi-pre-1.0", while currently we are only using
> "amlogic,meson-gxbb-scpi": [0]

Yes, I had to drop that legacy compatible as it was still under
discsussion.  Now that it's agreed upon, I've just sent a patch to fix
that.

> I fixed that in the Amlogic .dts files in [1] but this patch has not
> been applied yet.
>
> No pressure on this one - I just want to save your time (so you don't
> have to search why SCPI is not working anymore)

Thanks!

Kevin

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-November/470842.html

  reply	other threads:[~2016-11-28 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 22:23 [GIT PULL] Amlogic 64-bit DT changes for v4.10, round 2 Kevin Hilman
2016-11-23 22:23 ` Kevin Hilman
2016-11-26 15:07 ` Martin Blumenstingl
2016-11-26 15:07   ` Martin Blumenstingl
2016-11-28 18:27   ` Kevin Hilman [this message]
2016-11-28 18:27     ` Kevin Hilman
2016-11-28 20:00 ` Kevin Hilman
2016-11-28 20:00   ` Kevin Hilman

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=m2fumbtq81.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=linus-amlogic@lists.infradead.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 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.