mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Alexander Graf <agraf@suse.de>, Michal Simek <michal.simek@xilinx.com>
Cc: linux-arm-kernel@lists.infradead.org,
	"Punnaiah Choudary Kalluri"
	<punnaiah.choudary.kalluri@xilinx.com>,
	"Baoyou Xie" <baoyou.xie@linaro.org>,
	"Bharat Kumar Gogada" <bharatku@xilinx.com>,
	"Lucas Stach" <l.stach@pengutronix.de>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Nicolas Ferre" <nicolas.ferre@microchip.com>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"yangbo lu" <yangbo.lu@nxp.com>,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	"Alexandre Belloni" <alexandre.belloni@free-electrons.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Will Deacon" <will.deacon@arm.com>,
	devicetree@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
	"Moritz Fischer" <mdf@kernel.org>,
	"Michal Simek" <monstr@monstr.eu>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Simon Horman" <horms+renesas@verge.net.au>,
	linux-kernel@vger.kernel.org,
	"Marc Zyngier" <marc.zyngier@arm.com>
Subject: Re: [PATCH 0/3] arm64 xilinx zynqmp firmware interface
Date: Mon, 7 Aug 2017 08:09:32 +0200	[thread overview]
Message-ID: <1182e5f8-2588-32ff-8380-04273c28d1cd@xilinx.com> (raw)
In-Reply-To: <34C9E6FB-A8CA-462F-8B10-3E15F9EC87D4@suse.de>

On 5.8.2017 06:23, Alexander Graf wrote:
> 
> 
>> Am 04.08.2017 um 15:45 schrieb Michal Simek <michal.simek@xilinx.com>:
>>
>> Hi,
>>
>> xilinx is using this interface for very long time and we can't merge our
>> driver changes to Linux because of missing communication layer with
>> firmware. This interface was developed before scpi and scmi was
>> available. In connection to power management scpi and scmi are missing
>> pieces which we already use. There is a separate discussion how to
>> extend scmi to support all our use cases.
>> This simply patch is not adding any power management features but only
>> adding minimum functionality which are needed for drivers.
> 
> If you're thinking of changing the interface later down the road, wouldn't it make sense to probe EL3 for its existence? 
You could then expose this interface on today's EL3 and something
scpi/scmi based on tomorrow's.

Right now driver is checking pmu firmware version. Based on this it is
clear how to communicate with it. The same checking could be there for
ATF version. Both of these should tell you exactly what's the
communication channel.
If we decide to use scmi or any other implementation we will increase
versions.

Thanks,
Michal

      reply	other threads:[~2017-08-07  6:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 13:45 Michal Simek
2017-08-04 13:45 ` [PATCH 1/3] dt: xilinx: zynqmp: Add bindings for PM firmware Michal Simek
2017-08-10 19:10   ` Rob Herring
2017-08-11 12:58     ` Michal Simek
2017-08-11 13:54       ` Edgar E. Iglesias
2017-08-14 13:47         ` Michal Simek
2017-08-14 14:03           ` Rob Herring
2017-08-14 14:35             ` Michal Simek
2017-08-04 13:45 ` [PATCH 2/3] arm64: zynqmp: dt: Add PM firmware node Michal Simek
2017-08-04 13:45 ` [PATCH 3/3] soc: xilinx: zynqmp: Add firmware interface Michal Simek
2017-08-14 15:06   ` Arnd Bergmann
2017-08-16 11:51     ` Michal Simek
2017-08-16 12:05       ` Michal Simek
2017-08-16 12:41       ` Arnd Bergmann
2017-08-16 14:00         ` Michal Simek
2017-08-16 14:34           ` Michal Simek
2017-08-16 15:05             ` Arnd Bergmann
2017-08-17 10:48               ` Michal Simek
2017-08-17 21:11                 ` Arnd Bergmann
2017-08-18 12:14                   ` Michal Simek
2017-08-05  4:23 ` [PATCH 0/3] arm64 xilinx zynqmp " Alexander Graf
2017-08-07  6:09   ` Michal Simek [this message]

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=1182e5f8-2588-32ff-8380-04273c28d1cd@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=baoyou.xie@linaro.org \
    --cc=bharatku@xilinx.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=krzk@kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=mdf@kernel.org \
    --cc=monstr@monstr.eu \
    --cc=nicolas.ferre@microchip.com \
    --cc=punnaiah.choudary.kalluri@xilinx.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=soren.brinkmann@xilinx.com \
    --cc=will.deacon@arm.com \
    --cc=yangbo.lu@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®