All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Vinod Koul <vinod.koul@intel.com>,
	Vishal Sagar <vishal.sagar@xilinx.com>
Cc: dmaengine@vger.kernel.org, dineshk@xilinx.com,
	michal.simek@xilinx.com, jmouroux@xilinx.com, radheys@xilinx.com,
	hyunk@xilinx.com, mpenner@xilinx.com,
	Vishal Sagar <vsagar@xilinx.com>,
	John Nichols <jnichol@xilinx.com>,
	Hyun Kwon <hyun.kwon@xilinx.com>
Subject: [2/2] dma: xilinx: Add driver for Video Framebuffer IP
Date: Wed, 20 Dec 2017 19:27:16 +0100	[thread overview]
Message-ID: <1fcdeaec-a471-79a1-4e75-f8e55ad9918a@xilinx.com> (raw)

Hi Vinod,

On 20.12.2017 18:05, Vinod Koul wrote:
> On Wed, Dec 20, 2017 at 02:00:18PM +0530, Vishal Sagar wrote:
>> The Video Framebuffer IP is available in two forms: read or write.
>> This driver supports either form of the IP.
>> Each IP is a single channel DMA and is video format aware.
>> It can read/write video data arranged from/to memory as packed or
>> semi-planar way based on the selected video format.
>> To get list of supported video formats, clients can call certain
>> APIs exposed by the driver. This driver introduces support for
>> these IPs and integrates with the DMA Engine Framework.
> 
> The subsytem name is dmaengine!
> 
>> Signed-off-by: Radhey Shyam Pandey <radheys@xilinx.com>
>> Signed-off-by: John Nichols <jnichol@xilinx.com>
>> Signed-off-by: Jeffrey Mouroux <jmouroux@xilinx.com>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>> Signed-off-by: Hyun Kwon <hyun.kwon@xilinx.com>
>> Signed-off-by: Vishal Sagar <vsagar@xilinx.com>
>> ---
>>  drivers/dma/Kconfig                |   14 +-
>>  drivers/dma/xilinx/Makefile        |    1 +
>>  drivers/dma/xilinx/xilinx_frmbuf.c | 1155 ++++++++++++++++++++++++++++++++++++
> 
> Thats a very large file for review, do consider splitting stuff
> 
>> @@ -342,7 +342,7 @@ config MOXART_DMA
>>  	select DMA_VIRTUAL_CHANNELS
>>  	help
>>  	  Enable support for the MOXA ART SoC DMA controller.
>> -
>> +
> 
> why this noise, this patch has some many sign-off's but didnt anyone see this
> noise?
> 
>> +// SPDX-License-Identifier: GPL-2.0
> 
> Copyright needs to follow this in C99 style
> 
>> +/*
>> + * DMAEngine driver for Xilinx Framebuffer IP
>> + *
>> + * Copyright (C) 2016 - 2017 Xilinx, Inc. All rights reserved.
>> + *
>> + * Authors: Radhey Shyam Pandey <radheys@xilinx.com>
>> + *          John Nichols <jnichol@xilinx.com>
>> + *          Jeffrey Mouroux <jmouroux@xilinx.com>
>> + *
>> + * Based on the Freescale DMA driver.
>> + *
>> + * Description:
>> + * The AXI Framebuffer core is a soft Xilinx IP core that
>> + * provides high-bandwidth direct memory access between memory
>> + * and AXI4-Stream.
>> + *
>> + * This program is free software: you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public License as published by
>> + * the Free Software Foundation, either version 2 of the License, or
>> + * (at your option) any later version.
> 
> why do you need this license text? With SPDX tag this is implied..

We are in touch with Xilinx Legal to clear this if SPDX is enough.
We have been discussing this recently here.
https://lkml.org/lkml/2017/12/18/112

I will let you know when we have this discussion done. Right now I have
recommended to add SPDX header and also license text fragment which was
present in driver version added to Xilinx git tree.

Thanks,
Michal
---
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-12-20 18:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 18:27 Michal Simek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-12 13:36 [2/2] dma: xilinx: Add driver for Video Framebuffer IP Lars-Peter Clausen
2018-01-11  6:15 Vinod Koul
2018-01-10 11:53 Vishal Sagar
2017-12-22  9:55 Vinod Koul
2017-12-22  8:20 Vishal Sagar
2017-12-21  6:55 Philippe Ombredanne
2017-12-21  2:33 Vinod Koul
2017-12-20 17:05 Vinod Koul
2017-12-20  8:30 Vishal Sagar

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=1fcdeaec-a471-79a1-4e75-f8e55ad9918a@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=dineshk@xilinx.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=hyun.kwon@xilinx.com \
    --cc=hyunk@xilinx.com \
    --cc=jmouroux@xilinx.com \
    --cc=jnichol@xilinx.com \
    --cc=mpenner@xilinx.com \
    --cc=radheys@xilinx.com \
    --cc=vinod.koul@intel.com \
    --cc=vishal.sagar@xilinx.com \
    --cc=vsagar@xilinx.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.