<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/serial, branch v2.6.26</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.26</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.26'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2008-07-12T21:33:41Z</updated>
<entry>
<title>serial8250: sanity check nr_uarts on all paths.</title>
<updated>2008-07-12T21:33:41Z</updated>
<author>
<name>Eric W. Biederman</name>
<email>ebiederm@xmission.com</email>
</author>
<published>2008-07-12T20:47:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=05d81d2222beec7b63ac8c1c8cdb5bb4f82c2bad'/>
<id>urn:sha1:05d81d2222beec7b63ac8c1c8cdb5bb4f82c2bad</id>
<content type='text'>
I had 8250.nr_uarts=16 in the boot line of a test kernel and I had a weird
mysterious crash in sysfs.  After taking an in-depth look I realized that
CONFIG_SERIAL_8250_NR_UARTS was set to 4 and I was walking off the end of
the serial8250_ports array.

Ouch!!!

Don't let this happen to someone else.

Signed-off-by: Eric W. Biederman &lt;ebiederm@xmission.com&gt;
Acked-by: Alan Cox &lt;alan@redhat.com&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>serial: fix serial_match_port() for dynamic major tty-device numbers</title>
<updated>2008-07-04T17:40:04Z</updated>
<author>
<name>Guennadi Liakhovetski</name>
<email>g.liakhovetski@gmx.de</email>
</author>
<published>2008-07-04T16:59:28Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7ca796f492a11f9408e661c8f22cd8c4f486b8e5'/>
<id>urn:sha1:7ca796f492a11f9408e661c8f22cd8c4f486b8e5</id>
<content type='text'>
As reported by Vipul Gandhi, the current serial_match_port() doesn't work
for tty-devices using dynamic major number allocation.  Fix it.

It oopses if you suspend a serial port with _dynamic_ major number.  ATM,
I think, there's only the drivers/serial/jsm/jsm_driver.c driver, that
does it in-tree.

Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;
Tested-by: Vipul Gandhi &lt;vcgandhi1@aol.com&gt;
Cc: Alan Cox &lt;alan@lxorguk.ukuu.org.uk&gt;
Cc: &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Blackfin Serial Driver: Use timer to poll CTS PIN instead of workqueue.</title>
<updated>2008-06-19T09:46:39Z</updated>
<author>
<name>Sonic Zhang</name>
<email>sonic.zhang@analog.com</email>
</author>
<published>2008-06-19T09:46:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f30ac0ce34f32bb998ac87e37b251374de03e603'/>
<id>urn:sha1:f30ac0ce34f32bb998ac87e37b251374de03e603</id>
<content type='text'>
This allows other threads to run when the serial driver polls the CTS
PIN in a loop.

Signed-off-by: Sonic Zhang &lt;sonic.zhang@analog.com&gt;
Signed-off-by: Bryan Wu &lt;cooloney@kernel.org&gt;

</content>
</entry>
<entry>
<title>Blackfin serial driver: fix up tty core set_ldisc API change breakage bug</title>
<updated>2008-06-07T07:36:33Z</updated>
<author>
<name>Graf Yang</name>
<email>graf.yang@analog.com</email>
</author>
<published>2008-06-07T07:36:33Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3b8458a9793a92a6ca3cb24e309f19821bf0d8e5'/>
<id>urn:sha1:3b8458a9793a92a6ca3cb24e309f19821bf0d8e5</id>
<content type='text'>
This is the patch that follows Linus's modification about set_ldisc.
Graf has built and tested it on BF537 using Linus's git Tree.

Signed-off-by: Graf Yang &lt;graf.yang@analog.com&gt;
Signed-off-by: Bryan Wu &lt;cooloney@kernel.org&gt;

</content>
</entry>
<entry>
<title>Blackfin Serial Driver: Clean up BF54x macro in blackfin UART driver.</title>
<updated>2008-06-03T04:19:45Z</updated>
<author>
<name>Sonic Zhang</name>
<email>sonic.zhang@analog.com</email>
</author>
<published>2008-06-03T04:19:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1feaa51d84e9611521ec6e59172f9f90db274588'/>
<id>urn:sha1:1feaa51d84e9611521ec6e59172f9f90db274588</id>
<content type='text'>
Hide difference in head file.

Signed-off-by: Sonic Zhang &lt;sonic.zhang@analog.com&gt;
Signed-off-by: Bryan Wu &lt;cooloney@kernel.org&gt;

</content>
</entry>
<entry>
<title>atmel_serial: filter out FP during baud rate detection</title>
<updated>2008-06-06T18:29:12Z</updated>
<author>
<name>Haavard Skinnemoen</name>
<email>haavard.skinnemoen@atmel.com</email>
</author>
<published>2008-06-06T05:46:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=9c81c5c95c00c35a328e1757ca45a66647105f6c'/>
<id>urn:sha1:9c81c5c95c00c35a328e1757ca45a66647105f6c</id>
<content type='text'>
I made a change to u-boot that used the FP (Fractional Part) field of BRGR
to achieve more accurate baud rate generation.  Unfortunately, the
atmel_serial driver looks at the whole BRGR register when trying to detect
the baud rate that the port is currently running at, so setting FP to a
nonzero value breaks the baud rate detection.

