From: Olof Johansson <olof@lixom.net>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
ALKML <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>
Subject: Re: [GIT PULL] firmware: arm_ffa: Initial support for v5.14
Date: Tue, 15 Jun 2021 08:21:49 -0700 [thread overview]
Message-ID: <20210615152149.GB11724@lx2k> (raw)
In-Reply-To: <20210614170856.rs7jrke3gvpmu4km@bogus>
Hi,
On Mon, Jun 14, 2021 at 06:08:56PM +0100, Sudeep Holla wrote:
> Hi Olof,
>
> On Tue, Jun 01, 2021 at 10:58:38AM +0100, Sudeep Holla wrote:
> > Hi ARM SoC Team,
> >
> > Please pull !
> >
> > This is a new driver pull request. One of the arm64 patch is being
> > pulled from a stable arm64 branch for-next/ffa as the other patches
> > are dependent of the same.
> >
> > Background
> > ----------
> > This has been on the list for almost a year now with changing requirements.
> > Initially Arm KVM wanted to use this via userspace interface in VMM to
> > communicate with VMs. But it was later dropped in favour of arch-agnostic
> > interface[1].
> >
> > Also there was some discussion on the dt-bindings which was dropped
> > completely. Though we need to workaround the lack of full discoveribility
> > in v1.0 spec, it is now being fixed for the next version of the spec.
> >
>
> I see that you have pulled quite a lot of drivers and other SoC code
> including my scmi and juno ones that were sent more recently than this
> one. Just thought of checking if this is still in queue ? Sorry for the
> nag but this has been on a list almost a year. We missed v5.13 due to
> DT binding controveries(for good reasons) and we really don't want to
> miss v5.14
I held off because I wanted to spend a few cycles on looking into it before
blindly merging it.
Are there any implemented users of this (on either side) today? We normally
don't merge a framework in the kernel without having at least one user of it
also available.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof@lixom.net>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
ALKML <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>
Subject: Re: [GIT PULL] firmware: arm_ffa: Initial support for v5.14
Date: Tue, 15 Jun 2021 08:21:49 -0700 [thread overview]
Message-ID: <20210615152149.GB11724@lx2k> (raw)
Message-ID: <20210615152149.Uz0x60gU7hzV7DX3m1DkqScFebFE0ABZu3BY0yzVGaI@z> (raw)
In-Reply-To: <20210614170856.rs7jrke3gvpmu4km@bogus>
Hi,
On Mon, Jun 14, 2021 at 06:08:56PM +0100, Sudeep Holla wrote:
> Hi Olof,
>
> On Tue, Jun 01, 2021 at 10:58:38AM +0100, Sudeep Holla wrote:
> > Hi ARM SoC Team,
> >
> > Please pull !
> >
> > This is a new driver pull request. One of the arm64 patch is being
> > pulled from a stable arm64 branch for-next/ffa as the other patches
> > are dependent of the same.
> >
> > Background
> > ----------
> > This has been on the list for almost a year now with changing requirements.
> > Initially Arm KVM wanted to use this via userspace interface in VMM to
> > communicate with VMs. But it was later dropped in favour of arch-agnostic
> > interface[1].
> >
> > Also there was some discussion on the dt-bindings which was dropped
> > completely. Though we need to workaround the lack of full discoveribility
> > in v1.0 spec, it is now being fixed for the next version of the spec.
> >
>
> I see that you have pulled quite a lot of drivers and other SoC code
> including my scmi and juno ones that were sent more recently than this
> one. Just thought of checking if this is still in queue ? Sorry for the
> nag but this has been on a list almost a year. We missed v5.13 due to
> DT binding controveries(for good reasons) and we really don't want to
> miss v5.14
I held off because I wanted to spend a few cycles on looking into it before
blindly merging it.
Are there any implemented users of this (on either side) today? We normally
don't merge a framework in the kernel without having at least one user of it
also available.
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-15 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 9:58 [GIT PULL] firmware: arm_ffa: Initial support for v5.14 Sudeep Holla
2021-06-01 9:58 ` Sudeep Holla
2021-06-14 17:08 ` Sudeep Holla
2021-06-14 17:08 ` Sudeep Holla
2021-06-15 15:21 ` Olof Johansson [this message]
2021-06-15 15:21 ` Olof Johansson
2021-06-15 15:34 ` Sudeep Holla
2021-06-15 15:34 ` Sudeep Holla
2021-06-15 16:47 ` Olof Johansson
2021-06-15 16:47 ` Olof Johansson
2021-06-15 19:56 ` Sudeep Holla
2021-06-15 19:56 ` Sudeep Holla
2021-06-15 17:10 ` patchwork-bot+linux-soc
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=20210615152149.GB11724@lx2k \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@kernel.org \
--cc=sudeep.holla@arm.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.