linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 1/1] PRUSS UIO driver support
Date: Fri, 4 Mar 2011 08:52:04 -0800	[thread overview]
Message-ID: <20110304165204.GA21244@suse.de> (raw)
In-Reply-To: <201103041658.05655.arnd@arndb.de>

On Fri, Mar 04, 2011 at 04:58:05PM +0100, Arnd Bergmann wrote:
> On Friday 04 March 2011, Nori, Sekhar wrote:
> > On Fri, Mar 04, 2011 at 19:50:28, Hans J. Koch wrote:
> > > On Fri, Mar 04, 2011 at 10:12:52AM +0530, Pratheesh Gangadhar wrote:
> > > > diff --git a/include/linux/uio_pruss.h b/include/linux/uio_pruss.h
> > > > new file mode 100644
> > > > index 0000000..8c9b2c9
> > > > --- /dev/null
> > > > +++ b/include/linux/uio_pruss.h
> > > 
> > > That should go to arch/arm/mach-davinci/include/mach/
> > > and not to the top level include/linux/ directory.
> > 
> > It was put in here because this driver
> > will be used across two ARM architectures
> > (DaVinci and OMAP). Although it won't be used
> > outside of ARM at least in near future.
> 
> I think include/linux/ is fine for this

No, please use include/linux/platform_data/ instead, that is where
platform data should be going into, not into the "global" space if
include/linux/

> , and arch/arm/include/asm would
> be ok as well. You might want to have only a single pruss header
> file that defines all the platform data for the child drivers, though.
> 
> Ideally, you would of course not need the header at all. This will
> be possible with the move to a flat device tree, where you can store the
> offset as a property of the device
> 
> Another alternative would be to move it to a resource of the platform
> device.

That might be a nice idea for the future.

thanks,

greg k-h

  reply	other threads:[~2011-03-04 16:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04  4:42 [PATCH v10 0/1] Add PRUSS UIO driver support Pratheesh Gangadhar
2011-03-04  4:42 ` [PATCH v10 1/1] " Pratheesh Gangadhar
2011-03-04  9:11   ` Arnd Bergmann
2011-03-04 14:20   ` Hans J. Koch
2011-03-04 14:41     ` Nori, Sekhar
2011-03-04 15:58       ` Arnd Bergmann
2011-03-04 16:52         ` Greg KH [this message]
2011-03-04 16:05       ` Hans J. Koch
2011-03-04 19:50   ` Hans J. Koch

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=20110304165204.GA21244@suse.de \
    --to=gregkh@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).