Hi Scott,
On Tue, 4 Nov 2014 23:45:44 -0600
Scott Wood scottw...@freescale.com wrote:
On Wed, 2014-11-05 at 12:39 +0900, Masahiro Yamada wrote:
[2] There is no good place to insert a callback to an SoC file.
I need to write parameters such as page_size to hardware registers.
(You can see
Hi Scott,
On Mon, 3 Nov 2014 15:40:59 -0600
Scott Wood scottw...@freescale.com wrote:
On Thu, 2014-10-23 at 21:25 +0900, Masahiro Yamada wrote:
Since commit ff94bc40af34 (mtd, ubi, ubifs: resync with Linux-3.14),
chip-scan_bbt() is called at the end of nand_scan_tail().
It means the
On Wed, 2014-11-05 at 12:39 +0900, Masahiro Yamada wrote:
[2] There is no good place to insert a callback to an SoC file.
I need to write parameters such as page_size to hardware registers.
(You can see my code, nand_denali_fixup() in
arch/arm/cpu/armv7/uniphier/board_late_init.c)
The
On Thu, 2014-10-23 at 21:25 +0900, Masahiro Yamada wrote:
Since commit ff94bc40af34 (mtd, ubi, ubifs: resync with Linux-3.14),
chip-scan_bbt() is called at the end of nand_scan_tail().
It means the first read access happens immediately after the generic
NAND initialization process.
It
On Mon, 2014-11-03 at 15:40 -0600, Scott Wood wrote:
On Thu, 2014-10-23 at 21:25 +0900, Masahiro Yamada wrote:
Since commit ff94bc40af34 (mtd, ubi, ubifs: resync with Linux-3.14),
chip-scan_bbt() is called at the end of nand_scan_tail().
It means the first read access happens immediately
Since commit ff94bc40af34 (mtd, ubi, ubifs: resync with Linux-3.14),
chip-scan_bbt() is called at the end of nand_scan_tail().
It means the first read access happens immediately after the generic
NAND initialization process.
It causes a problem to some SoCs of UniPhier platform because some of
6 matches
Mail list logo
