This patch implements the USB part of the Diolan USB-I2C/SPI/GPIO
Master Adapter DLN-2. Details about the device can be found here:
https://www.diolan.com/i2c/i2c_interface.html.
Information about the USB protocol can be found in the Programmer's
Reference Manual [1], see section 1.7.
Because
This patch series adds support for Diolan USB-I2C/GPIO Master Adapter
DLN-2. Details about device can be found here:
https://www.diolan.com/i2c/i2c_interface.html.
This patch series has been rebased against the for-mfd-next branch of
the MFD tree.
Changes since v9:
* MFD: use decimal serial
On Wed, 2014-11-05 at 06:56AM +0100, Andreas Färber wrote:
Hi Sören,
Am 03.11.2014 um 20:05 schrieb Soren Brinkmann:
Soren Brinkmann (7):
pinctrl: pinconf-generic: Declare dt_params/conf_items const
pinctrl: pinconf-generic: Infer map type from DT property
pinctrl:
On Tue 2014-11-04 10:52:47, Steven Rostedt wrote:
From: Steven Rostedt (Red Hat) rost...@goodmis.org
The function bstr_printf() from lib/vsprnintf.c is only available if
CONFIG_BINARY_PRINTF is defined. This is due to the only user currently
being the tracing infrastructure, which needs to
Reviewed-by: Pekon Gupta pe...@pek-sem.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/configs/multi_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 18e2cd8..b1a507b 100644
---
On Wed, 2014-11-05 at 04:35AM +0100, Andreas Färber wrote:
Am 03.11.2014 um 20:05 schrieb Soren Brinkmann:
Add documentation for the devicetree binding for the Zynq pincontroller.
Signed-off-by: Soren Brinkmann soren.brinkm...@xilinx.com
---
.../bindings/pinctrl/xlnx,zynq-pinctrl.txt
Andy Lutomirski l...@amacapital.net 11/04/14 8:33 PM
On 11/04/2014 12:49 AM, Jan Beulich wrote:
Observing that per-CPU data (in the SMP case) is reachable by
exploiting 64-bit address wraparound, these two patches
arrange for using the one byte shorter RIP-relative addressing
forms for the
On 11/05/2014 11:39 AM, Johannes Thumshirn wrote:
On Mon, Nov 03, 2014 at 04:26:39PM -0500, Peter Hurley wrote:
On 11/03/2014 04:01 PM, Peter Hurley wrote:
On 11/03/2014 11:05 AM, Johannes Thumshirn wrote:
* Enable the handling of UART core's automatic flow control feature.
When AFE is
On Wed, Nov 5, 2014 at 7:32 AM, Andy Lutomirski l...@amacapital.net wrote:
I have no idea whether it's a security risk, but it's a serious wtf?!? risk.
Yeah. And considering that the only apparently user of this read-only
O_TMPFILE interface doesn't actually need it anyway because it carries
On Wed, Nov 05, 2014 at 05:44:52PM +0100, Andreas Färber wrote:
This enables the snd_soc_snow module to be auto-loaded.
Applied, thanks.
signature.asc
Description: Digital signature
On Wed, 2014-11-05 at 04:24AM +0100, Andreas Färber wrote:
Hi,
Am 03.11.2014 um 20:05 schrieb Soren Brinkmann:
+ PINCTRL_PIN(54, EMIO_SD0_WP),
+ PINCTRL_PIN(55, EMIO_SD0_CD),
+ PINCTRL_PIN(56, EMIO_SD1_WP),
+ PINCTRL_PIN(57, EMIO_SD0_CD),
Should this be EMIO_SD1_CD?
Andy Lutomirski l...@amacapital.net 11/04/14 8:40 PM
On 11/04/2014 01:24 AM, Jan Beulich wrote:
The main obstacle to having done this long ago was the need to
determine whether annotations are needed in the first place: They need
to be avoided when a frame pointer got set up. Since I can't
Commit-ID: 54c3cc2cd894f0d22897ebb283b6eddca4c814c0
Gitweb: http://git.kernel.org/tip/54c3cc2cd894f0d22897ebb283b6eddca4c814c0
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:12:11 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Commit-ID: a4aad01aa04e405dc41b6c8e75bed3a9b63327d7
Gitweb: http://git.kernel.org/tip/a4aad01aa04e405dc41b6c8e75bed3a9b63327d7
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:11:53 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
On Wed, Nov 05, 2014 at 07:05:01PM +0200, Octavian Purdila wrote:
From: Daniel Baluta daniel.bal...@intel.com
This patch adds GPIO and IRQ support for the Diolan DLN-2 GPIO module.
Information about the USB protocol interface can be found in the
Programmer's Reference Manual [1], see
Opening the slave BSD pty first already returns -EIO from the slave
pty_open(), which in turn causes the newly installed tty pair to be
released before returning from tty_open(). However, this can also
cause a parallel master BSD pty open to fail because the pty pair
destruction may already been
Now that re-open is not permitted for a legacy BSD pty master,
using TTY_CLOSING to indicate when a tty can be torn-down is
no longer necessary.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/tty_io.c | 14 ++
On Wed, 2014-11-05 at 06:12AM +0100, Andreas Färber wrote:
Am 03.11.2014 um 20:05 schrieb Soren Brinkmann:
+enum zynq_pinmux_functions {
+ ZYNQ_PMUX_ethernet0,
+ ZYNQ_PMUX_ethernet1,
+ ZYNQ_PMUX_mdio0,
+ ZYNQ_PMUX_mdio1,
+ ZYNQ_PMUX_qspi0,
+ ZYNQ_PMUX_qspi1,
+
Commit-ID: ba28a8505a43074cceab7b5f454cb1a107159b00
Gitweb: http://git.kernel.org/tip/ba28a8505a43074cceab7b5f454cb1a107159b00
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:11:52 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Holding tty_mutex for a tty re-open is no longer necessary since
tty: Clarify re-open behavior of master ptys. Because the
slave tty count is no longer accessed by tty_reopen(), holding
tty_mutex to prevent concurrent final tty_release() of the slave
pty is not required.
As with tty: Re-open
Commit-ID: dd379395f9951e8e152593007d66ede649a31fa5
Gitweb: http://git.kernel.org/tip/dd379395f9951e8e152593007d66ede649a31fa5
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:12:08 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Commit-ID: 5580d26aab193f1744f4bf94912ff12b73ab20c4
Gitweb: http://git.kernel.org/tip/5580d26aab193f1744f4bf94912ff12b73ab20c4
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:12:09 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Commit-ID: 5c9e8e9d5c88e1e83ac47d918fb8662de43a269b
Gitweb: http://git.kernel.org/tip/5c9e8e9d5c88e1e83ac47d918fb8662de43a269b
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:12:07 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Commit-ID: 5e4df93bbb0be6203a0037676a430abf5373a70e
Gitweb: http://git.kernel.org/tip/5e4df93bbb0be6203a0037676a430abf5373a70e
Author: Yinghai Lu ying...@kernel.org
AuthorDate: Mon, 27 Oct 2014 16:11:55 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Commit-ID: b26ea43d0bb1539ce047206a57c7fd8d636e7f22
Gitweb: http://git.kernel.org/tip/b26ea43d0bb1539ce047206a57c7fd8d636e7f22
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:11:58 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
On Tue 04-11-14 20:55:15, Heinrich Schuchardt wrote:
On 04.11.2014 10:28, Jan Kara wrote:
If inotify_add_watch() would allow to mark a complete mount (like
fanotify_mark() called with FAN_MOUNT) events for all files on this
mount could be detected. If furthermore inotify_read() would return
Commit-ID: 07539ef20d052b2fd8da63f13bd1d44c028ae2ef
Gitweb: http://git.kernel.org/tip/07539ef20d052b2fd8da63f13bd1d44c028ae2ef
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:12:02 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
On Wed, Nov 5, 2014 at 9:09 AM, Jan Beulich jbeul...@suse.com wrote:
Andy Lutomirski l...@amacapital.net 11/04/14 8:33 PM
On 11/04/2014 12:49 AM, Jan Beulich wrote:
Observing that per-CPU data (in the SMP case) is reachable by
exploiting 64-bit address wraparound, these two patches
arrange
Commit-ID: 3714c42b36f55f9d82f9ea553102e931da1087ae
Gitweb: http://git.kernel.org/tip/3714c42b36f55f9d82f9ea553102e931da1087ae
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:11:56 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Commit-ID: bb46613f7099f70bc68c1c684cfa22d6863cd8eb
Gitweb: http://git.kernel.org/tip/bb46613f7099f70bc68c1c684cfa22d6863cd8eb
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:12:06 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Commit-ID: 41e72f617ed6645817731711f4fb735130815c5f
Gitweb: http://git.kernel.org/tip/41e72f617ed6645817731711f4fb735130815c5f
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:11:54 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
On Wed, 2014-11-05 at 17:05 +0530, Sanjeev Sharma wrote:
This is a patch to the rtw_cmd.c file that fixes
Error reported by checkpatch.
Please run your patches through checkpatch before
sending them.
WARNING: suspect code indent for conditional statements (24, 24)
#178: FILE:
Commit-ID: 1e83b8afb8c872d9aec37b7bcfbece301f927d26
Gitweb: http://git.kernel.org/tip/1e83b8afb8c872d9aec37b7bcfbece301f927d26
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:12:04 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Commit-ID: 49e5780b2dd303bc86014934b13842c1a4675d01
Gitweb: http://git.kernel.org/tip/49e5780b2dd303bc86014934b13842c1a4675d01
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:11:57 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
The tty-ldisc_sem write lock is sufficient for serializing changes
to tty-ldisc; holding the tty lock is not required.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/tty_ldisc.c | 6 ++
1 file changed, 2 insertions(+), 4
Commit-ID: e1d8f79a27a41493c8f1ad0bde440048e17f9494
Gitweb: http://git.kernel.org/tip/e1d8f79a27a41493c8f1ad0bde440048e17f9494
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:12:10 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
Commit-ID: 2e5a61f54da689aa2de6e4f48f9ddc90b74fcb46
Gitweb: http://git.kernel.org/tip/2e5a61f54da689aa2de6e4f48f9ddc90b74fcb46
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:11:59 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
- Original Message -
From: Sebastian Andrzej Siewior bige...@linutronix.de
To: Alexandre Montplaisir alexmon...@voxpopuli.im
Cc: Jiri Olsa jo...@redhat.com, linux-kernel@vger.kernel.org, Dominique
Toupin dominique.tou...@ericsson.com,
Mathieu Desnoyers mathieu.desnoy...@efficios.com,
Re-opening master ptys is not allowed. Once opened and for the remaining
lifetime of the master pty, its tty count is 1. If its tty count has
dropped to 0, then the master pty was closed and TTY_CLOSING was set,
and destruction may begin imminently.
Besides the normal case of a legacy BSD pty
On Wed, Nov 5, 2014 at 9:13 AM, Jan Beulich jbeul...@suse.com wrote:
Andy Lutomirski l...@amacapital.net 11/04/14 8:40 PM
On 11/04/2014 01:24 AM, Jan Beulich wrote:
The main obstacle to having done this long ago was the need to
determine whether annotations are needed in the first place: They
Although perhaps not obvious, the TTY_CLOSING bit is set when the
tty count has been decremented to 0 (which occurs while holding
tty_lock). The only other case when tty count is 0 during a re-open
is when a legacy BSD pty master has been opened in parallel but
after the pty slave, which is
Now that tty_ldisc_hangup() does not drop the tty lock, it is no
longer possible to observe TTY_HUPPING while holding the tty lock
on another cpu.
Remove TTY_HUPPING bit definition.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
Dropping the tty lock to acquire the tty-ldisc_sem allows several
race conditions (such as hangup while changing the ldisc) which requires
extra states and testing. The ldisc_sem-tty_lock lock order has
not been required since tty buffer ownership was moved to tty_port.
Reviewed-by: Alan Cox
Opening /dev/tty (ie., the controlling tty for the current task)
is always a re-open of the underlying tty. Because holding the
tty_lock is sufficient for safely re-opening a tty, and because
having a tty kref is sufficient for safely acquiring the tty_lock [1],
tty_open_current_tty() does not
On Wed, Nov 05, 2014 at 07:04:59PM +0200, Octavian Purdila wrote:
This patch implements the USB part of the Diolan USB-I2C/SPI/GPIO
Master Adapter DLN-2. Details about the device can be found here:
https://www.diolan.com/i2c/i2c_interface.html.
Information about the USB protocol can be
On Tue, Nov 4, 2014 at 9:40 AM, David Drysdale drysd...@google.com wrote:
On Mon, Nov 3, 2014 at 5:22 PM, Eric W.Biederman ebied...@xmission.com
wrote:
On November 3, 2014 7:42:58 AM PST, Andy Lutomirski l...@amacapital.net
wrote:
On Mon, Nov 3, 2014 at 7:20 AM, Al Viro
Changes in v2:
* New patch 19 ('tty: Preset lock subclass for nested tty locks') makes
passing the tty_lock subclass at lock time unnecessary; regular ttys and
master ptys use subclass 0 and slave ptys use subclass 1. The expected
lock order is first subclass 0 then subclass 1. Lockdep will
On Wed, Nov 5, 2014 at 9:02 AM, Simon McVittie
simon.mcvit...@collabora.co.uk wrote:
On 05/11/14 15:56, Andy Lutomirski wrote:
- I tend to think that pid and tid should be separate. They're
really their own thing, and, as noted in all the perfectly valid
dislike directed at SO_PEERCRED, they
Commit-ID: b09198f7b59101e52bcf238ed3b7bfc64de055ef
Gitweb: http://git.kernel.org/tip/b09198f7b59101e52bcf238ed3b7bfc64de055ef
Author: Jiang Liu jiang@linux.intel.com
AuthorDate: Mon, 27 Oct 2014 16:12:05 +0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Wed, 5 Nov 2014
pcxe_open() has no definition in mainline; remove declaration.
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
include/linux/tty.h | 4
1 file changed, 4 deletions(-)
diff --git a/include/linux/tty.h b/include/linux/tty.h
index f6835ea..97cfb31 100644
--- a/include/linux/tty.h
+++
vt_get_kmsg_redirect() only has meaning to the console driver as
an alias for calling vt_kmsg_redirect(). Move the macro definition
to the only source file which uses it; remove from uapi/linux/vt.h
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/vt/vt.c | 2 ++
The last vestige of ASYNC_SPLIT_TERMIOS was removed by commit
'cris: Remove obsolete ASYNC_SPLIT_TERMIOS behavior'. Mark the flag
as defunct in the uapi header.
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
include/uapi/linux/tty_flags.h | 2 +-
1 file changed, 1 insertion(+), 1
devm_kzalloc() already warns if allocation fails; remove duplicate
message.
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/serial/8250/8250_em.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_em.c
On Wed, Nov 5, 2014 at 9:21 AM, David Drysdale drysd...@google.com wrote:
On Tue, Nov 4, 2014 at 9:40 AM, David Drysdale drysd...@google.com wrote:
On Mon, Nov 3, 2014 at 5:22 PM, Eric W.Biederman ebied...@xmission.com
wrote:
On November 3, 2014 7:42:58 AM PST, Andy Lutomirski
Hi Greg,
These patches are a mixture of dead declaration removals, uapi cleanup,
and other miscellany.
This series depends on the 10-patch 'serial core fixes' series.
Regards,
Peter Hurley (9):
tty: Replace open-coded test with tty_hung_up_p()
tty: Call methods in modern style
tty:
setup_serial_console() is obsolete and has been superseded by
early_serial_setup() which is called at the end of the function.
The IA64 arch does not call this function; only the m68k arch setup
calls this function.
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
serial_console_init() is not defined by the tty core; remove
declaration.
Note that the powerpc arch boot code contains a serial_console_init()
declaration in arch/powerpc/boot/ops.h which is restricted to
the powerpc arch boot.
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
ASYNC_SPLIT_TERMIOS behavior is a remnant of the long-dead /dev/cuaXX
callout device. Split termios handling was removed tree-wide in v2.5.71 by:
commit 99a21edebbfd8c29e39ee7fcc8a1ffa423657290
Author: Alexander Viro v...@www.linux.org.uk
Date: Wed Jun 11 07:41:28 2003 -0700
[PATCH]
tty_hung_up_p() is equivalent to the open-coded test in tty_open().
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/tty_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index 4bd48f7..1262368 100644
---
The use of older function ptr calling style, (*fn)(), makes static
analysis more error-prone; replace with modern fn() style.
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/tty_io.c| 12 ++--
drivers/tty/tty_ioctl.c | 4 ++--
2 files changed, 8 insertions(+), 8
Hi Kan,
On Tue, 4 Nov 2014 17:07:43 +, Kan Liang wrote:
Hi Namhyung,
tchain_edit[.] f1
0.14%3.913444 tchain_edit[.] f2
99.82%1.005478 tchain_edit[.] f3
Hmm.. I think it should be a default
The port-lock does not protect the filp-f_op field; move
the tty_hung_up_p() test outside the port-lock critical section
in tty_port_close_start().
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/tty_port.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff
The line discipline buffer and the tty buffers must be flushed again
after hardware shutdown; otherwise, a brief window exists between the
ldisc flush in tty_port_close_start() and the subsequent
tty_port_shutdown(), during which more data could be received into the
tty buffers. A racing open
Hi Greg,
These 3 patches are stragglers from the old tty closing series.
I'm still working on eliminating ASYNC_CLOSING and the improvements to
opening in O_NONBLOCK mode.
Regards,
Peter Hurley (3):
tty: Move tty hung up check from port-lock critical section
tty: Convert tty-closing to int
The reason why using LBR call stack mode is restricted to user level
only is because of
a bug in the LBR call stack hardware which forces the kernel to drop
LBR_FREEZE_PMI.
It works with PEBS events, just not with non PEBS (the patch currently
does not implement this distinction and I'm not
From: Paul E. McKenney paul...@linux.vnet.ibm.com
This commit abstracts rcu_cleanup_dead_rnp() from rcu_cleanup_dead_cpu()
in preparation for the rework of RCU priority boosting. This new function
will be invoked from rcu_read_unlock_special() in the reworked scheme,
which is why
From: Paul E. McKenney paul...@linux.vnet.ibm.com
This commit prevents random compiler optimizations by applying
ACCESS_ONCE() to lockless accesses.
Signed-off-by: Paul E. McKenney paul...@linux.vnet.ibm.com
---
kernel/rcu/tree_plugin.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
tty-closing is a bitfield member; prevent corruption from non-atomic
update by assigning a unique memory location.
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
include/linux/tty.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/tty.h
Hello!
This series reduces worst-case CPU-hotplug latency for PREEMPT_RCU
by avoiding an O(N) list move, where N is the number of threads that
were preempted recently while in an RCU read-side critical section.
This situation is rare, occurring only when the last CPU corresponding
to a given
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Given that there is now arcu_preempt_has_tasks() function that checks
to see if the -blkd_tasks list is non-empty, this commit makes use of it.
Signed-off-by: Paul E. McKenney paul...@linux.vnet.ibm.com
---
kernel/rcu/tree_plugin.h | 6 +++---
1
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Now that we are not migrating callbacks, there is no need to hold the
-orphan_lock across the the -qsmaskinit bit-clearing process.
This commit therefore releases -orphan_lock immediately after adopting
the orphaned RCU callbacks.
Signed-off-by:
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Despite what the comment says, it is only softirqs that are disabled,
not interrupts. This commit therefore fixes the comment.
Signed-off-by: Paul E. McKenney paul...@linux.vnet.ibm.com
---
kernel/rcu/tree.c | 2 +-
1 file changed, 1
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Because there is no longer any preempted tasks on the root rcu_node, and
because there is no longer ever an rcub kthread for the root rcu_node,
this commit drops the code in force_qs_rnp() that attempts to awaken
the non-existent root rcub
From: Paul E. McKenney paul...@linux.vnet.ibm.com
This commit undertakes a simple variable renaming to make way for
some rework of RCU priority boosting.
Signed-off-by: Paul E. McKenney paul...@linux.vnet.ibm.com
---
kernel/rcu/tree_plugin.h | 6 +++---
1 file changed, 3 insertions(+), 3
From: Paul E. McKenney paul...@linux.vnet.ibm.com
This commit causes rcu_read_unlock_special() to propagate -qsmaskinit
bit clearing up the rcu_node tree once a given rcu_node structure's
blkd_tasks list becomes empty. This is the final commit in preparation
for the rework of RCU priority
From: Paul E. McKenney paul...@linux.vnet.ibm.com
Now that offlining CPUs no longer moves leaf rcu_node structures'
-blkd_tasks lists to the root, there is no way for the root rcu_node
structure's -blkd_task list to be nonempty, unless the root node is also
the sole leaf node. This commit
From: Paul E. McKenney paul...@linux.vnet.ibm.com
When the last CPU associated with a given leaf rcu_node structure
goes offline, something must be done about the tasks queued on that
rcu_node structure. Each of these tasks has been preempted on one of
the leaf rcu_node structure's CPUs while in
On Wed 05-11-14 11:54:28, Tejun Heo wrote:
On Wed, Nov 05, 2014 at 05:39:56PM +0100, Michal Hocko wrote:
On Wed 05-11-14 11:29:29, Tejun Heo wrote:
Hello, Michal.
On Wed, Nov 05, 2014 at 05:01:15PM +0100, Michal Hocko wrote:
I am not sure I am following. With the latest patch OOM
Make sure to only raise DTR on transitions from B0 in set_termios.
Also allow set_termios to be called from open with a termios_old of
NULL. Note that DTR will not be raised prematurely in this case.
Cc: stable sta...@vger.kernel.org
Signed-off-by: Johan Hovold jo...@kernel.org
---
Greg,
I
On Wed, Nov 05, 2014 at 09:40:29AM +0200, Jarkko Sakkinen wrote:
I mean, if we have a patch that does:
struct tpm_chip {
struct device cdev; // the class device
struct device *pdev; // the 'platform' device chip is bound too
struct device *dev = pdev; // Temporary
Holding tty_mutex is no longer required to serialize changes to
the tty_count or to prevent concurrent opens of closing ttys;
tty_lock() is sufficient.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/tty_io.c | 6 --
1 file
The local o_tty variable in tty_release() is now accessed only
when closing the pty master.
Set o_tty to slave pty when closing pty master, otherwise NULL;
use o_tty != NULL as replacement for pty_master.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley
Passing the 'other' tty to tty_release_checks() only makes sense
for a pty pair; make o_tty scope local instead.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/tty_io.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
Eliminate the requirement of specifying the tty lock nesting at
lock time; instead, set the lock subclass for slave ptys at pty
install (normal ttys and master ptys use subclass 0).
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/pty.c | 2 ++
drivers/tty/tty_mutex.c
When releasing the master pty, the slave pty also needs to be locked
to prevent concurrent tty count changes for the slave pty and to
ensure that only one parallel master and slave release observe the
final close, and proceed to destruct the pty pair. Conversely, when
releasing the slave pty,
On Tue, Nov 04, 2014 at 08:04:36AM -0500, Steven Rostedt wrote:
On Wed, 29 Oct 2014 17:56:02 -0400
Steven Rostedt rost...@goodmis.org wrote:
[ REQUEST FOR ACKS ]
Al,
Can you take a look at these, and give me an Acked-by if they are OK
with you?
Looks sane. How do you want to handle
tty_ldisc_flush() first clears the line discipline input buffer,
then clears the tty flip buffers. However, this allows for existing
data in the tty flip buffers to be added after the ldisc input
buffer has been cleared, but before the flip buffers have been cleared.
Add an optional ldisc
Releasing the tty locks while waiting for the tty wait queues to
be empty is no longer necessary nor desirable. Prior to
tty: Don't take tty_mutex for tty count changes, dropping the
tty locks was necessary to reestablish the correct lock order between
tty_mutex and the tty locks. Dropping the
Perform work flush for both ends of a pty pair within tty_flush_works(),
rather than calling twice.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/tty_io.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff
The tty_unhangup() function is not defined.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
include/linux/tty.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/tty.h b/include/linux/tty.h
index 196c352..e33ea1a 100644
---
Holding the tty_lock() is necessary to prevent concurrent changes
to the tty count that may cause it to differ from the open file
list count. The tty_lock() is already held at all call sites.
NB: Note that the check for the pty master tty count is safe because
the slave's tty_lock() is held while
With the revised tty lock order and lockdep annotation, claiming
the pty slave lock is now safe while still holding the pty master lock.
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/pty.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/tty/pty.c
When the slave side closes and its tty count is 0, the pty
pair can be destroyed; the master side must have already
closed for the slave side tty count to be 0. Thus, only the
pty master close must check if the slave side has closed by
checking the slave tty count.
Remove the pre-computed closing
When releasing one end of a pty pair, that end may just have written
to the other, which the input processing worker, flush_to_ldisc(), is
still working on but has not completed the copy to the other end's
read buffer. So input may not appear to be available to a waiting
reader but yet
Passing the 'other' tty to tty_ldisc_release() only makes sense
for a pty pair; make o_tty function local instead.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley pe...@hurleysoftware.com
---
drivers/tty/tty_io.c| 2 +-
drivers/tty/tty_ldisc.c | 15 +++
When hanging up one end of a pty pair, there may be waiting
readers/writers on the other end which may not exit, preventing
tty_ldisc_lock_pair() from acquiring the other side's ldisc lock.
Only acquire this side's ldisc lock; although this will no longer
prevent the other side from writing new
tty_ldisc_lock(), tty_ldisc_unlock(), and tty_ldisc_lock_nested()
are low-level aliases for the underlying lock mechanism. Rename
with double underscore to allow for new, higher level functions
with those names.
Reviewed-by: Alan Cox a...@linux.intel.com
Signed-off-by: Peter Hurley
When changing the ldisc on one end of a pty pair, there may be
waiting readers/writers on the other end which may not exit from
the ldisc i/o loop, preventing tty_ldisc_lock_pair_timeout() from
acquiring the other side's ldisc lock.
Only acquire this side's ldisc lock; although this will no
On Wed, 2014-11-05 at 21:11 +1100, Michael Ellerman wrote:
From: Julia Lawall julia.law...@lip6.fr
Set the return variable to an error code as done elsewhere in the function.
Signed-off-by: Julia Lawall julia.law...@lip6.fr
Signed-off-by: Michael Ellerman m...@ellerman.id.au
---
Hi,
On Tue, Nov 04, 2014 at 11:47:06AM +0530, Kishon Vijay Abraham I wrote:
From: Oussama Ghorbel ghor...@pivasoftware.com
The USB OTG port does not work since v3.16 on omap platform.
This is a regression introduced by the commit
eb82a3d846fa (phy: omap-usb2: Balance pm_runtime_enable() on
501 - 600 of 2042 matches
Mail list logo
