All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moritz Fischer <mdf@kernel.org>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: atull@kernel.org, mdf@kernel.org, robh+dt@kernel.org,
	mark.rutland@arm.com, michal.simek@xilinx.com, rajanv@xilinx.com,
	jollys@xilinx.com, linux-fpga@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, chinnikishore369@gmail.com
Subject: Re: [PATCH v4 3/3] fpga manager: Adding FPGA Manager support for Xilinx zynqmp
Date: Tue, 2 Apr 2019 06:31:30 -0700	[thread overview]
Message-ID: <20190402133130.GA14646@archbook> (raw)
In-Reply-To: <20190402123123.915-4-nava.manne@xilinx.com>

Hi Nava,

looks mostly good to me. One minor nit below:

On Tue, Apr 02, 2019 at 06:01:23PM +0530, Nava kishore Manne wrote:

[..]
> diff --git a/drivers/fpga/zynqmp-fpga.c b/drivers/fpga/zynqmp-fpga.c
> new file mode 100644
> index 000000000000..f6e35fe95adb
> --- /dev/null
> +++ b/drivers/fpga/zynqmp-fpga.c
> @@ -0,0 +1,159 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +/*
> + * Copyright (C) 2019 Xilinx, Inc.
> + */
> +
> +#include <linux/dma-mapping.h>
> +#include <linux/fpga/fpga-mgr.h>
> +#include <linux/io.h>
> +#include <linux/kernel.h>
> +#include <linux/module.h>
> +#include <linux/of_address.h>
> +#include <linux/string.h>
> +#include <linux/firmware/xlnx-zynqmp.h>
> +
> +/* Constant Definitions */
> +#define IXR_FPGA_DONE_MASK	0X00000008U

You could use the BIT(x) macro here.
> +
> +/**
> + * struct zynqmp_fpga_priv - Private data structure
> + * @dev:	Device data structure
> + * @flags:	flags which is used to identify the bitfile type
> + */
> +struct zynqmp_fpga_priv {
> +	struct device *dev;
> +	u32 flags;
> +};
> +

[..]

Reviewed-by: Moritz Fischer <mdf@kernel.org>

Thanks,

Moritz

WARNING: multiple messages have this Message-ID (diff)
From: Moritz Fischer <mdf@kernel.org>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	atull@kernel.org, linux-fpga@vger.kernel.org,
	michal.simek@xilinx.com, linux-kernel@vger.kernel.org,
	jollys@xilinx.com, rajanv@xilinx.com, robh+dt@kernel.org,
	mdf@kernel.org, linux-arm-kernel@lists.infradead.org,
	chinnikishore369@gmail.com
Subject: Re: [PATCH v4 3/3] fpga manager: Adding FPGA Manager support for Xilinx zynqmp
Date: Tue, 2 Apr 2019 06:31:30 -0700	[thread overview]
Message-ID: <20190402133130.GA14646@archbook> (raw)
In-Reply-To: <20190402123123.915-4-nava.manne@xilinx.com>

Hi Nava,

looks mostly good to me. One minor nit below:

On Tue, Apr 02, 2019 at 06:01:23PM +0530, Nava kishore Manne wrote:

[..]
> diff --git a/drivers/fpga/zynqmp-fpga.c b/drivers/fpga/zynqmp-fpga.c
> new file mode 100644
> index 000000000000..f6e35fe95adb
> --- /dev/null
> +++ b/drivers/fpga/zynqmp-fpga.c
> @@ -0,0 +1,159 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +/*
> + * Copyright (C) 2019 Xilinx, Inc.
> + */
> +
> +#include <linux/dma-mapping.h>
> +#include <linux/fpga/fpga-mgr.h>
> +#include <linux/io.h>
> +#include <linux/kernel.h>
> +#include <linux/module.h>
> +#include <linux/of_address.h>
> +#include <linux/string.h>
> +#include <linux/firmware/xlnx-zynqmp.h>
> +
> +/* Constant Definitions */
> +#define IXR_FPGA_DONE_MASK	0X00000008U

You could use the BIT(x) macro here.
> +
> +/**
> + * struct zynqmp_fpga_priv - Private data structure
> + * @dev:	Device data structure
> + * @flags:	flags which is used to identify the bitfile type
> + */
> +struct zynqmp_fpga_priv {
> +	struct device *dev;
> +	u32 flags;
> +};
> +

[..]

Reviewed-by: Moritz Fischer <mdf@kernel.org>

Thanks,

Moritz

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-04-02 13:31 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 12:31 [PATCH v4 0/3] Add Bitstream configuration support for ZynqMP Nava kishore Manne
2019-04-02 12:31 ` Nava kishore Manne
2019-04-02 12:31 ` Nava kishore Manne
2019-04-02 12:31 ` [PATCH v4 1/3] firmware: xilinx: Add fpga API's Nava kishore Manne
2019-04-02 12:31   ` Nava kishore Manne
2019-04-02 12:31   ` Nava kishore Manne
2019-04-08 17:14   ` Moritz Fischer
2019-04-08 17:14     ` Moritz Fischer
2019-04-09  6:33     ` Michal Simek
2019-04-09  6:33       ` Michal Simek
2019-04-09  6:33       ` Michal Simek
2019-04-09  8:54       ` Nava kishore Manne
2019-04-09  8:54         ` Nava kishore Manne
2019-04-09  8:54         ` Nava kishore Manne
2019-04-09  8:54         ` Nava kishore Manne
2019-04-09 15:54         ` Moritz Fischer
2019-04-09 15:54           ` Moritz Fischer
2019-04-02 12:31 ` [PATCH v4 2/3] dt-bindings: fpga: Add bindings for ZynqMP fpga driver Nava kishore Manne
2019-04-02 12:31   ` Nava kishore Manne
2019-04-02 12:31   ` Nava kishore Manne
2019-04-02 12:31 ` [PATCH v4 3/3] fpga manager: Adding FPGA Manager support for Xilinx zynqmp Nava kishore Manne
2019-04-02 12:31   ` Nava kishore Manne
2019-04-02 12:31   ` Nava kishore Manne
2019-04-02 13:31   ` Moritz Fischer [this message]
2019-04-02 13:31     ` Moritz Fischer
2019-04-02 18:27   ` Alan Tull
2019-04-02 18:27     ` Alan Tull
2019-04-08 12:39     ` Nava kishore Manne
2019-04-08 12:39       ` Nava kishore Manne
2019-04-08 14:17       ` Alan Tull
2019-04-08 14:17         ` Alan Tull
2019-04-08 14:36         ` Michal Simek
2019-04-08 14:36           ` Michal Simek
2019-04-08 14:36           ` Michal Simek
2019-04-08 16:51           ` Moritz Fischer
2019-04-08 16:51             ` Moritz Fischer
2019-04-08 20:27             ` Alan Tull
2019-04-08 20:27               ` Alan Tull
2019-04-09  6:34               ` Michal Simek
2019-04-09  6:34                 ` Michal Simek
2019-04-09  6:34                 ` Michal Simek
2019-04-09  6:50               ` Nava kishore Manne
2019-04-09  6:50                 ` Nava kishore Manne
2019-04-09  6:50                 ` Nava kishore Manne

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=20190402133130.GA14646@archbook \
    --to=mdf@kernel.org \
    --cc=atull@kernel.org \
    --cc=chinnikishore369@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jollys@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=nava.manne@xilinx.com \
    --cc=rajanv@xilinx.com \
    --cc=robh+dt@kernel.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 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.