Function 12 implements 2D touch position sensor for newer Synaptics touch
devices. It replaces F11 and no device will contain both functions.
Signed-off-by: Andrew Duggan
Signed-off-by: Christopher Heiny
---
drivers/input/rmi4/Kconfig | 11 +
drivers/input/rmi4/Makefile | 1 +
Add the transport driver for devices using RMI4 over I2C.
Signed-off-by: Andrew Duggan
Signed-off-by: Christopher Heiny
---
drivers/input/rmi4/Kconfig | 9 +
drivers/input/rmi4/Makefile | 3 +
drivers/input/rmi4/rmi_i2c.c | 385 +++
3 files
Add devicetree binding for I2C devices and add bindings for optional
parameters in the function drivers. Parameters for function drivers are
defined in child nodes for each of the functions.
Signed-off-by: Andrew Duggan
---
.../devicetree/bindings/input/rmi4/rmi_f01.txt | 39
This is the v3 patch series which fixes the issues identified in the
previous patch series. These include:
- Removal of outdated message in drivers/input/rmi4/Kconfig stating that
some drivers could not be compiled as modules.
- Removal of Pen support in F11. If there is a device which needs it
Synaptics uses the Register Mapped Interface (RMI) protocol as a
communications interface for their devices. This driver adds the core
functionality needed to interface with RMI4 devices.
RMI devices can be connected to the host via several transport protocols
and can supports a wide variety of
On 02.02.2016 17:25, Philipp Hahn wrote:
Hi,
we recently updated our kernel to 4.1.16 + patch for "unix: properly
account for FDs passed over unix sockets" and have since then
self-detected stalls triggered by the Samba daemon:
> >
> > [...]
> >
We have not yet been able to reproduce the
We don't use CLK_IS_ROOT but in a few places in the common clk
framework core. Let's replace those checks with a check for the
number of parents a clk has instead of the flag, freeing up one
flag for something else. We don't remove the flag yet so that
things keep building, but we'll remove it
On 02/01/2016 10:53 AM, Insu Yun wrote:
When kthread_run fails, it returns ERR, not NULL.
Therefore, NULL checking is redundant.
(https://www.kernel.org/doc/htmldocs/device-drivers/API-kthread-run.html)
Thanks, the change looks reasonable.
...
task = kthread_run(kthread, k, "%s",
On Monday, February 01, 2016 03:51:55 PM Roman Pen wrote:
> Do not forget to put the disk back.
>
> Signed-off-by: Roman Pen
> Cc: Gi-Oh Kim
> Cc: "Rafael J. Wysocki"
> Cc: Len Brown
> Cc: Pavel Machek
> Cc: linux...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
Acked-by: Rafael J.
On 02.02.2016 23:56, Nicholas Krause wrote:
> This fixes the function s3c64xx_i2c_cfg_gpio to log output to the
> kernel log buff with WARN_ON if any of the calls to either
> s3c_gpio_cfgpin_range or s3c_gpio_cfgpin fail as we cannot exit
> from s3c64xx_i2s_cfg_gpio if any of these calls fail due
On 02/02/2016 05:07 PM, Rafael J. Wysocki wrote:
On Wed, Feb 3, 2016 at 12:42 AM, Rafael J. Wysocki wrote:
On Tue, Feb 2, 2016 at 11:21 PM, Saravana Kannan wrote:
On 02/02/2016 11:40 AM, Rafael J. Wysocki wrote:
On Tue, Feb 2, 2016 at 6:01 PM, Juri Lelli wrote:
[cut]
I also don't
Hi Joe,
On Wed, Feb 3, 2016 at 12:28 PM, Joe Perches wrote:
> On Wed, 2016-02-03 at 11:19 +1100, Julian Calaby wrote:
>> On Tue, Feb 2, 2016 at 9:27 PM, Chen-Yu Tsai wrote:
>> > Add an entry for X-Powers AXP family PMIC drivers and list myself
>> > as maintainer.
> []
>> > diff --git
On Tuesday, February 02, 2016 01:20:28 PM Bjorn Helgaas wrote:
> I'm on a quest to clean up compiler warnings in drivers/pci. I'd like to
> be able to treat warnings as errors, at least for the 0day build robot.
>
> ---
>
> Bjorn Helgaas (3):
> PCI: Check device_attach() return value
On Wed, 2016-02-03 at 11:19 +1100, Julian Calaby wrote:
> On Tue, Feb 2, 2016 at 9:27 PM, Chen-Yu Tsai wrote:
> > Add an entry for X-Powers AXP family PMIC drivers and list myself
> > as maintainer.
[]
> > diff --git a/MAINTAINERS b/MAINTAINERS
[]
> > @@ -11941,6 +11941,12 @@ F:
On Tuesday, February 02, 2016 11:29:22 AM Alexey Klimov wrote:
> This patch fixes the calculation of pcc_chan for non-zero id.
> After the compiler ignores the (unsigned long) cast the
> pcc_mbox_channels pointer is type-cast and then the type-cast
> offset is added which results in address
On Tue, Feb 2, 2016 at 4:34 PM, Matthew Wilcox wrote:
> On Tue, Feb 02, 2016 at 01:46:06PM -0800, Jared Hulbert wrote:
>> On Tue, Feb 2, 2016 at 8:51 AM, Dan Williams
>> wrote:
>> >> The filesystem I'm concerned with is AXFS
>> >>
clk_get() for DT based clks already returns EPROBE_DEFER when the
OF clk provider is not present. So having all this code in the
clk provider to return EPROBE_DEFER when the gpio isn't ready yet
can be replaced with a platform driver that doesn't add the clk
provider until the gpio can be
On Tuesday, February 02, 2016 04:42:52 PM Jassi Brar wrote:
> On Tue, Feb 2, 2016 at 2:21 AM, Rafael J. Wysocki wrote:
> > On Mon, Feb 1, 2016 at 4:43 PM, Jassi Brar wrote:
> >> On Mon, Feb 1, 2016 at 8:49 PM, Alexey Klimov
> >> wrote:
> >>> (adding Rafael and linux-acpi)
> >>>
> >>> On Fri,
On 01/29/2016 08:35 AM, John Ogness wrote:
> Hi Peter,
>
> On 2016-01-25, Peter Hurley wrote:
>>> The DMA-enabled OMAP UART driver in its current form queues 48 bytes
>>> for a DMA-RX transfer. After the transfer is complete, a new transfer
>>> of 48 bytes is queued. The DMA completion callback
On 02/02/2016 01:34 AM, Benjamin Tissoires wrote:
On Jan 14 2016 or thereabouts, Andrew Duggan wrote:
Synaptics uses the Register Mapped Interface (RMI) protocol as a
communications interface for their devices. This driver adds the core
functionality needed to interface with RMI4 devices.
RMI
On 02.02.2016 22:16, Laxman Dewangan wrote:
> To make RTC block of MAX77686/MAX77802 as independent driver,
> move the registeration of i2c device, regmap for register access
s/registeration/registration/
> and irq_chip for interrupt support inside the RTC driver.
> Removed the same
From: Rafael J. Wysocki
Subject: [PATCH] cpufreq: governor: Replace timers with utilization update
callbacks
Instead of using a per-CPU deferrable timer for queuing up governor
work items, register a utilization update callback that will be
invoked from the scheduler on utilization changes.
On 03.02.2016 01:57, Hannes Frederic Sowa wrote:
On 02.02.2016 23:11, Linus Torvalds wrote:
But I'm OK with that patch as is if you prefer it that way (maybe you
want
to use the cred to then test for root separately etc, out maybe there
already was done use of cred as cred that I just missed
On Thu, Dec 31, 2015 at 11:40 AM, Tony Luck wrote:
> Extend the severity checking code to add a new context IN_KERN_RECOV
> which is used to indicate that the machine check was triggered by code
> in the kernel with a EXTABLE_CLASS_FAULT fixup entry.
I think that the EXTABLE_CLASS_FAULT
The mm-of-the-moment snapshot 2016-02-02-17-08 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On Wed, Feb 3, 2016 at 12:42 AM, Rafael J. Wysocki wrote:
> On Tue, Feb 2, 2016 at 11:21 PM, Saravana Kannan
> wrote:
>> On 02/02/2016 11:40 AM, Rafael J. Wysocki wrote:
>>>
>>> On Tue, Feb 2, 2016 at 6:01 PM, Juri Lelli wrote:
[cut]
>>
>> I also don't like this patch because it forces
The layer enumeration start with 0 (0-15 for LS1021a and 0-63 for
Vybrid) whereas the register enumeration start from 1 (1-10 for
LS1021a and 1-9 for Vybrid). The loop started off from 0 for both
iterations and initialized the number of layers inclusive, which
is one layer too many.
All
Using flat regmap cache instead of RB-tree to avoid the following
lockdep warning on driver load:
[0.697285] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:2755
lockdep_trace_alloc+0x15c/0x160()
[0.697449] DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
The RB-tree regmap cache needs
On 02.02.2016 23:11, Linus Torvalds wrote:
[ sorry for the html mail, I'm out grocery shopping ]
On Feb 2, 2016 13:55, "Hannes Frederic Sowa"
wrote:
I slightly tested the attached patch.
Looks fine. I do wonder: if the only thing we use that "struct cred" for is
to do that ->user lookup,
On Sunday, January 31, 2016 11:38:21 PM Tomas Winkler wrote:
> On Fri, Jan 29, 2016 at 11:45 PM, Rafael J. Wysocki
> wrote:
> > On Friday, January 29, 2016 12:56:14 PM Joe Lawrence wrote:
> >> On 01/29/2016 12:01 PM, Steven Rostedt wrote:
> >> > On Thu, Jan 28, 2016 at 02:13:04PM -0600, Corey
Hi ByeoungWook,
On Wed, Feb 3, 2016 at 11:52 AM, ByeoungWook Kim wrote:
> Hi Julian,
>
> 0xfe and 0xfb was not same codes.
> 0xfe is udelay(50). and 0xfb is mdelay(50).
> It same code like udelay((n) * 1000).
I'm clearly blind! Sorry about that!
> but i agree with your answers of some parts. I
On Tue, Feb 2, 2016 at 4:28 PM, Luis R. Rodriguez wrote:
> On Tue, Feb 2, 2016 at 4:25 PM, H. Peter Anvin wrote:
>> On 02/02/2016 04:22 PM, Luis R. Rodriguez wrote:
>>s>>
Should it be possible to resuse free_init_pages() and/or
free_reserved_area() only for routines (members in the
On 02/02/2016 07:26 PM, Alexandre Courbot wrote:
> On Tue, Feb 2, 2016 at 8:54 AM, William Breathitt Gray
> wrote:
>> By the time request_region is called in several GPIO drivers, a
>> corresponding device structure has already been allocated. The
>> devm_request_region function should be used to
On Tue, Feb 02, 2016 at 04:15:43AM +, Bean Huo 霍斌斌 wrote:
> > Hi Bean,
> >
> > [auto build test WARNING on v4.5-rc2]
>
> This version 2.0 patches are based on 4.2-rc7.
Please don't send patches against ancient kernel versions.
Hi Richard,
> This adds proper single-touch support for BYD touchpads to the psmouse input
> driver.
I posted a driver for the same touchpad a few weeks ago, which has been merged
into linux-next. There's some stuff in this patch which is missing in my driver
though, so we should definitely try
On 2016-01-20 18:50, Stefan Agner wrote:
> Using flat regmap cache instead of RB-tree to avoid the following
> lockdep warning on driver load:
> [0.697285] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:2755
> lockdep_trace_alloc+0x15c/0x160()
> [0.697449]
On Mon, Feb 01, 2016 at 09:29:52AM -0800, Srinivas Kandagatla wrote:
> This patch adds mic support to the lpass driver, most of the driver is
> reused as it is, only the register level access is changed depending on
> te direction of the stream.
>
> Signed-off-by: Srinivas Kandagatla
> ---
>
On Mon, Feb 01, 2016 at 09:29:46AM -0800, Srinivas Kandagatla wrote:
> This patch add mic support on apq8016-sbc board aka db410c. Tested it
> with headset mic.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> sound/soc/qcom/apq8016_sbc.c | 10 +++---
> 1 file changed, 7 insertions(+), 3
On Mon, Feb 01, 2016 at 09:29:26AM -0800, Srinivas Kandagatla wrote:
> This patch adds wrdma registers into the lpaif-reg.h.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> sound/soc/qcom/lpass-lpaif-reg.h | 11 +++
> 1 file changed, 11 insertions(+)
Acked-by: Kenneth Westfield
--
On Mon, Feb 01, 2016 at 09:29:07AM -0800, Srinivas Kandagatla wrote:
> rdma_ch_bit_map can be reused for wrdma channel allocations as wrdma
> channel numbering start after rdma channel numbers.
> With capture support referring rdma_ch_bit_map for wrdma channel
> allocation
> is confusing, so
On Mon, Feb 01, 2016 at 09:29:38AM -0800, Srinivas Kandagatla wrote:
> Now that we are ready to access wrdma registers, set the max register
> and other regmap related configs to use correct values.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> sound/soc/qcom/lpass-cpu.c | 33
On Mon, Feb 01, 2016 at 09:29:32AM -0800, Srinivas Kandagatla wrote:
> diff --git a/sound/soc/qcom/lpass-lpaif-reg.h
> b/sound/soc/qcom/lpass-lpaif-reg.h
> index 2008f9f..2114b3e 100644
> --- a/sound/soc/qcom/lpass-lpaif-reg.h
> +++ b/sound/soc/qcom/lpass-lpaif-reg.h
...
> +#define
On Mon, Feb 01, 2016 at 09:28:55AM -0800, Srinivas Kandagatla wrote:
> diff --git a/sound/soc/qcom/lpass-lpaif-reg.h
> b/sound/soc/qcom/lpass-lpaif-reg.h
> index 95e22f1..8a64d1a 100644
> --- a/sound/soc/qcom/lpass-lpaif-reg.h
> +++ b/sound/soc/qcom/lpass-lpaif-reg.h
> @@ -47,6 +47,28 @@
...
>
On Mon, Feb 01, 2016 at 09:29:20AM -0800, Srinivas Kandagatla wrote:
> diff --git a/sound/soc/qcom/lpass-apq8016.c
> b/sound/soc/qcom/lpass-apq8016.c
> index df44f09..3eef0c3 100644
> --- a/sound/soc/qcom/lpass-apq8016.c
> +++ b/sound/soc/qcom/lpass-apq8016.c
...
> @@ -213,7 +225,11 @@ static
On Mon, Feb 01, 2016 at 09:29:01AM -0800, Srinivas Kandagatla wrote:
> diff --git a/sound/soc/qcom/lpass.h b/sound/soc/qcom/lpass.h
> index 30449f3..8475b60 100644
> --- a/sound/soc/qcom/lpass.h
> +++ b/sound/soc/qcom/lpass.h
> @@ -80,6 +80,7 @@ struct lpass_variant {
>* at different
On Mon, Feb 01, 2016 at 09:28:43AM -0800, Srinivas Kandagatla wrote:
> diff --git a/sound/soc/qcom/lpass-ipq806x.c
> b/sound/soc/qcom/lpass-ipq806x.c
> index 119048c..8bdcdcb 100644
> --- a/sound/soc/qcom/lpass-ipq806x.c
> +++ b/sound/soc/qcom/lpass-ipq806x.c
> @@ -65,7 +65,10 @@ static struct
On Mon, Feb 01, 2016 at 09:28:49AM -0800, Srinivas Kandagatla wrote:
> This patch adds wrdma related register offsets to the lpass variant data
> of ipq806x.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> sound/soc/qcom/lpass-ipq806x.c | 4
> 1 file changed, 4 insertions(+)
Acked-by:
On Mon, Feb 01, 2016 at 09:28:34AM -0800, Srinivas Kandagatla wrote:
> This patch updates the internal dma allocation callbacks to take the
> stream direction so that it can allocate channels suitable for that
> stream direction. Before the capture support this was not necessary.
>
>
On Mon, Feb 01, 2016 at 09:28:28AM -0800, Srinivas Kandagatla wrote:
> diff --git a/sound/soc/qcom/lpass-platform.c
> b/sound/soc/qcom/lpass-platform.c
> index a6dce1b..bfc9de6 100644
> --- a/sound/soc/qcom/lpass-platform.c
> +++ b/sound/soc/qcom/lpass-platform.c
> @@ -91,7 +91,7 @@ static int
On Mon, Feb 01, 2016 at 09:28:20AM -0800, Srinivas Kandagatla wrote:
> This patch adds wrdma related register offsets and shifts into lpass
> variant structure.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> sound/soc/qcom/lpass.h | 3 +++
> 1 file changed, 3 insertions(+)
Acked-by: Kenneth
On Mon, Feb 01, 2016 at 09:27:59AM -0800, Srinivas Kandagatla wrote:
> diff --git a/sound/soc/qcom/lpass-platform.c
> b/sound/soc/qcom/lpass-platform.c
> index 4aeb8e1..a6dce1b 100644
> --- a/sound/soc/qcom/lpass-platform.c
> +++ b/sound/soc/qcom/lpass-platform.c
> @@ -439,39 +439,6 @@ static
On Tue, Feb 02, 2016 at 01:46:06PM -0800, Jared Hulbert wrote:
> On Tue, Feb 2, 2016 at 8:51 AM, Dan Williams wrote:
> >> The filesystem I'm concerned with is AXFS
> >> (https://www.kernel.org/doc/ols/2008/ols2008v1-pages-211-218.pdf).
> >> Which I've been planning on trying to merge again due to
On Thu, 28 Jan 2016 09:27:28 +0100 Andrzej Hajda wrote:
> - use '<= 0' instead of '< 0' to silence gcc verbose warnings,
> - expand commit message.
> ---
> include/linux/err.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/err.h
On Mon, Feb 01, 2016 at 09:27:02AM -0800, Srinivas Kandagatla wrote:
> LPASS IP on QCOM SOC supports both Playback and capture
> via I2S, but this feature is missing in existing code.
> This patchset aims at adding capture support to lpass IP.
> First few patches in this series does cleanup the
On Wed, 2016-02-03 at 11:09 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> kernel/memremap.c
>
> between commit:
>
> eb7d78c9e7f6 ("devm_memremap_pages: fix vmem_altmap lifetime +
> alignment handling")
>
> from Linus' tree and
On Tue, Feb 2, 2016 at 3:41 PM, Dan Williams wrote:
> On Tue, Feb 2, 2016 at 3:36 PM, Jared Hulbert wrote:
>> On Tue, Feb 2, 2016 at 3:19 PM, Al Viro wrote:
>>>
>>> On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wrote:
>>>
>>> > However, for raw block devices and for XFS with a
On Wed, Feb 3, 2016 at 9:17 AM, Nicholas Krause wrote:
> This fixes a possible NULL pointer deference in the function,
> davinci_gpio_probe due to the function, gpio2regs being able
> to return a NULL pointer if it rans to get the registers for
> the gpio devices on a davinci board. Furthermore
On Tue, Feb 2, 2016 at 4:25 PM, H. Peter Anvin wrote:
> On 02/02/2016 04:22 PM, Luis R. Rodriguez wrote:
>>>
>>> Should it be possible to resuse free_init_pages() and/or
>>> free_reserved_area() only for routines (members in the array in this
>>> case of a struct of fns) that don't meet our
On Wed, Feb 3, 2016 at 9:10 AM, nick wrote:
>
>
> On 2016-02-02 06:30 PM, Alexandre Courbot wrote:
>> On Fri, Jan 29, 2016 at 6:04 AM, Nicholas Krause wrote:
>>> This fixes a possible NULL pointer deference in the function,
>>> davinci_gpio_probe due to the function, gpio2regs being able
>>> to
On Tue, Feb 2, 2016 at 8:54 AM, William Breathitt Gray
wrote:
> By the time request_region is called in several GPIO drivers, a
> corresponding device structure has already been allocated. The
> devm_request_region function should be used to help simplify the cleanup
> code and reduce the
On 02/02/2016 04:22 PM, Luis R. Rodriguez wrote:
>>
>> Should it be possible to resuse free_init_pages() and/or
>> free_reserved_area() only for routines (members in the array in this
>> case of a struct of fns) that don't meet our subarch once we're done
>> iterating over the routies and know we
On Mon, 01 Feb 2016, Paul E. McKenney wrote:
On Mon, Feb 01, 2016 at 11:28:07AM +0800, Kefeng Wang wrote:
Just like I mentioned before, keep consistent with rcutorture???
Because rcutorture does it doesn't mean locktorture has to do it ;)
In any case, I'd suggest the same be done for
On Fri, Jan 22, 2016 at 1:52 PM, Luis R. Rodriguez
wrote:
> On Fri, Jan 22, 2016 at 11:06 AM, H. Peter Anvin wrote:
>> On 01/22/2016 05:44 AM, Michael Matz wrote:
>>> Hi,
>>>
>>> On Thu, 21 Jan 2016, H. Peter Anvin wrote:
>>>
Something that confuses me is that gcc seems to give these
Hi Chen-Yu,
On Tue, Feb 2, 2016 at 9:27 PM, Chen-Yu Tsai wrote:
> Add an entry for X-Powers AXP family PMIC drivers and list myself
> as maintainer.
>
> Cc: Carlo Caione
> Cc: Maxime Ripard
> Cc: Ramakrishna Pallala
> Cc: Todd Brandt
> Cc: Jacob Pan
> Signed-off-by: Chen-Yu Tsai
> ---
>
On Tue, Feb 2, 2016 at 3:48 PM, H. Peter Anvin wrote:
> On 01/22/2016 05:44 AM, Michael Matz wrote:
>> Hi,
>>
>> On Thu, 21 Jan 2016, H. Peter Anvin wrote:
>>
>>> Something that confuses me is that gcc seems to give these sections the
>>> "aw" attributes which makes as complain. This might be a
Hi Andrew,
On Tue, 2 Feb 2016 15:04:35 -0800 Andrew Morton
wrote:
>
> On Tue, 2 Feb 2016 23:37:50 +0100 Christian Borntraeger
> wrote:
>
> >
> > I pushed it on my tree for kbuild testing purposes some days ago.
> > Will drop so that it can go via mm.
>
> There are other patches that I
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
kernel/memremap.c
between commit:
eb7d78c9e7f6 ("devm_memremap_pages: fix vmem_altmap lifetime + alignment
handling")
from Linus' tree and commit:
1c29f25bf5d6 ("memremap: Change region_intersects() to take @flags and
On 02.02.2016 22:16, Laxman Dewangan wrote:
> Get rid of referring parent device info for register access
> all the places by making regmap as part of max77686 rtc
> device info. This will also remove the need of storing parent
> device info in max77686 rtc device info as this is no more required.
On Wed, Feb 3, 2016 at 4:53 AM, Bjorn Helgaas wrote:
> asm/gpio.h is included only by linux/gpio.h, and then only when the arch
> selects ARCH_HAVE_CUSTOM_GPIO_H. Only the following arches select it: arm
> avr32 blackfin m68k (COLDFIRE only) sh unicore32.
>
> Remove the unused asm/gpio.h files
On Wed, Feb 3, 2016 at 4:53 AM, Bjorn Helgaas wrote:
> Most arches have an asm/gpio.h that merely includes linux/gpio.h. The
> others select ARCH_HAVE_CUSTOM_GPIO_H, and when that's selected,
> linux/gpio.h includes asm/gpio.h.
Looks correct if that's really what happens, GPIO includes can be
On 02.02.2016 22:16, Laxman Dewangan wrote:
> rtc_regmap should be used to access all RTC regsiters instead
> of parent regmap regardless of what chip or property have it.
>
> This makes the register access uniform and extendible for other
> chips.
>
> Signed-off-by: Laxman Dewangan
> CC:
On 1/28/2016 6:20 PM, Douglas Anderson wrote:
> This is a bit of catchall series for all the bug fix and performance
> patches I've been working on over the last few months. Note that for
> dwc2 we need to do LOTS in software and need super low interrupt
> latency, so most performance
On 02.02.2016 22:16, Laxman Dewangan wrote:
> Fix following check patch error in rtc-max77686 driver:
> - Alignment should match open parenthesis.
> - braces {} should be used on all arms of this statement.
> - Prefer using the BIT macro
>
> Signed-off-by: Laxman Dewangan
> ---
>
Hi Linus,
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.5-3
for you to fetch changes up to
On Tue, Feb 02, 2016 at 03:39:15PM -0800, Dan Williams wrote:
> On Tue, Feb 2, 2016 at 3:19 PM, Al Viro wrote:
> > On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wrote:
> >> However, for raw block devices and for XFS with a real-time device, the
> >> value in inode->i_sb->s_bdev is not
On 01/22/2016 05:44 AM, Michael Matz wrote:
> Hi,
>
> On Thu, 21 Jan 2016, H. Peter Anvin wrote:
>
>> Something that confuses me is that gcc seems to give these sections the
>> "aw" attributes which makes as complain. This might be a gcc bug.
>
> Workaround: use an (possibly empty)
The Apex Embedded Systems STX104 is a 16-channel 16-bit analog input and
2-channel 16-bit analog output PC/104 card. The STX104 incorporates a
large one mega-sample FIFO.
This driver provides IIO support for the 2-channel DAC on the STX104.
The base port address for the device may be configured
On Tue, Feb 2, 2016 at 11:21 PM, Saravana Kannan wrote:
> On 02/02/2016 11:40 AM, Rafael J. Wysocki wrote:
>>
>> On Tue, Feb 2, 2016 at 6:01 PM, Juri Lelli wrote:
>>>
>>> Hi Rafael,
>>>
>>> On 02/02/16 17:35, Rafael J. Wysocki wrote:
On Tue, Feb 2, 2016 at 4:47 PM, Juri Lelli wrote:
On Tue, Feb 2, 2016 at 3:36 PM, Jared Hulbert wrote:
> On Tue, Feb 2, 2016 at 3:19 PM, Al Viro wrote:
>>
>> On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wrote:
>>
>> > However, for raw block devices and for XFS with a real-time device, the
>> > value in inode->i_sb->s_bdev is not
[ adding btrfs, resend with the correct list address ]
On Tue, Feb 2, 2016 at 3:19 PM, Al Viro wrote:
> On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wrote:
>
>> However, for raw block devices and for XFS with a real-time device, the
>> value in inode->i_sb->s_bdev is not correct.
[ adding btrfs ]
On Tue, Feb 2, 2016 at 3:19 PM, Al Viro wrote:
> On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wrote:
>
>> However, for raw block devices and for XFS with a real-time device, the
>> value in inode->i_sb->s_bdev is not correct. With the code as it is
>> currently
On Tue, Feb 2, 2016 at 3:19 PM, Al Viro wrote:
>
> On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wrote:
>
> > However, for raw block devices and for XFS with a real-time device, the
> > value in inode->i_sb->s_bdev is not correct. With the code as it is
> > currently written, an fsync
Kever,
On Mon, Feb 1, 2016 at 11:04 PM, Kever Yang wrote:
>>> Oh, now I get what you're saying!
>>>
>>> A) You've got dwc2_release_channel() -> dwc2_deactivate_qh() ->
>>> dwc2_hcd_qh_deactivate()
>>> ...and always in that case we'll do a select / queue, so we don't need it
>>> there.
>>>
>>> B)
On Tue, Feb 02, 2016 at 03:39:18PM +0530, Ganapatrao Kulkarni wrote:
> dt node parsing for numa topology is done using device property
> numa-node-id and device node distance-map.
>
> Reviewed-by: Robert Richter
> Signed-off-by: Ganapatrao Kulkarni
> ---
> drivers/of/Kconfig | 11 +++
>
On Fri, Jan 29, 2016 at 6:04 AM, Nicholas Krause wrote:
> This fixes a possible NULL pointer deference in the function,
> davinci_gpio_probe due to the function, gpio2regs being able
> to return a NULL pointer if it rans to get the registers for
> the gpio devices on a davinci board. Furthermore
Make use of the EXTABLE_FAULT exception table entries. This routine
returns a structure to indicate the result of the copy:
struct mcsafe_ret {
u64 trapnr;
u64 remain;
};
If the copy is successful, then both 'trapnr' and 'remain' are zero.
If we faulted during the copy, then
On Tuesday 02 February 2016 17:14:49 Bjorn Helgaas wrote:
> On Tue, Feb 02, 2016 at 09:25:25PM +0100, Arnd Bergmann wrote:
> > On Monday 01 February 2016 18:07:45 Joao Pinto wrote:
> > > +static void synopsys_pcie_establish_link(struct pcie_port *pp)
> > > +{
> > > + int retries = 0;
> > > +
> >
This series is initially targeted at the folks doing filesystems
on top of NVDIMMs. They really want to be able to return -EIO
when there is a h/w error (just like spinning rust, and SSD does).
I plan to use the same infrastructure to write a machine check aware
"copy_from_user()" that will
Extend the severity checking code to add a new context IN_KERN_RECOV
which is used to indicate that the machine check was triggered by code
in the kernel with a EXTABLE_CLASS_FAULT fixup entry.
Major re-work to the tail code in do_machine_check() to make all this
readable/maintainable. One
Huge amounts of help from Andy Lutomirski and Borislav Petkov to
produce this. Andy provided the inspiration to add classes to the
exception table with a clever bit-squeezing trick, Boris pointed
out how much cleaner it would all be if we just had a new field.
Linus Torvalds blessed the
The Intel Software Developer Manual describes bit 24 in the MCG_CAP
MSR:
MCG_SER_P (software error recovery support present) flag,
bit 24 — Indicates (when set) that the processor supports
software error recovery
But only some models with this capability bit set will actually
generate
The X/Y position measurements read from the controller are interpreted
wrong. The first measurement X+ contains the Y position, and the second
measurement Y+ the X position (see also Table 11 Register Table in the
data sheet).
The problem is already known and a swap option has been introduced:
Add device tree support for the I2C and SPI variant of AD7879(-1).
This allows to specify the touchscreen controller as a I2C client
node or SPI slave device. Most of the options available in platform
data are also available as device tree properties, the only exception
being GPIO capabilities,
The header file is used by the SPI and I2C variant of the driver.
Therefore, move it to a more generic place under platform_data.
Signed-off-by: Stefan Agner
---
Changes since v2:
- (none)
Changes since v1:
- Move to include/linux/platform_data/
arch/blackfin/mach-bf527/boards/ezbrd.c| 2
On Tue, 02 Feb 2016 22:25:45 +0100,
Dmitry Vyukov wrote:
>
> On Mon, Feb 1, 2016 at 11:36 AM, Takashi Iwai wrote:
> > On Mon, 01 Feb 2016 11:15:08 +0100,
> > Dmitry Vyukov wrote:
> >>
> >> Hello,
> >>
> >> The following program triggers WARNING in snd_rawmidi_kernel_write1:
> >>
> >> //
On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wrote:
> However, for raw block devices and for XFS with a real-time device, the
> value in inode->i_sb->s_bdev is not correct. With the code as it is
> currently written, an fsync or msync to a DAX enabled raw block device will
> cause a
On 02/02/2016 04:09 PM, Sakari Ailus wrote:
> Hi Shuah,
>
> On Tue, Feb 02, 2016 at 04:04:50PM -0700, Shuah Khan wrote:
>> On 02/02/2016 03:53 PM, Sakari Ailus wrote:
>>> Hi Shuah,
>>>
>>> On Sat, Jan 30, 2016 at 01:10:52PM -0700, Shuah Khan wrote:
Change media_entity_pipeline_stop() to not
On Fri, Jan 29, 2016 at 04:28:14PM -0800, Jarkko Sakkinen wrote:
> Fixed rollback and gave better names to the functions (more
> self-documenting, less confusing).
>
> Fixes: d972b0523f ("tpm: fix call order in tpm-chip.c")
> Signed-off-by: Jarkko Sakkinen
> cc: sta...@vger.kernel.org
>
On 02/02/2016 02:59 PM, David Rientjes wrote:
> On Tue, 2 Feb 2016, Mike Kravetz wrote:
>
>> Attempting to preallocate 1G gigantic huge pages at boot time with
>> "hugepagesz=1G hugepages=1" on the kernel command line will prevent
>> booting with the following:
>>
>> kernel BUG at
On Tue, Feb 02, 2016 at 09:25:25PM +0100, Arnd Bergmann wrote:
> On Monday 01 February 2016 18:07:45 Joao Pinto wrote:
> > +static void synopsys_pcie_establish_link(struct pcie_port *pp)
> > +{
> > + int retries = 0;
> > +
> > + /* check if the link is up or not */
> > + for (retries = 0;
201 - 300 of 2334 matches
Mail list logo
