sh-sci driver doesn't report actual baud rate

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

 



Hello everyone,

I'm testing UART with different custom baud rates on a renesas lager board that uses the sh-sci driver.

After discovering that TIOCSSERIAL is deprecated I found the way of doing it with TCSETS2, which seems to work. My problem comes when trying to confirm the speed that I've tried to set, it seems to set any speed I request, when it's obvious that some of those speeds are not even valid. The issue seems to be with set_termios(), the serial driver API does not allow the serial driver to return an error, it must make a best effort. But then when I ask back for the speed again it returns the speed I had requested, instead of the actual one.

So for example, when I run my code trying to set up a speed of 9587bps, I would expect it to actually set 9600, but when I ask for the speed back I still get 9587.

Is this the normal/expected behaviour?

Thank you,

Violeta Menendez Gonzalez

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




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux