On Wed, 10 Sep 2014, Russell King - ARM Linux wrote:
> On Fri, Sep 05, 2014 at 03:27:51PM -0400, Nicolas Pitre wrote:
> > On Tue, 2 Sep 2014, Christoph Lameter wrote:
> >
> > > On Tue, 2 Sep 2014, Christoph Lameter wrote:
> > >
> > > > Oww.. This is double indirection deal there. A percpu offset
On Wed, Sep 10, 2014 at 12:05 PM, Rasmus Villemoes
wrote:
> The options -mno-mmx and -mno-sse are unconditionally added to
> KBUILD_CFLAGS in both branches of an ifeq and through a $(cc-option)
> further down. We can safely remove the first instances.
>
> In fact, since the -mno-mmx and -mno-sse o
On Tue, Sep 09, 2014 at 04:37:33PM -0700, David Miller wrote:
> From: Stephen Rothwell
> Date: Wed, 10 Sep 2014 09:28:19 +1000
>
> > Hi Dave,
> ...
> > This fix patch is now needed in the net-next tree ...
>
> Applied thanks Stephen.
Doh! Sorry I missed that one...
--
John W. Linville
On Wed, Sep 10, 2014 at 10:52 AM, Doug Anderson wrote:
> Mark,
>
> On Wed, Sep 10, 2014 at 10:27 AM, Mark Rutland wrote:
>> Hi Sonny,
>>
>> On Wed, Aug 27, 2014 at 10:03:39PM +0100, Sonny Rao wrote:
>>> This is a bug fix for using physical arch timers when
>>> the arch_timer_use_virtual boolean i
On Wed, Sep 10, 2014 at 11:28:16AM -0600, Stephen Warren wrote:
> On 09/10/2014 08:33 AM, nick.d...@itdev.co.uk wrote:
> >From: Stephen Warren
> >
> >[reworked after comments by Dmitry Torokhov. Move free of input device into
> >separate function. Only call in paths that require it.]
> >Signed-off
Hi Dmitry,
On Wed, Sep 10, 2014 at 04:46:46PM +0300, Dmitry Lavnikevich wrote:
> This is driver for i.MX6 boards with tlv320aic3x audio codecs.
>
> Signed-off-by: Dmitry Lavnikevich
> ---
> .../bindings/sound/fsl,imx-audio-tlv320aic3x.txt | 27
> sound/soc/fsl/Kconfig
On Wed, Sep 10, 2014 at 4:35 AM, Daniel Borkmann wrote:
>
> Since we already have an extensive BPF test suite, that is, lib/test_bpf.c,
> which currently also does sanity checks for the classic BPF verifier, is
> there a reason these verifier test cases cannot be extended/integrated there
> as wel
On Wed, Sep 10, 2014 at 10:18:14AM +0800, John Sung wrote:
> Hi Dmitry,
>
> I tried the patch, and it works with my 32-bit inputattach.
Excellent, I queued it up for mainline.
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Will,
On Wed, Sep 10, 2014 at 10:34 AM, Will Deacon wrote:
> Setting aside the security model, booting in secure mode can also have a
> significant impact on the programming model of system IP, not just the CPU.
> For example, the SMMU register file suddenly looks different and the way in
> which
Hi Russell,
On 10/09/14 18:41, Russell King - ARM Linux wrote:
> On Fri, Sep 05, 2014 at 03:27:51PM -0400, Nicolas Pitre wrote:
>> On Tue, 2 Sep 2014, Christoph Lameter wrote:
>>
>>> On Tue, 2 Sep 2014, Christoph Lameter wrote:
>>>
Oww.. This is double indirection deal there. A percpu offset
On 09/09/2014 06:18 PM, Robert Elliott wrote:
> From: Robert Elliott
>
> One change introduced by blk-mq is that it does all
> the completion work in hard irq context rather than
> soft irq context.
>
> On a 6 core system, if all interrupts are routed to
> one CPU, then you can easily run into t
On Wed, Sep 10, 2014 at 7:27 AM, Markus Pargmann wrote:
> Hi,
>
> On Wed, Sep 10, 2014 at 04:46:46PM +0300, Dmitry Lavnikevich wrote:
>> This is driver for i.MX6 boards with tlv320aic3x audio codecs.
>>
>> Signed-off-by: Dmitry Lavnikevich
>> ---
>> .../bindings/sound/fsl,imx-audio-tlv320aic3x.t
On 09/05/2014 01:53 PM, Tejun Heo wrote:
On Fri, Sep 05, 2014 at 01:21:00PM -0400, Murali Karicheri wrote:
Keystone K2E EVM uses Marvel 0x9182 controller. This requires support
for the ID in the ahci driver.
Signed-off-by: Murali Karicheri
Applied to libata/for-3.17-fixes w/ stable cc'd.
Tha
On Wed, Sep 10, 2014 at 4:24 AM, Daniel Borkmann wrote:
> On 09/10/2014 07:10 AM, Alexei Starovoitov wrote:
>>
>> move instruction macros (like BPF_MOV64_REG or BPF_ALU32_IMM)
>> from linux/filter.h into uapi/linux/bpf.h
>> so that userspace programs can use them.
>>
>> verifier testsuite (in late
On 09/09/2014 06:18 PM, Robert Elliott wrote:
> From: Robert Elliott
>
> Make blk_mq_alloc_tag_set return an error if set->reserved_tags
> is greater than BLK_MQ_MAX_DEPTH minus the minimum number of
> tags, since:
> * set->queue_depth is truncated to that value
> * set->reserved_tags needs to be
[+ linux acpi]
could be other problems ...that is caused by wrong
use memblock_alloc replace memblock_find
On Wed, Sep 10, 2014 at 8:44 AM, Daniel J Blueman wrote:
> Kernels 3.14 and newer fail ACPI handover [1] on Supermicro H8QGL servers,
> invariant of BIOS version or settings, causing bo
On Tuesday 09 September 2014 12:20:54 Catalin Marinas wrote:
>
> We can assume that if a domain is not specified and there is a single
> top level PCIe node, the domain defaults to 0. Are there any arm32
> platforms that require multiple domains (and do not specify a number in
> the DT)?
In theor
On 10 September 2014 13:31, Dirk Brandewie wrote:
> On 09/10/2014 09:11 AM, Ashwin Chaugule wrote:
>> On 10 September 2014 11:44, Dirk Brandewie
>> With the current split I think you will still be able to maintain
>> Intel specific changes for the future in the backend driver. The PID
>> algorith
On Tue, Sep 9, 2014 at 10:09 PM, Alexei Starovoitov wrote:
> Hi David,
>
> I've managed to reduce this set to 12:
> Patches 1-4 establish BPF syscall shell for maps and programs.
> Patches 5-10 add verifier step by step
> Patch 11 exposes existing instruction macros to user space
> Patch 12 adds t
On Tue, Sep 09, 2014 at 06:54:45PM +0100, Stephen Boyd wrote:
> On 09/09/14 04:39, Will Deacon wrote:
> > It's interesting that arm64 isn't affected by this problem, since we don't
> > update the active_irqs mask for PPIs there and consequently just pass the
> > irq instead of the cpu_pmu. I can't
On Wed, Sep 10, 2014 at 9:51 AM, Toshi Kani wrote:
> This patch changes reserve_memtype() to handle the WT cache mode.
> When PAT is not enabled, it continues to set UC- to *new_type for
> any non-WB request.
>
> When a target range is RAM, reserve_ram_pages_type() fails for WT
> for now. This fu
> Note that since then we have actually fixed the 'cannot fault from NMI
> context' thing, so we should be able to actually take those faults. I
> suspect we can simply remove those WARNs from the vmalloc fault path,
> but it would need double checking to see if there's no other reasons.
I think w
On 09/10/2014 10:25 AM, Boaz Harrosh wrote:
> Yes the block_allocator of the pmem-FS always holds the final REF on this
> page, as long as there is valid data on this block. Even cross boots, the
> mount code re-initializes references. The only internal state that frees
> these blocks is truncate,
On Wed, Sep 10, 2014 at 05:38:13PM +0200, Maciej Matraszek wrote:
> Hi Greg,
> thanks for your reply!
>
> > > +static int __init pm_genpd_debug_init(void)
> > > +{
> > > + struct dentry *d;
> > > +
> > > + pm_genpd_debugfs_dir = debugfs_create_dir("pm_genpd", NULL);
> > > +
> > > + /* No debugfs *
On Wed, Sep 10, 2014 at 9:51 AM, Toshi Kani wrote:
> This patch adds ioremap_wt() for creating WT mapping on x86.
> It follows the same model as ioremap_wc() for multi-architecture
> support. ARCH_HAS_IOREMAP_WT is defined in the x86 version of
> io.h to indicate that ioremap_wt() is implemented
On Wed, Sep 10, 2014 at 02:21:59PM +0100, Bjorn Helgaas wrote:
> On Wed, Sep 10, 2014 at 7:04 AM, Will Deacon wrote:
>
> > It's blindingly obvious that acpi=off is there to disable ACPI at boot.
> > We either support that option or we don't -- none of this `oh, well you
> > can use it in this spe
On Wed, Sep 10, 2014 at 9:51 AM, Toshi Kani wrote:
> +Drivers may map the entire NV-DIMM range with ioremap_cache and then change
> +a specific range to wt with set_memory_wt.
That's mighty specific :)
It's also not all that informative. Are you supposed to set the
memory back before iounmappin
glibc 2.9 introduced the htole<16/32/64> macros, add them to
tools/include to support older versions of glibc.
Reported-by: Andrew Morton
Signed-off-by: Peter Foley
---
Documentation/arm/SH-Mobile/Makefile | 2 +-
Documentation/arm/SH-Mobile/vrl4.c | 1 +
Documentation/mic/mpssd/Makefile
An interface may need to assert a lock invariant and not flood the
system logs; add a lockdep helper macro equivalent to
lockdep_assert_held() which only WARNs once.
cc: Greg Kroah-Hartman
Signed-off-by: Peter Hurley
---
include/linux/lockdep.h | 5 +
1 file changed, 5 insertions(+)
diff -
On Wed, Sep 10, 2014 at 10:52:28AM -0600, Azael Avalos wrote:
> Hi Darren,
>
> 2014-09-09 22:11 GMT-06:00 Darren Hart :
> > On Fri, Sep 05, 2014 at 11:14:06AM -0600, Azael Avalos wrote:
> >
> > Hi Azael,
> >
> > Apologies for the delay. I'm still recovering from a couple weeks of travel
> > and
>
Hi,
On Wed, Sep 10, 2014 at 10:52 AM, Doug Anderson wrote:
> Mark,
>
> On Wed, Sep 10, 2014 at 10:27 AM, Mark Rutland wrote:
>> Hi Sonny,
>>
>> On Wed, Aug 27, 2014 at 10:03:39PM +0100, Sonny Rao wrote:
>>> This is a bug fix for using physical arch timers when
>>> the arch_timer_use_virtual bool
On Wed, Sep 10, 2014 at 08:07:24AM +0200, Johannes Thumshirn wrote:
> On Tue, Sep 09, 2014 at 05:26:35PM -0700, Greg Kroah-Hartman wrote:
> > On Tue, Sep 09, 2014 at 07:56:15AM +0200, Johannes Thumshirn wrote:
> > > On Mon, Sep 08, 2014 at 04:17:33PM -0700, Greg Kroah-Hartman wrote:
> > > > >
> > >
From: Markos Chandras
Date: Wed, 10 Sep 2014 14:23:28 +0100
> On 08/29/2014 04:33 PM, Daniel Borkmann wrote:
>> On 08/29/2014 04:23 PM, Markos Chandras wrote:
>>> MIPS supports BPF JIT since v3.16-rc1
>>>
>>> Cc: Randy Dunlap
>>> Cc: "David S. Miller"
>>> Cc: Daniel Borkmann
>>> Cc: Alexei Sta
On Wed, Sep 10, 2014 at 10:45:33AM -0400, Peter Hurley wrote:
> On 09/10/2014 09:08 AM, Peter Zijlstra wrote:
> > On Wed, Sep 10, 2014 at 07:02:10AM -0400, Peter Hurley wrote:
> >> On 09/04/2014 01:14 AM, Ingo Molnar wrote:
> >>>
> >>> * Peter Zijlstra wrote:
> >>>
> On Wed, Sep 03, 2014 at 1
On Wed, Sep 10, 2014 at 10:28:39AM -0400, Jeff Layton wrote:
> The current scheme of using the i_flock list is really difficult to
> manage. Start conversion to a new scheme to eventually replace it.
>
> We start by adding a new i_flctx to struct inode. For now, it lives in
> parallel with i_flock
In PTE holes that contain VM_SOFTDIRTY VMAs, unmapped addresses before
VM_SOFTDIRTY VMAs are reported as softdirty by /proc/pid/pagemap. This
bug was introduced in 68b5a652485682f67eacdee3deae640fb7845b63. The
aforementioned patch made /proc/pid/pagemap look at VM_SOFTDIRTY in PTE
holes but neglect
On Wed, Sep 10, 2014 at 07:09:59PM +0100, Doug Anderson wrote:
> On Wed, Sep 10, 2014 at 10:34 AM, Will Deacon wrote:
> > Setting aside the security model, booting in secure mode can also have a
> > significant impact on the programming model of system IP, not just the CPU.
> > For example, the SM
On 09/10/14 11:21, Will Deacon wrote:
> On Tue, Sep 09, 2014 at 06:54:45PM +0100, Stephen Boyd wrote:
>
>> Here's the interdiff. Is there a reason arm64 casts data to an unsigned
>> int pointer when what's passed is an int pointer?
> There has to be a cast to something because data is a void *.
> e
On Wed, 10 Sep 2014 14:38:15 -0400
"J. Bruce Fields" wrote:
> On Wed, Sep 10, 2014 at 10:28:39AM -0400, Jeff Layton wrote:
> > The current scheme of using the i_flock list is really difficult to
> > manage. Start conversion to a new scheme to eventually replace it.
> >
> > We start by adding a n
On Wed, Sep 10, 2014 at 11:27:44AM -0700, Andi Kleen wrote:
> > Note that since then we have actually fixed the 'cannot fault from NMI
> > context' thing, so we should be able to actually take those faults. I
> > suspect we can simply remove those WARNs from the vmalloc fault path,
> > but it would
Hi Stefan,
On Wed, Sep 10, 2014 at 2:32 PM, Stefan Wahren wrote:
> Hi Mark,
>
> Am 10.09.2014 17:13, schrieb Mark Brown:
>>
>> On Wed, Sep 10, 2014 at 03:18:53PM +0100, Mark Rutland wrote:
>>>
>>> On Tue, Sep 09, 2014 at 08:17:17PM +0100, Stefan Wahren wrote:
>>
>>
>> Ugh, this looks like it migh
On Wed, Sep 10, 2014 at 09:40:11AM +0800, Ming Lei wrote:
> I am wondering we can do that because lifetime is totally different
> between flush requests and tag_set requests which are initialized
> before request queue is created.
We shouldn't do it in the tag sets, but where we allocate and free
On Tue, 9 Sep 2014, Mel Gorman wrote:
> Since 2.6.24 there has been a paranoid check in move_freepages that looks
> up the zone of two pages. This is a very slow path and the only time I've
> seen this bug trigger recently is when memory initialisation was broken
> during patch development. Despit
On 03/09/14 11:13, Heiko Stübner wrote:
> Am Mittwoch, 3. September 2014, 00:20:58 schrieb Hartmut Knaack:
>> Heiko Stübner schrieb:
>>> Older Rockchip SoCs, at least the rk3066, used a slightly modified saradc
>>> for temperature measurements. This so called tsadc does not contain any
>>> active p
> + pte = pte_mkwrite(pte);
> + }
> #ifdef CONFIG_HUGETLB_PAGE
> if (PageHuge(new)) {
> pte = pte_mkhuge(pte);
I seem to have hit this warning:
[ 4782.617806] WARNING: CPU: 10 PID: 21180 at mm/migrate.c:155
remove_migration_pte+0x3f7/0x420()
[
The tty core does not test tty->hw_stopped; remove from drivers
which don't test it themselves.
cc: Johan Hovold
Signed-off-by: Peter Hurley
---
drivers/usb/serial/digi_acceleport.c | 7 +--
drivers/usb/serial/io_ti.c| 7 +--
drivers/usb/serial/ti_usb_3410_5052.c | 7 +-
Commit 64851636d568ae9f167cd5d1dcdbfe17e6eef73c,
serial: bfin-uart: Remove ASYNC_CTS_FLOW flag for hardware automatic CTS,
open-codes uart_handle_cts_change() when CONFIG_SERIAL_BFIN_HARD_CTSRTS
to skip start and stop tx.
But the CTS interrupt handler _still_ calls uart_handle_cts_change();
only c
Without serialization, the flow control state can become inverted
wrt. the actual hardware state. For example,
CPU 0 | CPU 1
stop_tty() |
lock ctrl_lock |
tty->stopped = 1 |
unlock ctrl_lock |
tty->hw_stopped is not used by the tty core and is thread-unsafe;
hw_stopped is a member of a bitfield whose fields are updated
non-atomically and no lock is suitable for serializing updates.
Replace serial core usage of tty->hw_stopped with uport->hw_stopped.
Use int storage which works around Al
Hi Greg,
Changes since v1:
1. Omits v1 patches 1-12 which you already applied
2. Depends on 'locking: Add WARN_ON_ONCE lock assertion',
which replaces v1 patch 13
3. Works around Alpha EV4/5 non-atomic byte/short storage
4. Works around gcc bug in versions < 4.7.2, where bitfield stores can
The stopped, hw_stopped, flow_stopped and packet bits are smp-unsafe
and interrupt-unsafe. For example,
CPU 0 | CPU 1
|
tty->flow_stopped = 1 | tty->hw_stopped = 0
One of these updates will be corrupted, as the bitwise operation
on the
ISDN4Linux always enables CTS flow control and does not use the
tty_port_cts_enabled() helper function; remove ASYNC_CTS_FLOW
state enable/disable.
cc: Karsten Keil
cc:
Signed-off-by: Peter Hurley
---
drivers/isdn/i4l/isdn_tty.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/i
uart_set_termios() is called with interrupts enabled; no need to
save and restore the interrupt state when taking the uart port lock.
Signed-off-by: Peter Hurley
---
drivers/tty/serial/serial_core.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/tty/serial/s
The serial core provides two helper functions, uart_handle_dcd_change()
and uart_handle_cts_change(), for UART drivers to use at interrupt
time. The serial core expects the UART driver to hold the uart port lock
when calling these helpers to prevent state corruption.
If lockdep enabled, trigger a
The serial core uses the tty port flags, ASYNC_CTS_FLOW and
ASYNC_CD_CHECK, to track whether CTS and DCD changes should be
ignored or handled. However, the tty port flags are not safe for
atomic bit operations and no lock provides serialized updates.
Introduce the struct uart_port status field to
On Wed, 10 Sep 2014, Sasha Levin wrote:
> On 09/09/2014 10:45 PM, Hugh Dickins wrote:
> > Sasha, you say you're getting plenty of these now, but I've only seen
> > the dump for one of them, on Aug26: please post a few more dumps, so
> > that we can look for commonality.
>
> I wasn't saving older l
Rob Clark reports a sleeping while atomic bug when using perf.
BUG: sleeping function called from invalid context at
../kernel/locking/mutex.c:583
in_atomic(): 1, irqs_disabled(): 128, pid: 0, name: swapper/0
[ cut here ]
WARNING: CPU: 2 PID: 4828 at ../kernel/locking/mute
On 09/10/2014 11:26 AM, Andy Lutomirski wrote:
> On Wed, Sep 10, 2014 at 9:51 AM, Toshi Kani wrote:
>> This patch changes reserve_memtype() to handle the WT cache mode.
>> When PAT is not enabled, it continues to set UC- to *new_type for
>> any non-WB request.
>>
>> When a target range is RAM, res
Hi Kever,
Am Mittwoch, 10. September 2014, 18:05:53 schrieb Kever Yang:
> basic rk3288 smp support
>
> Signed-off-by: Heiko Stuebner
> Signed-off-by: Kever Yang
> ---
>
> arch/arm/mach-rockchip/core.h| 1 +
> arch/arm/mach-rockchip/platsmp.c | 60
> +--
On Wed, Sep 10, 2014 at 10:28:46AM -0400, Jeff Layton wrote:
> Signed-off-by: Jeff Layton
> ---
> fs/nfs/delegation.c | 37 +
> fs/nfs/nfs4state.c | 24 +++-
> fs/nfs/pagelist.c | 3 ++-
> fs/nfs/write.c | 39 +++
On Wed, Sep 10, 2014 at 01:28:56PM +0200, Maciej Matraszek wrote:
> +static int pm_genpd_summary_open(struct inode *inode, struct file *file)
> +{
> + return single_open(file, pm_genpd_summary_show, inode->i_private);
On Wed, Sep 10, 2014 at 03:17:34PM -0400, J. Bruce Fields wrote:
> On Wed, Sep 10, 2014 at 10:28:46AM -0400, Jeff Layton wrote:
> > Signed-off-by: Jeff Layton
> > ---
> > fs/nfs/delegation.c | 37 +
> > fs/nfs/nfs4state.c | 24 +++-
> > fs/
On Wed, 10 Sep 2014 15:17:34 -0400
"J. Bruce Fields" wrote:
> On Wed, Sep 10, 2014 at 10:28:46AM -0400, Jeff Layton wrote:
> > Signed-off-by: Jeff Layton
> > ---
> > fs/nfs/delegation.c | 37 +
> > fs/nfs/nfs4state.c | 24 +++-
> > fs/nfs
On 10/09/14 18:57, Hartmut Knaack wrote:
> Daniel Baluta schrieb, Am 10.09.2014 08:57:
>> Minimal implementation. This driver provides raw illuminance readings.
>>
>> This is based on drivers/hwmon/al3320.c (*) driver from msm tree written
>> by Tsechih Lin
>>
>> * https://android.googlesource.com
The serial8250_do_startup() function unconditionally clears the
interrupts and for that it reads from the RX-FIFO without checking if
there is a byte in the FIFO or not. This works fine on OMAP4+ HW like
AM335x or DRA7.
OMAP3630 ES1.1 (which means probably all OMAP3 and earlier) does not like
this:
Right now it is possible that serial8250_tx_dma() fails and returns
-EBUSY. The caller (serial8250_start_tx()) will then enable
UART_IER_THRI which will generate an interrupt once the TX FIFO is
empty.
In serial8250_handle_irq() nothing will happen because up->dma is set
and so serial8250_tx_chars(
The OMAP UART provides support for HW assisted flow control. What is
missing is the support to throttle / unthrottle callbacks which are used
by the omap-serial driver at the moment.
This patch adds the callbacks. It should be safe to add them since they
are only invoked from the serial_core (uart_
serial8250_do_startup() adds UART_IER_RDI and UART_IER_RLSI to ier.
serial8250_stop_rx() should remove both.
This is what the serial-omap driver has been doing and is now moved to
the 8250-core since it does no look to be *that* omap specific.
Cc: heikki.kroge...@linux.intel.com
Reviewed-by: Tony
At least on AM335x the following problem exists: Even if the TX FIFO is
empty and a TX transfer is programmed (and started) the UART does not
trigger the DMA transfer.
After $TRESHOLD number of bytes have been written to the FIFO manually the
UART reevaluates the whole situation and decides that no
On Tue, 9 Sep 2014, Weike Chen wrote:
> The Synopsys DesignWare APB GPIO driver only supports open firmware devices.
> But, like Intel Quark X1000 SOC, which has a single PCI function exporting
> a GPIO and an I2C controller, it is a Multifunction device. This patch is
> to enable the current Syno
This patch provides a 8250-core based UART driver for the internal OMAP
UART. The long term goal is to provide the same functionality as the
current OMAP uart driver and DMA support.
I tried to merge omap-serial code together with the 8250-core code.
There should should be hardly a noticable differ
Tony noticed that the old omap-serial driver picked the uart "number"
based on the hint given from device tree or platform device's id.
The 8250 based omap driver doesn't do this because the core code does
not honour the ->line argument which is passed by the driver.
This patch aims to keep the sa
On 02/09/14 11:30, Laurentiu Palcu wrote:
> On Mon, Sep 01, 2014 at 08:51:36AM -0700, Srinivas Pandruvada wrote:
>> On Mon, 2014-09-01 at 08:36 -0700, Joe Perches wrote:
>>> On Mon, 2014-09-01 at 12:11 +0300, Laurentiu Palcu wrote:
The following chips are either similar or have only the resolu
While comparing the OMAP-serial and the 8250 part of this I noticed that
the latter does not use run time-pm. Here are the pieces. It is
basically a get before first register access and a last_busy + put after
last access. This has to be enabled from userland _and_ UART_CAP_RPM is
required for this
the diff of v8…v9 is small:
- rebased on top's of Greg's tty-next branch
- fixed #10 where we might have THRE interrupt enabled for longer than
needed
- re-did register setup in #10. Before this "less file" could freeze the
am335x-evm.
Sebastian
--
To unsubscribe from this list: send the line
On Wed, Sep 10, 2014 at 03:28:10PM -0400, Jeff Layton wrote:
> Yes, that's the downside of moving to multiple list_heads. Still, I
> think it's worth doing that even if we end up with the code a bit more
> verbose.
>
> It may be best to consider moving some of this into helpers that live
> in lock
The omap needs a DMA request pending right away. If it is enqueued once
the bytes are in the FIFO then nothing will happen and the FIFO will be
later purged via RX-timeout interrupt.
This patch enqueues RX-DMA request on completion but not if it was
aborted on error. The first enqueue will happen i
I noticed that the serial8250_tx_dma() is invoked sometimes while
uart_circ_empty() says that the buffer is empty.
I tracked one occuring down to:
n_tty_write()
=> O_OPOST(tty))
=> the while loop did something but neither tty's ->write()
nor its ->uart_put_char()
On 02/09/14 10:30, Laurentiu Palcu wrote:
> The following chips are either similar or have only the resolution
> different. Hence, change this driver to support these chips too:
>
> BMI055 - combo chip (accelerometer part is identical to BMC150's)
> BMA255 - identical to BMC150's accelerometer
>
> -Original Message-
> From: Jens Axboe [mailto:ax...@kernel.dk]
> Sent: Wednesday, 10 September, 2014 1:15 PM
> To: Robert Elliott; Elliott, Robert (Server Storage); h...@lst.de;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 1/2] block: default to rq_affinity=2 for blk-mq
>
> On
On Wed, Sep 10, 2014 at 10:28 PM, Jonathan Cameron wrote:
> On 10/09/14 18:57, Hartmut Knaack wrote:
>> Daniel Baluta schrieb, Am 10.09.2014 08:57:
>>> Minimal implementation. This driver provides raw illuminance readings.
>>>
>>> This is based on drivers/hwmon/al3320.c (*) driver from msm tree wr
On Wed, Sep 10, 2014 at 06:59:20PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140909:
>
> New tree: powerpc-merge-mpe
>
> The pm tree gained conflicts against the mvebu and arm-soc trees.
>
> The v4l-dvb tree still had its build failure so I used the version from
> next-201409
On Wed, 10 Sep 2014, Mel Gorman wrote:
> On Tue, Sep 09, 2014 at 07:45:26PM -0700, Hugh Dickins wrote:
> >
> > I've been rather assuming that the 9d340902 seen in many of the
> > registers in that Aug26 dump is the pte val in question: that's
> > SOFT_DIRTY|PROTNONE|RW.
The 900s in the latest dum
With 8250-dma, 8250-omap and am335x I observe the following:
- start a RX transfer which will finish once the FIFO has enough data
- The TX side starts a large TX transfer, say 1244 bytes. It takes approx
102ms for the transfer to complete
- cancel the RX transfer & start the RX transfer a few t
On Wed, Sep 10, 2014 at 06:53:56PM +0300, Dan Carpenter wrote:
> On Wed, Sep 10, 2014 at 05:28:11PM +0200, Jiri Kosina wrote:
> >
> > Too late for this now, yes.
>
> We could still introduce a __kfree_fast_path() which doesn't have
> checking.
Well, there certainly is precedence for that sort of
On Wed, 2014-09-10 at 11:26 -0700, Andy Lutomirski wrote:
> On Wed, Sep 10, 2014 at 9:51 AM, Toshi Kani wrote:
> > This patch changes reserve_memtype() to handle the WT cache mode.
> > When PAT is not enabled, it continues to set UC- to *new_type for
> > any non-WB request.
> >
> > When a target r
On Wed, 2014-09-10 at 20:35 +0100, Jonathan Cameron wrote:
> On 02/09/14 10:30, Laurentiu Palcu wrote:
> > The following chips are either similar or have only the resolution
> > different. Hence, change this driver to support these chips too:
> >
> > BMI055 - combo chip (accelerometer part is ide
From: Joe Perches
Date: Tue, 9 Sep 2014 21:17:27 -0700
> Remove remaining uses of pr_warning in net/
>
> Joe Perches (5):
> atm: Convert pr_warning to pr_warn
> ceph: Convert pr_warning to pr_warn
> pktgen: Convert pr_warning to pr_warn
> iucv: Convert pr_warning to pr_warn
> netfilte
The Alpha EV4/EV5 cpus can corrupt adjacent byte and short data because
those cpus use RMW to store byte and short data. Thus, concurrent adjacent
byte stores could become corrupted, if serialized by a different lock.
tty_struct uses different locks to protect certain fields within the
structure, a
Relocate the file-scope function, send_prio_char(), as a global
helper tty_send_xchar(). Remove the global declarations for
tty_write_lock()/tty_write_unlock(), as these are file-scope only now.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c| 33 +++--
drive
While transmitting a START/STOP char for tcflow(TCION/TCIOFF), prevent
a termios change. Otherwise, a garbage in-band flow control char
may be sent, if the termios change overlaps the transmission setup.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ioctl.c | 10 +++---
1 file changed, 7 i
This patch fixes the following sparse warnings:
CHECK drivers/staging/rtl8188eu/hal/fw.c
drivers/staging/rtl8188eu/hal/fw.c:219:13: warning: cast to restricted
__le16
drivers/staging/rtl8188eu/hal/fw.c:219:13: warning: cast to restricted
__le16
drivers/staging/rtl8188eu/hal/fw.c:219:13: warnin
When a master pty is set to packet mode, flow control changes to
the slave pty cause notifications to the master pty via reads and
polls. However, these tests are occurring for all ttys, not
just ptys.
Implement flow control packet mode notifications in the pty driver.
Only the slave side implemen
Use newly-introduced tty->flow_lock to serialize updates to
tty->flow_stopped (via tcflow()) and with concurrent tty flow
control changes from other sources.
Merge the storage for ->stopped and ->flow_stopped, now that both
flags are serialized by ->flow_lock.
The padding bits are necessary to fo
Will,
On Wed, Sep 10, 2014 at 11:46 AM, Will Deacon wrote:
> On Wed, Sep 10, 2014 at 07:09:59PM +0100, Doug Anderson wrote:
>> On Wed, Sep 10, 2014 at 10:34 AM, Will Deacon wrote:
>> > Setting aside the security model, booting in secure mode can also have a
>> > significant impact on the program
On Wed, 2014-09-10 at 11:29 -0700, Andy Lutomirski wrote:
> On Wed, Sep 10, 2014 at 9:51 AM, Toshi Kani wrote:
:
> > +#ifndef ARCH_HAS_IOREMAP_WT
> > +#define ioremap_wt ioremap_nocache
> > +#endif
> > +
>
> This is a little bit sad. I wouldn't be too surprised if there are
> eventually users w
On Wed, Sep 10, 2014 at 07:32:36PM +0200, Stefan Wahren wrote:
> Am 10.09.2014 17:13, schrieb Mark Brown:
> >Ugh, this looks like it might be a regulator driver but since the
> >subject line was "ARM: " I deleted it unread - if your changelog looks
> >different to all the other changelogs in the s
On 09/10/2014 01:35 PM, Elliott, Robert (Server Storage) wrote:
>
>
>> -Original Message-
>> From: Jens Axboe [mailto:ax...@kernel.dk]
>> Sent: Wednesday, 10 September, 2014 1:15 PM
>> To: Robert Elliott; Elliott, Robert (Server Storage); h...@lst.de;
>> linux-kernel@vger.kernel.org
>> Su
On 09/10/2014 03:33 PM, Sebastian Andrzej Siewior wrote:
> I noticed that the serial8250_tx_dma() is invoked sometimes while
> uart_circ_empty() says that the buffer is empty.
>
> I tracked one occuring down to:
>
> n_tty_write()
>=> O_OPOST(tty))
> => the while loop did somethin
This patch adds the required pieces to 8250-OMAP UART driver for DMA
support. The TX burst size is set to 1 so we can send an arbitrary
amount of bytes.
The RX burst is currently set to 48 which means we receive an DMA
interrupt every 48 bytes and have to reprogram everything. Less bytes in
the RX
1 - 100 of 874 matches
Mail list logo
