I was also confused when looking at the current kernel cmdline, we have the following parameters listed there related to console:
console=tty1 console=ttyS0 console=ttyMFD2 earlyprintk=mrst >From looking at the actual console output using the above cmdline param: [ 0.000000] bootconsole [earlymrst0] enabled [ 0.000000] console [tty1] enabled [ 3.621771] console [ttyMFD2] enabled, bootconsole disabled [ 3.679697] mrst_max3110: start main thread [ 3.679736] spi0.1: ttyS0 at I/O 0x0 (irq = 0) is a spi_max3111 [ 6.271427] spi_master spi0: DW SPI: Status keeps busy for 5000us after a read/write! I knew that I am connected to SPI UART (max3110). Bootconsole (aka earlyprintk) should be disabled before enable the normal console, so questions are: According to Feng's response, why I didn't see ttyS0 enabled message? Why we would even have this "keeps busy for 5000us..." messages? Is that correct that bootconsole should be disabled before enabling normal console? If so, Is this console configuration in the cmdline incorrect that causing the problem? I don't think it's a good idea to either simply remove "earlyprintk=mrst" to make the problem goes away, (this earlyprintk=mrst can be still useful to debug hw issue during integration) nor should we downgrade the error message to dev_dbg. /Winson >-----Original Message----- >From: [email protected] [mailto:meego-kernel- >[email protected]] On Behalf Of [email protected] >Sent: Friday, February 18, 2011 1:15 AM >To: Tang, Feng; Jayaraman, Venkat; [email protected] >Subject: Re: [Meego-kernel] Question on Designware SPI Controller Driver > >Hello, > >This problem also confuse me long time ago. >I change module_init(serial_m3110_init) to be >late_initcall(serial_m3110_init) to avoid this problem. > >May I ask that if the root cause is conflict between the MRST >earlyprintk console and the real spi max3110 console, is there possible >also conflict other SPI device? > >Thank you. > >Sincerely, >Major Lee > > > > >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Tang, Feng >> Sent: Friday, February 18, 2011 4:24 PM >> To: Jayaraman, Venkat; [email protected] >> Subject: Re: [Meego-kernel] Question on Designware SPI >> Controller Driver >> >> Hi Venkat, >> >> I've heard several reports about the annoying message. >> >> The reason for it should be the conflict between the MRST >> earlyprintk console (earlyprintk=mrst in cmdline) and the >> real spi max3110 console aka ttyS0, and actually the 2 >> consoles use the same hardware. >> >> I developed that early console mainly for MRST/MDF power >> on use, which is to debug the early kernel boot by hacky >> direct operating the DW SPI0 controller, long before the >> spi driver subsystem get inited which I developed for the >> MRST power on So when the spi subsystem is up, there is >> conflict between them, other spi devices connected to >> SPI0 including max3110 itself will access the SPI0 controller >> by apis from spi core, while the earlyprintk still directly >> access controller, so likely the message will be triggered out. >> >> And in current phase, the earlyprintk should be disabled for >> normal stable kernels, and I suggest to remove the >> "earlyprintk=mrst" from cmdline for Meego kernel. Another way >> is to downgrade the error message to a dev_dbg(). >> >> Thanks, >> Feng >> ________________________________________ >> From: [email protected] >> [mailto:[email protected]] On Behalf Of >> Jayaraman, Venkat >> Sent: Friday, February 18, 2011 3:03 PM >> To: [email protected] >> Subject: [Meego-kernel] Question on Designware SPI Controller Driver >> >> Hi, >> I consistently see the following message >> being printed from the Designware SPI controller driver >> (dw_spi.c) during the booting phase on Medfield platform. >> >> "Status keeps busy for 5000us after a read/write" >> >> Seems like a "write" inside the interrupt >> handler is causing this. Any idea why this happens? >> >> Thanks >> Venkat >> _______________________________________________ >> MeeGo-kernel mailing list >> [email protected] >> http://lists.meego.com/listinfo/meego-kernel >> >_______________________________________________ >MeeGo-kernel mailing list >[email protected] >http://lists.meego.com/listinfo/meego-kernel _______________________________________________ MeeGo-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
