From: Bryan Wu <bryan.wu@analog.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bryan.wu@analog.com, linux-mtd@lists.infradead.org,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Blackfin BF54x NAND Flash Controller driver
Date: Fri, 14 Sep 2007 15:19:41 +0800 [thread overview]
Message-ID: <1189754381.8165.11.camel@roc-desktop> (raw)
In-Reply-To: <20070913013702.d446739a.akpm@linux-foundation.org>
On Thu, 2007-09-13 at 01:37 -0700, Andrew Morton wrote:
> On Mon, 03 Sep 2007 15:25:23 +0800 Bryan Wu <bryan.wu@analog.com>
> wrote:
>
> > This is the driver for latest Blackfin BF54x nand flash controller
> >
> > - use nand_chip and mtd_info common nand driver interface
> > - provide both PIO and dma operation
> > - compiled with ezkit bf548 configuration
> > - use hardware 1-bit ECC
> > - tested with YAFFS2 and can mount YAFFS2 filesystem as rootfs
> >
> > ...
> >
> > +int hardware_ecc = 0;
>
> scripts/checkpatch.pl, please.
>
Things are fixed in the try#3 version of the driver, which will be sent
out soon.
> > +#endif
> > +
> > +unsigned short bfin_nfc_pin_req[] = {P_NAND_CE, P_NAND_RB, 0};
>
> static. Please review whole patch for this.
>
[!snip!]
> > +
> > +/*
> > + * bf54x_nand_probe
> > + *
> > + * called by device layer when it finds a device matching
> > + * one our driver can handled. This code checks to see if
> > + * it can allocate all necessary resources then calls the
> > + * nand layer to look for devices
> > + */
> > +static int bf54x_nand_probe(struct platform_device *pdev)
> > +{
> > + struct bf54x_nand_platform *plat = to_nand_plat(pdev);
> > + struct bf54x_nand_info *info = NULL;
> > + struct nand_chip *chip = NULL;
> > + struct mtd_info *mtd = NULL;
> > + int err = 0;
> > +
> > + dev_dbg(&pdev->dev, "(%p)\n", pdev);
> > +
> > + if (!plat) {
> > + dev_err(&pdev->dev, "no platform specific information\n");
> > + goto exit_error;
>
> and can this?
>
Try to prevent board configuration missing the bf54x_nand_platform
information.
> > + }
> > +
> > + info = kzalloc(sizeof(*info), GFP_KERNEL);
> > + if (info == NULL) {
> > + dev_err(&pdev->dev, "no memory for flash info\n");
> > + err = -ENOMEM;
> > + goto exit_error;
> > + }
Thanks
-Bryan Wu
prev parent reply other threads:[~2007-09-14 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 7:25 [PATCH] Blackfin BF54x NAND Flash Controller driver Bryan Wu
2007-09-03 10:14 ` Clemens Koller
2007-09-03 17:58 ` Mike Frysinger
2007-09-03 16:46 ` David Woodhouse
2007-09-03 17:33 ` Bryan Wu
2007-09-03 17:57 ` Mike Frysinger
2007-09-04 3:21 ` Bryan Wu
2007-09-13 8:37 ` Andrew Morton
2007-09-13 8:45 ` Mike Frysinger
2007-09-13 8:45 ` Bryan Wu
2007-09-13 8:51 ` Mike Frysinger
2007-09-13 8:49 ` Bryan Wu
2007-09-13 8:49 ` Andrew Morton
2007-09-14 7:19 ` Bryan Wu [this message]
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=1189754381.8165.11.camel@roc-desktop \
--to=bryan.wu@analog.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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