Abdul Nasser Sokariah | 23 Aug 16:09 2014

Urgent Assistance from Syria

Good Day From Syria,

My name is Abdul Nasser Sokariah and I am writing you from Syria, I
choose to contact you directly as I need a reliable person to trust
who can help me make claims to my huge deposit with a vault company in
AFRICA, and based on my present situation in Syria, I need you
urgently to take  possession of everything and further
modalities/directives will follow.

Contact me  only on my private Email:nabdul247 <at> gmail.com for
clarifications,I await your response.

Yours truly, Abdul Nasser Sokariah
Contact Email:nabdul247 <at> gmail.com
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

mr.tomcoulibaly | 23 Aug 14:40 2014

Dear friend

Dear friend

I am contacting you on a business deal of $17.5 Million US Dollars, ready for
transfer into your account The depositor of the said fund died with
his entire family during the Iraq war in 2006, unfortunately leaving
nobody for the claim. if we make this claim, we will share it
60%/40%.100% risk free and it will be legally backed up with
government approved If you are interested reply for more details.Reply
to alternative email address. (mr.tomcoulibaly <at> gmail.com) Waiting for
your reply

Best regard, Mr.Tom Coulibaly
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Sudip Mukherjee | 20 Aug 18:51 2014

[resend PATCH] tty: serial: serial_core.c: printk replacement

printk replaced with corresponding pr_err, dev_alert, dev_notice and pr_info.
fixed two broken user-visible strings used by the corresponding printk

Signed-off-by: Sudip Mukherjee <sudip <at> vectorindia.org>

In the first patch i sent Greg suggested to use dev_err instead of pr_err , but as later Jiri pointed out in my
later patches that uport->dev is having a null check so can not be used , tty_dev is also having a put_device
, so back to pr_err. Any other suggestion ?

 drivers/tty/serial/serial_core.c | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
