linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Neuendorffer <stephen.neuendorffer@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	"Ira W. Snyder" <iws@ovro.caltech.edu>
Subject: Re: [PATCH 3/5] fpga: add basic CARMA board support
Date: Sun, 28 Nov 2010 19:35:43 -0800	[thread overview]
Message-ID: <AANLkTimTpJSsP=LM4MA_+uqtDj0-7a3b+xAb-r8ktuTF@mail.gmail.com> (raw)
In-Reply-To: <1290991094.32570.213.camel@pasglop>

[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]

On Sun, Nov 28, 2010 at 4:38 PM, Benjamin Herrenschmidt <
benh@kernel.crashing.org> wrote:

> On Wed, 2010-09-08 at 09:41 -0700, Ira W. Snyder wrote:
> > This adds basic support for the system controller FPGA on the OVRO CARMA
> > board. This patch only adds infrastructure that will be used by later
> > drivers.
>
> Oh and another comment ...
>
> I'm not sure about drivers/fpga ... in the end, one would expect such a
> directory to contain stuff to manipulate FPGAs in the sense of
> downloading bitfiles, instanciating devices (device-tree manipulation ?)
> etc...
>
> From what I see in your code, the fact that these are FPGAs is almost
> irrelevant, you are providing support for "carma" devices, and such are
> no different than some other platform device, they just happen to be
> implemented as FPGAs. Or am I missing something ?
>
> Cheers,
> Ben.
>
>
Generally, I agree with this: There doesn't seem to be anything generic
about
the FPGA support you are adding, it seems very specific to the CARMA
hardware.

I'm generally not opposed to drivers/fpga: I think that colocating drivers
for things
that are basically FPGA compute platforms isn't necessarily a bad idea, but
I think it would be better if those devices were colocated because they
shared
some FPGA-oriented infrastructure, which this doesn't seem to do.
Currently,
generic infrastructure has been going into drivers/char, and drivers
themselves have
been going wherever they seem best.  Really what you have is 2 character
devices: one
for configuration, and one for access.

Steve

[-- Attachment #2: Type: text/html, Size: 2129 bytes --]

  reply	other threads:[~2010-11-29  3:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 16:41 [PATCH RFCv2 0/5] CARMA Board Support Ira W. Snyder
2010-09-08 16:41 ` [PATCH 1/5] fsldma: fix missing header include Ira W. Snyder
2010-09-08 16:41 ` [PATCH 2/5] fsldma: move DMA_SLAVE support functions to the driver Ira W. Snyder
2010-09-08 16:41 ` [PATCH 3/5] fpga: add basic CARMA board support Ira W. Snyder
2010-11-29  0:36   ` Benjamin Herrenschmidt
2010-11-29  0:38   ` Benjamin Herrenschmidt
2010-11-29  3:35     ` Stephen Neuendorffer [this message]
2010-11-29 16:32     ` Ira W. Snyder
2010-09-08 16:41 ` [PATCH 4/5] fpga: add CARMA DATA-FPGA Access Driver Ira W. Snyder
2010-09-08 16:41 ` [PATCH 5/5] fpga: add CARMA DATA-FPGA Programmer support Ira W. Snyder
2010-09-17 18:41 ` [PATCH RFCv2 0/5] CARMA Board Support Ira W. Snyder

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='AANLkTimTpJSsP=LM4MA_+uqtDj0-7a3b+xAb-r8ktuTF@mail.gmail.com' \
    --to=stephen.neuendorffer@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=iws@ovro.caltech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).