NAND: Add flags to the probe calls to control scan behaviour
Ben Dooks
ben at simtec.co.uk
Tue Oct 20 09:11:52 EDT 2009
Artem Bityutskiy wrote:
> On Mon, 2009-10-19 at 11:36 +0100, Ben Dooks wrote:
>> I'd rather it be silent if it cannot find a device, as a number of our boards
>> have slots where NAND devices may be fitted by the customer and as such all
>> possibilities are registered with the NAND driver.
>>
>>> Could you please elaborate why more why is this needed a bit more? What
>>> is the driver?
>> Because customers get scared when errors with '!!!' turn up.
>
>>> Why not to just remove that print at all?
>> Possible, but what about the case where there is a legitimate problem with
>> the device that is supposed to be there.
>
> I would go for this instead. I think the drivers can print an error
> message themselves.
I was trying to avoid touching the 40+ drivers which use this
code. This would also be a bit of a code bloat as we would have
some interesting checks for the precise error code (was the failure
no-chip, no memory, some other problem?)
> Or can this be done using the chip->options ?
I will look into this.
--
Ben Dooks, Software Engineer, Simtec Electronics
http://www.simtec.co.uk/
More information about the linux-mtd
mailing list