Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 4/7] dt-bindings: fpga: add Stratix10 SoC FPGA manager binding
Date: Wed, 7 Mar 2018 13:47:45 -0600	[thread overview]
Message-ID: <20180307194745.657ewa6rtcta6eqm@rob-hp-laptop> (raw)
In-Reply-To: <1519949975-13548-5-git-send-email-richard.gong@linux.intel.com>

On Thu, Mar 01, 2018 at 06:19:32PM -0600, richard.gong at linux.intel.com wrote:
> From: Alan Tull <atull@kernel.org>
> 
> Add a Device Tree binding for the Intel Stratix10 SoC FPGA manager.
> 
> Signed-off-by: Alan Tull <atull@kernel.org>
> ---
> v2: this patch is added in patch set version 2
> ---
>  .../devicetree/bindings/fpga/intel-stratix10-soc-fpga-mgr.txt  | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/fpga/intel-stratix10-soc-fpga-mgr.txt
> 
> diff --git a/Documentation/devicetree/bindings/fpga/intel-stratix10-soc-fpga-mgr.txt b/Documentation/devicetree/bindings/fpga/intel-stratix10-soc-fpga-mgr.txt
> new file mode 100644
> index 0000000..78de689
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/fpga/intel-stratix10-soc-fpga-mgr.txt
> @@ -0,0 +1,10 @@
> +Intel Stratix10 SoC FPGA Manager
> +
> +Required properties:
> +- compatible : should contain "intel,stratix10-soc-fpga-mgr"
> +
> +Example:
> +
> +	fpga_mgr: fpga-mgr at 0 {
> +		compatible = "intel,stratix10-soc-fpga-mgr";

No reg or anything else? Is that because it all goes thru the service 
layer firmware? Just get the service layer driver to instantiate a 
device for this driver or get rid of the 2 layers if that's all the 
firmware interface does. DT is not a Linux driver instantiation 
mechanism.

And build your dts files with "W=1" because there's an error in this 
example.

Rob

  reply	other threads:[~2018-03-07 19:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02  0:19 [PATCHv2 0/7] Add Intel Stratix10 FPGA manager and service layer richard.gong at linux.intel.com
2018-03-02  0:19 ` [PATCHv2 1/7] dt-bindings, firmware: add Intel Stratix10 service layer binding richard.gong at linux.intel.com
2018-03-07 19:39   ` Rob Herring
2018-03-02  0:19 ` [PATCHv2 2/7] arm64: dts: stratix10: add service driver binding to base dtsi richard.gong at linux.intel.com
2018-03-02  0:19 ` [PATCHv2 3/7] driver, misc: add Intel Stratix10 service layer driver richard.gong at linux.intel.com
2018-03-15 16:48   ` Greg KH
2018-03-02  0:19 ` [PATCHv2 4/7] dt-bindings: fpga: add Stratix10 SoC FPGA manager binding richard.gong at linux.intel.com
2018-03-07 19:47   ` Rob Herring [this message]
2018-03-07 22:20     ` Alan Tull
2018-03-08  1:24       ` Rob Herring
2018-03-08 15:32         ` Alan Tull
2018-03-08 22:27           ` Rob Herring
2018-03-02  0:19 ` [PATCHv2 5/7] arm64: dts: stratix10: add fpga manager and region richard.gong at linux.intel.com
2018-03-02  0:19 ` [PATCHv2 6/7] fpga: add intel stratix10 soc fpga manager driver richard.gong at linux.intel.com
2018-03-02  0:19 ` [PATCHv2 7/7] defconfig: enable fpga and service layer richard.gong at linux.intel.com

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=20180307194745.657ewa6rtcta6eqm@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox