All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Alexandre Courbot <acourbot@nvidia.com>
Cc: Russell King <linux@arm.linux.org.uk>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Tomasz Figa <t.figa@samsung.com>, Olof Johansson <olof@lixom.net>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-samsung-soc@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: move firmware_ops to drivers/firmware
Date: Mon, 18 Nov 2013 10:00:32 -0700	[thread overview]
Message-ID: <528A47B0.1090800@wwwdotorg.org> (raw)
In-Reply-To: <CAHkRjk5LBOFx3ir49RgEsaFwvp5UCpTjYFWto+URXebAsOP0RA@mail.gmail.com>

On 11/17/2013 08:59 AM, Catalin Marinas wrote:
> On 17 November 2013 08:49, Alexandre Courbot <acourbot@nvidia.com> wrote:
>> The ARM tree includes a firmware_ops interface that is designed to
>> implement support for simple, TrustZone-based firmwares but could
>> also cover other use-cases. It has been suggested that this
>> interface might be useful to other architectures (e.g. arm64) and
>> that it should be moved out of arch/arm.
> 
> NAK. I'm for code sharing with arm via common locations but this API
> goes against the ARMv8 firmware standardisation efforts like PSCI,
> encouraging each platform to define there own non-standard interface.

Surely PSCI is *an* implementation of firmware_ops?

Couldn't firmware_ops be relevant to non-ARM architectures too? If so,
that would support my previous point; we're presumably not requiring
non-ARM architectures to implement PSCI?

On a practical note, unless ARM mandates by ARM architecture licensing
condition that mechanisms other than PSCI are not allowed, then they're
going to exist even if the upstream Linux community doesn't like it.
History has certainly shown that.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: move firmware_ops to drivers/firmware
Date: Mon, 18 Nov 2013 10:00:32 -0700	[thread overview]
Message-ID: <528A47B0.1090800@wwwdotorg.org> (raw)
In-Reply-To: <CAHkRjk5LBOFx3ir49RgEsaFwvp5UCpTjYFWto+URXebAsOP0RA@mail.gmail.com>

On 11/17/2013 08:59 AM, Catalin Marinas wrote:
> On 17 November 2013 08:49, Alexandre Courbot <acourbot@nvidia.com> wrote:
>> The ARM tree includes a firmware_ops interface that is designed to
>> implement support for simple, TrustZone-based firmwares but could
>> also cover other use-cases. It has been suggested that this
>> interface might be useful to other architectures (e.g. arm64) and
>> that it should be moved out of arch/arm.
> 
> NAK. I'm for code sharing with arm via common locations but this API
> goes against the ARMv8 firmware standardisation efforts like PSCI,
> encouraging each platform to define there own non-standard interface.

Surely PSCI is *an* implementation of firmware_ops?

Couldn't firmware_ops be relevant to non-ARM architectures too? If so,
that would support my previous point; we're presumably not requiring
non-ARM architectures to implement PSCI?

On a practical note, unless ARM mandates by ARM architecture licensing
condition that mechanisms other than PSCI are not allowed, then they're
going to exist even if the upstream Linux community doesn't like it.
History has certainly shown that.

  parent reply	other threads:[~2013-11-18 17:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-17  8:49 [PATCH] ARM: move firmware_ops to drivers/firmware Alexandre Courbot
2013-11-17  8:49 ` Alexandre Courbot
2013-11-17 15:59 ` Catalin Marinas
2013-11-17 15:59   ` Catalin Marinas
2013-11-18  3:05   ` Alex Courbot
2013-11-18  3:05     ` Alex Courbot
2013-11-18 11:58     ` Catalin Marinas
2013-11-18 11:58       ` Catalin Marinas
2013-11-18 11:58       ` Catalin Marinas
2013-11-18 17:03       ` Stephen Warren
2013-11-18 17:03         ` Stephen Warren
2013-11-18 17:10         ` Russell King - ARM Linux
2013-11-18 17:10           ` Russell King - ARM Linux
2013-11-18 17:18           ` Stephen Warren
2013-11-18 17:18             ` Stephen Warren
2013-11-18 17:30         ` Catalin Marinas
2013-11-18 17:30           ` Catalin Marinas
2013-11-18 17:52           ` Stephen Warren
2013-11-18 17:52             ` Stephen Warren
2013-11-19 11:38             ` Catalin Marinas
2013-11-19 11:38               ` Catalin Marinas
2013-11-19 11:38               ` Catalin Marinas
2013-11-18 19:04           ` Christopher Covington
2013-11-18 19:04             ` Christopher Covington
2013-11-19 11:02             ` Catalin Marinas
2013-11-19 11:02               ` Catalin Marinas
2013-11-19 11:02               ` Catalin Marinas
2013-11-19  2:46       ` Alex Courbot
2013-11-19  2:46         ` Alex Courbot
2013-11-19 12:26         ` Catalin Marinas
2013-11-19 12:26           ` Catalin Marinas
2013-11-19 12:26           ` Catalin Marinas
2013-11-19 14:29           ` Alexandre Courbot
2013-11-19 14:29             ` Alexandre Courbot
2013-11-19 15:07             ` Catalin Marinas
2013-11-19 15:07               ` Catalin Marinas
2013-11-19 15:07               ` Catalin Marinas
2013-11-19 15:17               ` Alexandre Courbot
2013-11-19 15:17                 ` Alexandre Courbot
2013-11-18 17:00   ` Stephen Warren [this message]
2013-11-18 17:00     ` Stephen Warren
2013-11-18 17:23     ` Catalin Marinas
2013-11-18 17:23       ` Catalin Marinas
2013-11-18 17:14   ` Russell King - ARM Linux
2013-11-18 17:14     ` Russell King - ARM Linux

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=528A47B0.1090800@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=acourbot@nvidia.com \
    --cc=catalin.marinas@arm.com \
    --cc=gnurou@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=olof@lixom.net \
    --cc=t.figa@samsung.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.