index 29a7be4..0e03c31 100644
--- a/drivers/tty/serial/serial_core.c
+++ b/drivers/tty/serial/serial_core.c
 <at>  <at>  -892,10 +892,11  <at>  <at>  static int uart_set_info(struct tty_struct *tty, struct tty_port *port,
 			if (uport->flags & UPF_SPD_MASK) {
 				char buf[64];
-				printk(KERN_NOTICE
-				       "%s sets custom speed on %s. This "
-				       "is deprecated.\n", current->comm,
-				       tty_name(port->tty, buf));
+				dev_notice(uport->dev,
+				       "%s sets custom speed on %s. This is deprecated.\n",
+				      current->comm,
+				      tty_name(port->tty, buf));
(Continue reading)

Mika Westerberg | 19 Aug 15:34 2014

[PATCH] serial: 8250_dw: Add ACPI ID for Intel Braswell

From: Alan Cox <alan <at> linux.intel.com>

Another new ACPI identifier for the 8250 dw bindings to cover newer Intel
SoCs such as Braswell.

Signed-off-by: Alan Cox <alan <at> linux.intel.com>
Signed-off-by: Mika Westerberg <mika.westerberg <at> linux.intel.com>
 drivers/tty/serial/8250/8250_dw.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/tty/serial/8250/8250_dw.c b/drivers/tty/serial/8250/8250_dw.c
index 4db7987ec225..57d9df84ce5d 100644
--- a/drivers/tty/serial/8250/8250_dw.c
+++ b/drivers/tty/serial/8250/8250_dw.c
 <at>  <at>  -540,6 +540,7  <at>  <at>  static const struct acpi_device_id dw8250_acpi_match[] = {
 	{ "INT3434", 0 },
 	{ "INT3435", 0 },
 	{ "80860F0A", 0 },
+	{ "8086228A", 0 },
 	{ },
 MODULE_DEVICE_TABLE(acpi, dw8250_acpi_match);


To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
(Continue reading)

Cestonaro Thilo | 18 Aug 11:54 2014

is there a struct uart_driver like struct i2c_driver


I need to write a driver which communicates with it's chip via uart.
So I was wondering which the best way is to do this.

For a i2c device there is the i2c subsystem with it's 
"module_i2c_driver(foo_driver);" and so on.
But I couldn't find any equivalent for a uart device.

So what is the desired way to implement such a driver? Is there one or 
do I need to "struct file * f = filp_open("/dev/ttyS4", FLAGS, MODE);" ?

Thanks any hint!


Attachment (smime.p7s): application/pkcs7-signature, 3783 bytes
Barry Song | 18 Aug 11:32 2014

[PATCH] serial: sirf: fix line over 80 characters style issue

From: Qipan Li <Qipan.Li <at> csr.com>

According to key customer's requirement, fix "line over 80

Signed-off-by: Qipan Li <Qipan.Li <at> csr.com>
Signed-off-by: Barry Song <Baohua.Song <at> csr.com>
 drivers/tty/serial/sirfsoc_uart.c | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/drivers/tty/serial/sirfsoc_uart.c b/drivers/tty/serial/sirfsoc_uart.c
index 4102192..89f1e59 100644
--- a/drivers/tty/serial/sirfsoc_uart.c
+++ b/drivers/tty/serial/sirfsoc_uart.c
 <at>  <at>  -525,7 +525,8  <at>  <at>  static void sirfsoc_rx_tmo_process_tl(unsigned long param)

 	spin_lock_irqsave(&port->lock, flags);
 	while (DMA_COMPLETE == dmaengine_tx_status(sirfport->rx_dma_chan,
-		sirfport->rx_dma_items[sirfport->rx_completed].cookie, &tx_state)) {
+		sirfport->rx_dma_items[sirfport->rx_completed].cookie,
+		&tx_state)) {
 <at>  <at>  -707,7 +708,8  <at>  <at>  static void sirfsoc_uart_rx_dma_complete_tl(unsigned long param)
 	struct dma_tx_state tx_state;
 	spin_lock_irqsave(&port->lock, flags);
 	while (DMA_COMPLETE == dmaengine_tx_status(sirfport->rx_dma_chan,
-			sirfport->rx_dma_items[sirfport->rx_completed].cookie, &tx_state)) {
(Continue reading)

Carlo Caione | 17 Aug 12:49 2014

[PATCH 0/7] ARM: meson: add preliminary support for MesonX/Meson6 SoCs

Amlogic AML8726-MX (codename Meson6) is a highly integrated multimedia
application processor SoC for Multimedia Internet Device (MID), tablet
and Set Top Box (STB). It integrates a powerful CPU, a 2D/3D graphics
subsystem and a state-of-the-art video decoding engine together with
all major peripherals. It is manufactured by Amlogic, inc.

This patchset introduces preliminary support for Meson6-based SoCs but
several IPs and drivers are common among all the MesonX SoCs.

Amlogic doesn't release any documentation about their SoCs, so the code
has been reverse-engineered from the messy source code released at:


Carlo Caione (7):
  ARM: meson: debug: add debug UART for earlyprintk support
  ARM: meson: serial: add MesonX SoC on-chip uart driver
  ARM: meson6: clocksource: add Meson6 timer support
  ARM: meson: add basic support for MesonX SoCs
  ARM: meson: dts: add basic Meson/Meson6/Meson6-atv1200 DTSI/DTS
  ARM: meson: update defconfigs
  ARM: meson: update documentation (uart, timer and vendors)

 .../bindings/serial/amlogic,meson-uart.txt         |  17 +
 .../bindings/timer/amlogic,meson6-timer.txt        |  16 +
 .../devicetree/bindings/vendor-prefixes.txt        |   1 +
 arch/arm/Kconfig                                   |   2 +
 arch/arm/Kconfig.debug                             |  14 +-
 arch/arm/Makefile                                  |   1 +
 arch/arm/boot/dts/Makefile                         |   1 +
(Continue reading)

Felipe Balbi | 15 Aug 00:58 2014

Re: DTR gpio handling removed by 985bfd54c826c0ba873ca0adfd5589263e0c6ee2


On Thu, Aug 14, 2014 at 11:04:58PM +0200, Belisko Marek wrote:
> during 3.15 release was removed by commit
> 985bfd54c826c0ba873ca0adfd5589263e0c6ee2 code which was added by
> 9574f36fb801035f6ab0fbb1b53ce2c12c17d100 by Neil Brown. We're using
> DTR gpio in gta04 device. I plan to post DT binding for DTR gpio +
> documentation and find out that Neil's code was removed by Felipe.
> Greg can you please revert mentioned commit? We're using DTR gpio in
> gta04 device. Or is there other way how to proceed? Thanks.

there are *NO* users of that in tree, if you're using it, then please
add a proper DTS for your device and figure out a way of passing DTR
gpio through DT.

Keep in mind, also, that we might be switching back to 8250 driver (see
thread from Sebastian Siewior) so you might want to look into a way of
adding *generic* gpio-based DTR handling.


Oleksij Rempel | 14 Aug 10:50 2014

one char delay

Hello all,

i do some hobby work on porting linux to Alpscale asm9260 SoC and have
fallowing problem with serial driver. May be you can help me.

- each RX char will be send to the console only after next chart is
entered. For example:
Typed: dmesg
Displ:  dmesg
- all chars are immediately send with uart_insert_char() and
tty_flip_buffer_push() to the core. So this delay is not insight of
driver. I assume, i miss some flag or initialization.

The driver was initially based on atmel_serial.c and ported by Alpscale
to 2.4.28.
I reused this code.. which is working with this issue. Here is the driver:



yegorslists | 13 Aug 15:54 2014

[PATCH] Documentation: serial: fix header path

From: Yegor Yefremov <yegorslists <at> googlemail.com>

RS485 related structure will be defined in user space API

Signed-off-by: Yegor Yefremov <yegorslists <at> googlemail.com>
 Documentation/serial/serial-rs485.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/serial/serial-rs485.txt b/Documentation/serial/serial-rs485.txt
index 41c8378..39dac95 100644
--- a/Documentation/serial/serial-rs485.txt
+++ b/Documentation/serial/serial-rs485.txt
 <at>  <at>  -132,5 +132,5  <at>  <at> 


- [1]	include/linux/serial.h
+ [1]	include/uapi/linux/serial.h
  [2]	Documentation/devicetree/bindings/serial/rs485.txt


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

(Continue reading)

Alan Cox | 12 Aug 17:01 2014

[RFC 1/3] tty: Add RS485 helper functions

From: Alan <gnomes <at> lxorguk.ukuu.org.uk>

This follows the pattern of moving repeatedly occuring ioctl helpers into
common code where possible. We want things like user space copies to be done
in one place.

We allow the existing ioctl fall through to continue working. Old drivers
will not be affected and can be cleaned up in later patches.

Signed-off-by: Alan Cox <alan <at> linux.intel.com>
 drivers/tty/tty_ioctl.c    |   46 ++++++++++++++++++++++++++++++++++++++++++++
 include/linux/tty.h        |    1 +
 include/linux/tty_driver.h |   11 +++++++++++
 3 files changed, 58 insertions(+)

diff --git a/drivers/tty/tty_ioctl.c b/drivers/tty/tty_ioctl.c
index 6fd60fe..7f50d6e 100644
--- a/drivers/tty/tty_ioctl.c
+++ b/drivers/tty/tty_ioctl.c
 <at>  <at>  -20,6 +20,7  <at>  <at> 
 #include <linux/bitops.h>
 #include <linux/mutex.h>
 #include <linux/compat.h>
+#include <linux/serial.h>

 #include <asm/io.h>
 #include <asm/uaccess.h>
 <at>  <at>  -968,6 +969,26  <at>  <at>  static int tty_change_softcar(struct tty_struct *tty, int arg)
(Continue reading)