From: LiuShuo <b35362@freescale.com>
To: <dedekind1@gmail.com>
Cc: "Artem.Bityutskiy@nokia.com" <Artem.Bityutskiy@nokia.com>,
Li Yang-R58472 <r58472@freescale.com>,
Wood Scott-B07421 <B07421@freescale.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip
Date: Thu, 24 Nov 2011 18:02:21 +0800 [thread overview]
Message-ID: <4ECE162D.7080408@freescale.com> (raw)
In-Reply-To: <1322122592.24797.299.camel@sauron.fi.intel.com>
=E4=BA=8E 2011=E5=B9=B411=E6=9C=8824=E6=97=A5 16:16, Artem Bityutskiy =E5=
=86=99=E9=81=93:
> On Thu, 2011-11-24 at 07:49 +0000, Li Yang-R58472 wrote:
>>> Subject: Re: [PATCH 3/3] mtd/nand : workaround for Freescale FCM to s=
upport
>>> large-page Nand chip
>>>
>>> On Thu, 2011-11-24 at 08:41 +0800, b35362@freescale.com wrote:
>>>> + /*
>>>> + * Freescale FCM controller has a 2K size limitation=
of buffer
>>>> + * RAM, so elbc_fcm_ctrl->buffer have to be used if =
writesize
>>>> + * of chip is greater than 2048.
>>>> + * We malloc a large enough buffer (maximum page siz=
e is
>>> 16K).
>>>> + */
>>>> + elbc_fcm_ctrl->buffer =3D kmalloc(1024 * 16 + 1024,
>>> GFP_KERNEL);
>>>
>>> Are there NANDs with 16KiB page size?
>> We are not sure, but are there possibility that chip with 16K page wil=
l appear? Or maybe we can add a MACRO for the maximum page size?
> I do not know, but I know that allocating 32KiB of contiguous physical
> RAM may cause unneeded memory pressure and even fail if the memory is
> too fragmented. So I would not go for this unless this is necessary.
What is your suggestion ? 8k is enough ?
> Did you try to look how the NAND base interface could be changed to
> avoid re-allocation altogether, BTW?
This buffer is a controller-wide resource( as Scott said), I only=20
allocate buffer one time in this version.
It should be a large enough buffer for all chips.
-Liu Shuo
next prev parent reply other threads:[~2011-11-24 9:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 0:41 [PATCH 1/3] mtd/nand : use elbc_fcm_ctrl->oob to set FPAR_MS bit of FPAR b35362
2011-11-24 0:41 ` [PATCH 2/3] mtd/nand : set correct length to FBCR for a non-full-page write b35362
2011-11-24 0:41 ` [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip b35362
2011-11-24 7:37 ` Li Yang-R58472
2011-11-28 17:20 ` Scott Wood
2011-11-24 7:41 ` Artem Bityutskiy
2011-11-24 7:49 ` Li Yang-R58472
2011-11-24 8:16 ` Artem Bityutskiy
2011-11-24 10:02 ` LiuShuo [this message]
2011-11-24 11:07 ` Artem Bityutskiy
2011-11-28 21:48 ` Scott Wood
2011-11-28 21:49 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2011-12-04 4:31 [PATCH 1/3] mtd/nand : use elbc_fcm_ctrl->oob to set FPAR_MS bit of FPAR shuo.liu
2011-12-04 4:31 ` [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip shuo.liu
2011-12-05 6:47 ` Artem Bityutskiy
2011-12-05 19:46 ` Scott Wood
2011-12-06 11:49 ` Artem Bityutskiy
2011-12-06 11:49 ` Artem Bityutskiy
2011-12-07 0:09 ` Scott Wood
2011-12-07 3:55 ` LiuShuo
2011-12-07 19:11 ` Scott Wood
2011-12-08 10:44 ` LiuShuo
2011-12-08 18:43 ` Scott Wood
2011-12-12 21:09 ` Artem Bityutskiy
2011-12-12 21:15 ` Scott Wood
2011-12-12 21:19 ` Artem Bityutskiy
2011-12-12 21:30 ` Scott Wood
2011-12-13 2:46 ` LiuShuo
2011-12-14 8:41 ` LiuShuo
2011-12-14 20:15 ` Scott Wood
2011-12-15 4:59 ` Li Yang
2011-12-15 17:32 ` Scott Wood
2011-12-16 2:44 ` LiuShuo
2011-12-16 17:59 ` Scott Wood
2011-12-19 11:05 ` Li Yang
2011-12-19 16:47 ` Scott Wood
2011-12-20 9:08 ` Li Yang
2011-12-20 19:48 ` Scott Wood
2011-12-17 14:35 ` Artem Bityutskiy
2011-12-19 18:38 ` Scott Wood
2011-12-19 18:42 ` Scott Wood
2011-12-14 3:41 ` LiuShuo
2011-12-14 20:53 ` Scott Wood
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=4ECE162D.7080408@freescale.com \
--to=b35362@freescale.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=B07421@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=r58472@freescale.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 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).