I'll sit on the u-boot patch for a while longer, but this is clearly a
bug in the atmel_serial driver which should be fixed.

Signed-off-by: Haavard Skinnemoen &lt;haavard.skinnemoen@atmel.com&gt;
Acked-by: Andrew Victor &lt;linux@maxim.org.za&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>serial: fix driver_name conflicts</title>
<updated>2008-06-06T18:29:09Z</updated>
<author>
<name>Anton Vorontsov</name>
<email>avorontsov@ru.mvista.com</email>
</author>
<published>2008-06-06T05:45:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4feead71fa68a41db1d4f065c0f91fd67288877d'/>
<id>urn:sha1:4feead71fa68a41db1d4f065c0f91fd67288877d</id>
<content type='text'>
Some drivers are using too generic "serial" name for driver_name, this
might cause issues, like this:

Freescale QUICC Engine UART device driver
proc_dir_entry 'serial' already registered
Call Trace:
[cf82de50] [c0007f7c] show_stack+0x4c/0x1ac (unreliable)
[cf82de90] [c00b03fc] proc_register+0xfc/0x1ac
[cf82dec0] [c00b05c8] create_proc_entry+0x60/0xac
[cf82dee0] [c00b23dc] proc_tty_register_driver+0x60/0x98
[cf82def0] [c016dbd8] tty_register_driver+0x1b4/0x228
[cf82df20] [c0184d70] uart_register_driver+0x144/0x194
[cf82df40] [c030a378] ucc_uart_init+0x2c/0x94
[cf82df50] [c02f21a0] kernel_init+0x98/0x27c
[cf82dff0] [c000fa74] kernel_thread+0x44/0x60

^^ The board is using ucc_uart.c and 8250.c, both registered as
   "serial".

This patch fixes two drivers that are using "serial" for driver_name and
not "ttyS" for dev_name.  Drivers that are using "ttyS" for dev_name, will
conflict anyway, so we don't bother with these.

Signed-off-by: Anton Vorontsov &lt;avorontsov@ru.mvista.com&gt;
Acked-by: Alan Cox &lt;alan@redhat.com&gt;
Acked-By: Timur Tabi &lt;timur@freescale.com&gt;
Acked-by: Maciej W. Rozycki &lt;macro@linux-mips.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Fix uart_set_ldisc() function type</title>
<updated>2008-06-04T17:35:03Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2008-06-04T17:35:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=edeb280e49d38a5330db25463ef45f5466b0058a'/>
<id>urn:sha1:edeb280e49d38a5330db25463ef45f5466b0058a</id>
<content type='text'>
Commit 64e9159f5d2c4edf5fa6425031e556f8fddaf7e6 ("serial_core:
uart_set_ldisc infrastructure") introduced the ability for low-level
serial drivers to be informed when the tty ldisc changes.

However, the actual tty-layer function that does this callback for
serial devices was declared with the wrong type, having a spurious and
unused 'ldisc' argument.

This fixed the resulting compiler warning by just removing it.

Acked-by: Blithering Idiot &lt;alan@redhat.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>serial_core: uart_set_ldisc infrastructure</title>
<updated>2008-06-03T15:20:17Z</updated>
<author>
<name>Alan Cox</name>
<email>alan@lxorguk.ukuu.org.uk</email>
</author>
<published>2008-06-03T14:18:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=64e9159f5d2c4edf5fa6425031e556f8fddaf7e6'/>
<id>urn:sha1:64e9159f5d2c4edf5fa6425031e556f8fddaf7e6</id>
<content type='text'>
The tty layer provides a callback that is used when the line discipline
is changed. Some hardware uses this to configure hardware specific
features such as IrDA mode on serial ports. Unfortunately the serial
layer does not provide this feature or pass it down to drivers.

Blackfin used to hack around this by rewriting the tty ops, but those are
now properly shared and const so the hack fails. Instead provide the
proper operations.

This change plus a follow up from the Blackfin guys is needed to avoid
blackfin losing features in this release.

Signed-off-by: Alan Cox &lt;alan@redhat.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>8250 Serial Driver: revert extra IRQ flag definition patch</title>
<updated>2008-05-31T08:10:04Z</updated>
<author>
<name>Bryan Wu</name>
<email>cooloney@kernel.org</email>
</author>
<published>2008-05-31T08:10:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a4ed1e41a734d77c9a83a88a8736e19b68e6a2a0'/>
<id>urn:sha1:a4ed1e41a734d77c9a83a88a8736e19b68e6a2a0</id>
<content type='text'>
As Russell pointed out, original patch will break some serial configurations
because of the dependency of the &lt;asm/serial.h&gt; header file.

Revert it first and try to find out other solution later

Cc: Javier Herrero &lt;jherrero@hvsistemas.es&gt;
Cc: Alan Cox &lt;alan@lxorguk.ukuu.org.uk&gt;
Cc: Russell King &lt;rmk+lkml@arm.linux.org.uk&gt;
Signed-off-by: Bryan Wu &lt;cooloney@kernel.org&gt;

</content>
</entry>
</feed>
