vrtsystems / linux

The revision D TS-7670 uses eMMC on the GPMI pins instead of NAND flash,
and so requires a different device tree layout.

This uses a PWM channel at 50% duty cycle to synchronise an external
device to the baud rate of the serial port.

The PWM channel is specified in the device tree:

	auart2: serial@8006e000 {
		pinctrl-names = "default";
		pinctrl-0 = <&auart2_2pins_a>;
		pwms = <&pwm 2 9600 0>;
		status = "okay";
	};

- Reconfigured for kernel 4.4.1
- Swap out Freescale built-in watchdog for Technologic Systems external
  watchdog.

Rename the dts for the TS-7670/TS-7400v2 to be consistent with that used
in U-Boot provided by Technologic Systems.

…ble WDT, not instantly reset Added support for MAGICCLOSE since thats a common thing Added a do_ts_halt function for TS WDT and assign it in linux pm

… TS-7680

Missed during cherry-pick of patches across to kernel 4.4.1.

It seems someone goofed up with the design of the modem daughter card
and wired up some of the modems (notably reset and RTS) to the SPI
signals going to the Cortex M0 companion chip.

Consequently, I've had to disable this feature and will have to look at
what signals being asserted on the GPIO lines cause the modem to break.

Finally got mmc1 working.  I had tried booting with this change and
still didn't get any sense from the card, but then after powering off
and re-seating the SD card, the card magically started working.

Regulators sound like the right tool for the job but:
- they can't be controlled from userspace
- the serial driver's don't know how to turn them on and off

The RS-232 ports have a transceiver that is switched by GPIO 1/25.
The Modbus port has some pins that output 24V when GPIOs 1/13 and 1/15
are both turned on.  There's also a status pin to indicate a fault on
GPIO 1/14.

We'll just leave the GPIOs unregistered so they can be accessed via
userspace.

spi0 is a bit-banged bus from what I can see, and it is one of two
possible connections to the LPC11U12 MCU that acts as the companion MCU
for the i.MX286.

Things that appear to work:
- LEDs
- Ethernet
- Flash (is at least seen, not tested)
- Serial interfaces (again, at least seen, not tested)
- USB (works fine)

What doesn't work:
- MicroSD card slots.

commit a13f085 upstream.

This fixes the following issues:

- When a buffer size is supplied to reiserfs_listxattr() such that each
  individual name fits, but the concatenation of all names doesn't fit,
  reiserfs_listxattr() overflows the supplied buffer.  This leads to a
  kernel heap overflow (verified using KASAN) followed by an out-of-bounds
  usercopy and is therefore a security bug.

- When a buffer size is supplied to reiserfs_listxattr() such that a
  name doesn't fit, -ERANGE should be returned.  But reiserfs instead just
  truncates the list of names; I have verified that if the only xattr on a
  file has a longer name than the supplied buffer length, listxattr()
  incorrectly returns zero.

With my patch applied, -ERANGE is returned in both cases and the memory
corruption doesn't happen anymore.

Credit for making me clean this code up a bit goes to Al Viro, who pointed
out that the ->actor calling convention is suboptimal and should be
changed.

Link: http://lkml.kernel.org/r/20180802151539.5373-1-jannh@google.com
Fixes: 48b32a3 ("reiserfs: use generic xattr handlers")
Signed-off-by: Jann Horn <jannh@google.com>
Acked-by: Jeff Mahoney <jeffm@suse.com>
Cc: Eric Biggers <ebiggers@google.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>