From: Jamie Iles <jamie@jamieiles.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
linux-arm-kernel@lists.infradead.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>
Subject: Re: [PATCH 1/3] ATMEL: fix nand ecc support
Date: Wed, 11 Jan 2012 00:49:28 +0000 [thread overview]
Message-ID: <20120111004928.GE3226@page> (raw)
In-Reply-To: <1326232616.2335.11.camel@koala>
On Tue, Jan 10, 2012 at 11:56:54PM +0200, Artem Bityutskiy wrote:
> On Sat, 2012-01-07 at 11:49 +0100, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
> > +#ifndef __ATMEL_NAND_H__
> > +#define __ATMEL_NAND_H__
> > +
> > +#include <linux/mtd/nand.h>
> > +
> > + /* NAND / SmartMedia */
> > +struct atmel_nand_data {
> > + int enable_pin; /* chip enable */
> > + int det_pin; /* card detect */
> > + int rdy_pin; /* ready/busy */
> > + u8 rdy_pin_active_low; /* rdy_pin value is inverted */
> > + u8 ale; /* address line number connected to ALE */
> > + u8 cle; /* address line number connected to CLE */
> > + u8 bus_width_16; /* buswidth is 16 bit */
> > + u8 ecc_mode; /* ecc mode */
> > + struct mtd_partition *parts;
> > + unsigned int num_parts;
> > +};
> > +
> > +#endif /* __ATMEL_NAND_H__ */
>
> The "include/linux" directory, I think, should generally contain only
> those headers which define some "userspace-kernel" or "kernel subsystem"
> API. This file defines Atmel NAND driver's, so it should not be placed
> there.
>
> I am not sure "include/linux" is the best place for this header - is it?
If this is platform data, which it looks like to me then
include/linux/platform_data would be a great home for it.
Jamie
WARNING: multiple messages have this Message-ID (diff)
From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ATMEL: fix nand ecc support
Date: Wed, 11 Jan 2012 00:49:28 +0000 [thread overview]
Message-ID: <20120111004928.GE3226@page> (raw)
In-Reply-To: <1326232616.2335.11.camel@koala>
On Tue, Jan 10, 2012 at 11:56:54PM +0200, Artem Bityutskiy wrote:
> On Sat, 2012-01-07 at 11:49 +0100, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
> > +#ifndef __ATMEL_NAND_H__
> > +#define __ATMEL_NAND_H__
> > +
> > +#include <linux/mtd/nand.h>
> > +
> > + /* NAND / SmartMedia */
> > +struct atmel_nand_data {
> > + int enable_pin; /* chip enable */
> > + int det_pin; /* card detect */
> > + int rdy_pin; /* ready/busy */
> > + u8 rdy_pin_active_low; /* rdy_pin value is inverted */
> > + u8 ale; /* address line number connected to ALE */
> > + u8 cle; /* address line number connected to CLE */
> > + u8 bus_width_16; /* buswidth is 16 bit */
> > + u8 ecc_mode; /* ecc mode */
> > + struct mtd_partition *parts;
> > + unsigned int num_parts;
> > +};
> > +
> > +#endif /* __ATMEL_NAND_H__ */
>
> The "include/linux" directory, I think, should generally contain only
> those headers which define some "userspace-kernel" or "kernel subsystem"
> API. This file defines Atmel NAND driver's, so it should not be placed
> there.
>
> I am not sure "include/linux" is the best place for this header - is it?
If this is platform data, which it looks like to me then
include/linux/platform_data would be a great home for it.
Jamie
next prev parent reply other threads:[~2012-01-11 0:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 10:49 [PATCH 1/3] ATMEL: fix nand ecc support Jean-Christophe PLAGNIOL-VILLARD
2012-01-07 10:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-01-07 10:49 ` [PATCH 2/3] mtd/atmel_nand: add on_flash_bbt to enable the use of On Flash BBT Jean-Christophe PLAGNIOL-VILLARD
2012-01-07 10:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-01-07 10:49 ` [PATCH 3/3] ARM: at91: enable on flash bbt for Atmel Reference and DT boards Jean-Christophe PLAGNIOL-VILLARD
2012-01-10 21:56 ` [PATCH 1/3] ATMEL: fix nand ecc support Artem Bityutskiy
2012-01-10 21:56 ` Artem Bityutskiy
2012-01-11 0:49 ` Jamie Iles [this message]
2012-01-11 0:49 ` Jamie Iles
2012-01-11 11:54 ` Hans-Christian Egtvedt
2012-01-11 11:54 ` Hans-Christian Egtvedt
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=20120111004928.GE3226@page \
--to=jamie@jamieiles.com \
--cc=dedekind1@gmail.com \
--cc=egtvedt@samfundet.no \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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.