From: Greg KH <gregkh@linuxfoundation.org>
To: Jolly Shah <jolly.shah@xilinx.com>
Cc: ard.biesheuvel@linaro.org, mingo@kernel.org,
matt@codeblueprint.co.uk, sudeep.holla@arm.com,
hkallweit1@gmail.com, keescook@chromium.org,
dmitry.torokhov@gmail.com, michal.simek@xilinx.com,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
rajanv@xilinx.com, Jolly Shah <jollys@xilinx.com>
Subject: Re: [PATCH v2 2/4] drivers: firmware: xilinx: Add ZynqMP firmware driver
Date: Tue, 23 Jan 2018 09:38:23 +0100 [thread overview]
Message-ID: <20180123083823.GB21463@kroah.com> (raw)
In-Reply-To: <1516220434-22204-3-git-send-email-jollys@xilinx.com>
On Wed, Jan 17, 2018 at 12:20:32PM -0800, Jolly Shah wrote:
> This patch is adding communication layer with firmware.
> Firmware driver provides an interface to firmware APIs.
> Interface APIs can be used by any driver to communicate to
> PMUFW(Platform Management Unit). All requests go through ATF.
>
> Signed-off-by: Jolly Shah <jollys@xilinx.com>
> Signed-off-by: Rajan Vaja <rajanv@xilinx.com>
> ---
> arch/arm64/Kconfig.platforms | 1 +
> drivers/firmware/Kconfig | 1 +
> drivers/firmware/Makefile | 1 +
> drivers/firmware/xilinx/Kconfig | 4 +
> drivers/firmware/xilinx/Makefile | 4 +
> drivers/firmware/xilinx/zynqmp/Kconfig | 16 +
> drivers/firmware/xilinx/zynqmp/Makefile | 4 +
> drivers/firmware/xilinx/zynqmp/firmware.c | 987 ++++++++++++++++++++++++
> include/linux/firmware/xilinx/zynqmp/firmware.h | 570 ++++++++++++++
Why does this file need to be in include/linux/ at all? Shouldn't it
just live in the driver-specific subdir?
thanks,
greg k-h
next prev parent reply other threads:[~2018-01-23 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 20:20 [PATCH v2 0/4] drivers: firmware: xilinx: Add firmware driver support Jolly Shah
[not found] ` <1516220434-22204-1-git-send-email-jollys-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2018-01-17 20:20 ` [PATCH v2 1/4] dt-bindings: firmware: Add bindings for ZynqMP firmware Jolly Shah
2018-01-17 20:20 ` [PATCH v2 4/4] drivers: firmware: xilinx: Add debugfs interface Jolly Shah
[not found] ` <1516220434-22204-5-git-send-email-jollys-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2018-01-23 8:41 ` Greg KH
2018-01-24 23:33 ` Jolly Shah
2018-01-17 20:20 ` [PATCH v2 2/4] drivers: firmware: xilinx: Add ZynqMP firmware driver Jolly Shah
2018-01-23 8:38 ` Greg KH [this message]
[not found] ` <20180123083823.GB21463-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2018-01-24 23:28 ` Jolly Shah
2018-01-17 20:20 ` [PATCH v2 3/4] drivers: firmware: xilinx: Add sysfs interface Jolly Shah
2018-01-23 8:37 ` Greg KH
2018-01-24 23:30 ` Jolly Shah
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=20180123083823.GB21463@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jolly.shah@xilinx.com \
--cc=jollys@xilinx.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matt@codeblueprint.co.uk \
--cc=michal.simek@xilinx.com \
--cc=mingo@kernel.org \
--cc=rajanv@xilinx.com \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).