Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 23 3月, 2010 2 次提交
  3. 19 3月, 2010 2 次提交
  5. 16 3月, 2010 1 次提交
  7. 15 3月, 2010 1 次提交
  9. 13 3月, 2010 2 次提交
  11. 11 3月, 2010 1 次提交
  13. 03 3月, 2010 19 次提交
  15. 02 3月, 2010 2 次提交
  17. 28 2月, 2010 2 次提交
  19. 27 2月, 2010 1 次提交
    • M
      SERIAL 8250: Fixes for Alchemy UARTs. · b2b13cdf
      由 Manuel Lauss 提交于 
      Limit the amount of address space claimed for Alchemy serial ports to
0x1000.  On the Au1300, ports are only 0x1000 apart, and the registers
only extend to 0x110 at most on all supported alchemy models.

On the Au1300 the autodetect logic no longer works and this makes it
necessary to specify the port type through platform data.  Because of
this the MSR quirk needs to be moved outside the autoconfig() function
which will no longer be called when UPF_FIXED_TYPE is specified.
Signed-off-by: NManuel Lauss <manuel.lauss@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Cc: linux-serial@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-mips@linux-mips.org
Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      b2b13cdf
  21. 24 2月, 2010 2 次提交
  23. 19 2月, 2010 1 次提交
  25. 18 2月, 2010 1 次提交
  27. 17 2月, 2010 3 次提交
    • A
      serial: mpc52xx_uart: re-enable mpc5121 PSC UART support · 6acc6833
      由 Anatolij Gustschin 提交于 
      Currently the support for MPC5121 PSC UART in the mpc52xx_uart
driver is broken (only console pre-initialized by the bootloader
works). Re-enable it now by providing MPC5121 specific ops
for PSCx clock activation, FIFO controller init/uninit and
MPC5121 PSC FIFO shared interrupt handling functions.
Signed-off-by: NJohn Rigby <jcrigby@gmail.com>
Signed-off-by: NAnatolij Gustschin <agust@denx.de>
Acked-by: NGreg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      6acc6833
    • D
      serial: 8250: add serial transmitter fully empty test · bca47613
      由 Dick Hollenbeck 提交于 
      When controlling an industrial radio modem it can be necessary to
manipulate the handshake lines in order to control the radio modem's
transmitter, from userspace.

The transmitter should not be turned off before all characters have been
transmitted.  serial8250_tx_empty() was reporting that all characters were
transmitted before they actually were.

===

Discovered in parallel with more testing and analysis by Kees Schoenmakers
as follows:

I ran into an NetMos 9835 serial pci board which behaves a little
different than the standard.  This type of expansion board is very common.

"Standard" 8250 compatible devices clear the 'UART_LST_TEMT" bit together
with the "UART_LSR_THRE" bit when writing data to the device.

The NetMos device does it slightly different

I believe that the TEMT bit is coupled to the shift register.  The problem
is that after writing data to the device and very quickly after that one
does call serial8250_tx_empty, it returns the wrong information.

My patch makes the test more robust (and solves the problem) and it does
not affect the already correct devices.

Alan:

  We may yet need to quirk this but now we know which chips we have a
  way to do that should we find this breaks some other 8250 clone with
  dodgy THRE.
Signed-off-by: NDick Hollenbeck <dick@softplc.com>
Signed-off-by: NAlan Cox <alan@linux.intel.com>
Cc: Kees Schoenmakers <k.schoenmakers@sigmae.nl>
Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
Cc: stable <stable@kernel.org>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      bca47613
    • A
      imx-serial-excessive-status-clearing-on-break.patch · 94d32f99
      由 Andy Green 提交于 
      cc: Sasha Hauer <kernel@pengutronix.de>

We noticed that we were only able to communicate once with a GSM module
per session, if we powered down the module then the serial driver was
broken until reset, no traffic or /proc/interrupts activity could be
seen any more.

Volker noticed it was provoked by a long "break" seen on the wire when
the RX was not driven during powerdown, we discovered we could kill the
serial driver just by forcing RX low extenally for a little while.

I saw that the processing for BREAK in the driver gets too excited and
clears down all set bits in USR2, including that a character is pending.
This stops all further characters getting processed.

The attached one-liner makes the serial driver immortal against BREAK.
Signed-off-by: NAndy Green <andy.green@txtr.com>
Signed-off-by: NVolker Ernst <volker.ernst@txtr.com>
Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      94d32f99