Re: Support either NAND or OneNAND on omap3-gpmc CS0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Ladislav Michl <ladis@xxxxxxxxxxxxxx> [160816 11:51]:
> Hi Roger,
> 
> On Mon, Aug 15, 2016 at 10:22:45AM +0300, Roger Quadros wrote:
> > Hi Ladis,
> > 
> > On 14/08/16 11:43, Ladislav Michl wrote:
> > > Hi there,
> > > 
> > > some IGEPv2 boards comes either with NAND or OneNAND flash memory and I'd
> > > like to support that with single kernel and fdt blob. As U-Boot can
> > > already detect flash type used I thought that having both onenand@0,0
> > > and nand@0,0 nodes in FDT would be easiest method. Bootloader could then
> > > set status="disabled" property on memory not detected.
> > 
> > Yes, that should work.
> 
> That logic should be positive or negative? There are both aproaches
> present in kernel and it is not immediately obvious under what cimcumstaces
> is one better than another. Having both enabled by default means higher
> probability that kernel boots even if bootloader does not support
> FDT manipulation, but I'm unsure wheneven probe code is robust enough
> not to break anything. Thoughts?

We "should" be able to have both enabled in the dts just fine have
it probed and have onenand or nand probe bail out for the one not found.
Not sure what happens with that right now though :)

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux