* Girish <girishsg@xxxxxx> [080128 05:22]: > > > >-----Original Message----- > >From: Ville Tervo [mailto:ville.tervo@xxxxxxxxx] > >Sent: Wednesday, December 19, 2007 5:43 PM > >To: ext Girish > >Cc: linux-omap@xxxxxxxxxxxxxxx; linux-omap-open-source@xxxxxxxxxxxxxx > >Subject: Re: [RFC] [PATCH 0/2] High Speed uart support on 3430 > > > >ext Girish wrote: > >> > >> > >>> -----Original Message----- > >>> From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] > >>> Sent: Monday, December 17, 2007 11:07 PM > >> > >>>> - Data transfer Configuration(DMA mode) > >>>> - ISR registration > >>>> - UART Speed change > >>> Well all that sounds good, but please move the driver to > >>> drivers/serial to start with. > >> > >> This UART driver is more like an independent library which doesn't > >> interface with serial framework so this might not fit in > >driver/serial. Any comments? > > > >Is it possible to make a driver for omap uarts based on your library? > >Current generic drivers seems to trigger some hw(?) bugs, so > >at least in > > we had to use custom serial driver. Also working power > >management was added so that clock are not used when the uart > >is not actually used. > > Sorry for late reply. Well, when you say driver for omap uarts are you mentioning a serial driver interfacing with *tty* framework? > > > Yes, we can have a separate serial driver for all our omap uarts, this way it would be more cleaner than the current generic serial > driver. > Making driver based on this library won't be straight forward though, needless to say we can reuse some of the code. But yes, if you > can eloborate more on your idea/requirement then we can think of having a separate serial driver for omap uarts. > > The main idea behind having this uart library was: > 1. To have a common uart code base across IrDA/bluetooth. > 2. To have DMA base uart communication (non tty based transfer). > > Also, let me know your opinion on this. Because of the PM and DMA support, we should continue from Juha Yrjölä's earlier omap specific serial driver [1]. The patch should be first refreshed by diffing between Nokia N800 kernel[2][3] and linux-omap tree. The driver name should be changed from ttyS to ttyO or something similar to avoid conflicts with plugin 8250 based devices. Regards, Tony [1] http://marc.info/?l=linux-omap&m=119634464931867&w=2 [2] http://repository.maemo.org/pool/os2008/free/source/k/kernel-source-rx-34/kernel-source-rx-34_2.6.21.0.orig.tar.gz [3] http://repository.maemo.org/pool/os2008/free/source/k/kernel-source-rx-34/kernel-source-rx-34_2.6.21.0-osso71.diff.gz - 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
