From: Jean-Hugues Deschenes <jean-hugues.deschenes-YGVykHU+fedBDgjK7y7TUQ@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
David Brownell
<dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] Memory-mapped Dwsignware SPI driver
Date: Mon, 18 Jan 2010 13:14:49 -0500 [thread overview]
Message-ID: <4B54A519.7030606@octasic.com> (raw)
In-Reply-To: <fa686aa41001180921u3919c3e4u3711097218cbfa7e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Grant Likely wrote:
> On Mon, Jan 18, 2010 at 9:50 AM, Jean-Hugues Deschenes
> <jean-hugues.deschenes-YGVykHU+fedBDgjK7y7TUQ@public.gmane.org> wrote:
>
>> +choice
>> + prompt "Designware bus type"
>> + depends on SPI_DESIGNWARE
>> + default SPI_DW_PCI
>> +
>> config SPI_DW_PCI
>> - tristate "PCI interface driver for DW SPI core"
>> - depends on SPI_DESIGNWARE && PCI
>> + bool "PCI interface driver for DW SPI core"
>> + depends on PCI
>> +
>> +config SPI_DW_MMIO
>> + bool "Memory-mapped io interface driver for DW SPI core"
>> +
>> +endchoice
>>
>
> The MMIO patch looks non-orthogonal to the PCI stuff so I don't
> understand why a choice/endchoice is being used here. Is there any
> reason that both bus attachments cannot be compiled as modules at the
> same time?
>
Aside from the fact that no chip would realistically have both at the
same time, nope. I'll lift the restriction.
>
>> --- /dev/null
>> +++ b/drivers/spi/dw_spi_mmio.c
>> @@ -0,0 +1,164 @@
>> +/*
>> + * dw_spi_mmio.c - Memory-mapped interface driver for DW SPI Core
>> + *
>> + * Copyright (c) 2010, Octasic semiconductor.
>> + *
>> + * Somewhat derived from PCI implementation,
>> + * Copyright (c) 2009, Intel Corporation.
>> + *
>> + * ...and from designware i2c driver
>> + * Copyright (C) 2006 Texas Instruments.
>> + * Copyright (C) 2007 MontaVista Software Inc.
>> + * Copyright (C) 2009 Provigent Ltd.
>> + *
>> + * This program is free software; you can redistribute it and/or modify it
>> + * under the terms and conditions of the GNU General Public License,
>> + * version 2, as published by the Free Software Foundation.
>> + *
>> + * This program is distributed in the hope it will be useful, but WITHOUT
>> + * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
>> + * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
>> + * more details.
>> + *
>> + * You should have received a copy of the GNU General Public License along
>> + * with this program; if not, write to the Free Software Foundation,
>> + * Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
>>
>
> Do you really need these three paragraphs of preamble? IMNSOH, the
> first paragraph stating GPLv2 should be sufficient.
>
I'm always a bit uncomfortable with the legal stuff, but this code Is
not very controversial so I guess I can make the preamble lighter...
Thanks!
jh
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
next prev parent reply other threads:[~2010-01-18 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 16:50 [PATCH] Memory-mapped Dwsignware SPI driver Jean-Hugues Deschenes
[not found] ` <20100118164921.23527.74770.stgit-PR71IgaHmJalNznWqnLNUK6RkeBMCJyt@public.gmane.org>
2010-01-18 17:21 ` Grant Likely
[not found] ` <fa686aa41001180921u3919c3e4u3711097218cbfa7e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-18 18:14 ` Jean-Hugues Deschenes [this message]
[not found] ` <4B54A519.7030606-YGVykHU+fedBDgjK7y7TUQ@public.gmane.org>
2010-01-19 15:21 ` Grant Likely
2010-01-19 3:26 ` Feng Tang
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=4B54A519.7030606@octasic.com \
--to=jean-hugues.deschenes-ygvykhu+fedbdgjk7y7tuq@public.gmane.org \
--cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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;
as well as URLs for NNTP newsgroup(s).