'dmaengine_prep_dma_cyclic()' does not return an error pointer, so the test
can be simplified to be more consistent.
Signed-off-by: Christophe JAILLET
---
drivers/tty/serial/sirfsoc_uart.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch adds sysfs "otg_inputs" for usb role swap. This parameter
is write-only and if you use them as the following, you can swap
the usb role.
For example:
1) connect a usb cable using 2 salvator-x boards
2) On A-device (as host), you input the following command:
# echo a_bus_req/ >
The code providing functionality surpassed by the atomic PWM is not needed
anymore and hence can be removed.
Suggested-by: Stefan Agner
Suggested-by: Boris Brezillon
Signed-off-by: Lukasz Majewski
Reviewed-by: Boris
The software reset code has been extracted from imx_pwm_config_v2 function
and moved to new one - imx_pwm_sw_reset().
This change reduces the overall size of imx_pwm_config_v2() and prepares
it for atomic PWM operation.
Suggested-by: Stefan Agner
Suggested-by: Boris Brezillon
The imx-pwm.txt documentation update as a preparation for polarity
support.
Signed-off-by: Bhuvanchandra DV
Signed-off-by: Lukasz Majewski
Acked-by: Rob Herring
---
Changes for v3:
- None
Changes for v2:
- New patch
---
On Tue, 2016-11-01 at 07:33 +0100, Ingo Molnar wrote:
> * Pavel Machek wrote:
>
> > I'm not going to buy broken hardware just for a test.
>
> Can you suggest a method to find heavily rowhammer affected hardware?
> Only by
> testing it, or are there some chipset IDs ranges or
The code, which waits for fifo slot, has been extracted from
imx_pwm_config_v2 function and moved to new one - imx_pwm_wait_fifo_slot().
This change reduces the overall size of imx_pwm_config_v2() and prepares
it for atomic PWM operation.
Suggested-by: Stefan Agner
Hi!
> * Pavel Machek wrote:
>
> > I'm not going to buy broken hardware just for a test.
>
> Can you suggest a method to find heavily rowhammer affected hardware? Only by
> testing it, or are there some chipset IDs ranges or dmidecode info that will
> pinpoint potentially
On Sun, 2016-10-30 at 14:20 +0100, Thorsten Leemhuis wrote:
> As always: Are you aware of any other regressions? Then please let me
> know (simply CC regressi...@leemhuis.info).
Do build regressions count?
Because I was trying to fix an obscure build issue in arch/mips, choose
a random
In the current probe function the GPIO is acquired after the codec's
bus clock is enabled. However if it fails to acquire the GPIO due to
a deferred probe, it does not disable the bus clock before bailing out.
This would result in the clock being enabled multiple times.
Move the code that enables
Hi Sean,
> Andi, it would be good to know what the use-case for the original change is.
the use case is the ir-spi itself which doesn't need the lirc to
perform any waiting on its behalf.
To me it just doesn't look right to simulate a fake transmission
period and wait unnecessary time. Of
From: Lothar Wassmann
Change the pwm chip driver registration, so that a chip driver that
supports polarity inversion can still be used with DTBs that don't
provide the 'PWM_POLARITY' flag.
This is done to provide polarity inversion support for the pwm-imx
driver
With this patch the polarity settings for i.MX's PWMv2 is now supported
on top of atomic PWM setting
Signed-off-by: Bhuvanchandra DV
Signed-off-by: Lukasz Majewski
---
Changes for v3:
- None
Changes for v2:
- New patch
---
I have a prepared another patch that is not USB VID/PID dependent for
rtl8723bu devices. It is more elegant. I will send it after this
email.
If I have more patches is it preferable I just put them on github only
and notify a link address until there might be some resolution?
What I meant below
On Mon, Oct 31, 2016 at 12:41:32PM +0100, Paolo Bonzini wrote:
>
>
> On 31/10/2016 12:05, Borislav Petkov wrote:
> > On Mon, Oct 31, 2016 at 11:47:48AM +0100, Paolo Bonzini wrote:
> >> The information is all in arch/x86/kernel/cpu/scattered.c's cpuid_bits
> >> array. Borislav, would it be okay
On 10/28/2016 04:27 PM, Philipp Zabel wrote:
> Hi Peter,
>
> Am Donnerstag, den 27.10.2016, 13:01 +0300 schrieb Peter Ujfalusi:
>> Move the checks to select the initial state for the backlight to a new
>> function and document the checks we are doing.
>>
>> At the same time correct the handling
Am Dienstag, den 01.11.2016, 08:10 +0100 schrieb Lukasz Majewski:
> From: Sascha Hauer
>
> The use of the ipg clock was introduced with commit 7b27c160c681
> ("pwm: i.MX: fix clock lookup").
> In the commit message it was claimed that the ipg clock is enabled for
>
On Mon, Oct 31, 2016 at 10:25 PM, Rafael J. Wysocki wrote:
> On Thursday, October 27, 2016 09:05:34 AM Brian Norris wrote:
>> Consider two devices, A and B, where B is a child of A, and B utilizes
>> asynchronous suspend (it does not matter whether A is sync or async). If
>> B
>From: Mika Westerberg
>Subject: Re: [RFC v2 2/2] i2c: Pass i2c_device_id to probe func when
using DT ids through ACPI
>Date: Monday 13th June 2016 09:26:55 UTC (5 months ago)
>
>On Fri, Jun 10, 2016 at 06:57:36PM +0300, Crestez Dan Leonard wrote:
>> On 06/10/2016
* Pavel Machek wrote:
> I'm not going to buy broken hardware just for a test.
Can you suggest a method to find heavily rowhammer affected hardware? Only by
testing it, or are there some chipset IDs ranges or dmidecode info that will
pinpoint potentially affected machines?
'ubifs_fast_find_freeable()' can not return an error pointer, so this test
can be removed.
Signed-off-by: Christophe JAILLET
---
fs/ubifs/gc.c | 4
1 file changed, 4 deletions(-)
diff --git a/fs/ubifs/gc.c b/fs/ubifs/gc.c
index e845c64b6ce1..7b35e3d6cde7
'create_root_ns()' does not return an error pointer, so the test can be
simplified to be more consistent.
Signed-off-by: Christophe JAILLET
---
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Commit-ID: 36fd4f0249f8cb445835acb7c6937a0ffa2b5f14
Gitweb: http://git.kernel.org/tip/36fd4f0249f8cb445835acb7c6937a0ffa2b5f14
Author: Andy Lutomirski
AuthorDate: Mon, 31 Oct 2016 15:18:42 -0700
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016
Commit-ID: 5a83d60c074ddf4f6364be25654a643d0e941824
Gitweb: http://git.kernel.org/tip/5a83d60c074ddf4f6364be25654a643d0e941824
Author: Andy Lutomirski
AuthorDate: Mon, 31 Oct 2016 15:18:44 -0700
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016
Commit-ID: cd95ea81f25608c403052d0508ee5c9b32e2bc7d
Gitweb: http://git.kernel.org/tip/cd95ea81f25608c403052d0508ee5c9b32e2bc7d
Author: Andy Lutomirski
AuthorDate: Mon, 31 Oct 2016 15:18:46 -0700
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016
From: Lothar Wassmann
Make the messages that are printed in case of fatal errors actually
visible to the user without having to recompile the driver with
debugging enabled.
Signed-off-by: Lothar Waßmann
Signed-off-by: Bhuvanchandra DV
Commit-ID: 04ac88abaf758bd76edcc3be5549003a017e7963
Gitweb: http://git.kernel.org/tip/04ac88abaf758bd76edcc3be5549003a017e7963
Author: Andy Lutomirski
AuthorDate: Mon, 31 Oct 2016 15:18:45 -0700
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016
On Tue, Nov 01, 2016 at 06:57:23AM +0100, Lukasz Majewski wrote:
> Hi Sascha,
>
> > The current assumption as discussed by Philipp and me is that the ipg
> > clk is only needed when the pwm output is driven by the ipg clk
> > (MX3_PWMCR[16:17] = MX3_PWMCR_CLKSRC_IPG)
>
> At least on my setup
Commit-ID: adb402cd1461eef6e1a21db4532a3b9e6a6be853
Gitweb: http://git.kernel.org/tip/adb402cd1461eef6e1a21db4532a3b9e6a6be853
Author: Borislav Petkov
AuthorDate: Mon, 31 Oct 2016 16:10:15 +0100
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016 07:41:27
Commit-ID: 0d50612c041f213fb6b98e3ff06e306a859c36f2
Gitweb: http://git.kernel.org/tip/0d50612c041f213fb6b98e3ff06e306a859c36f2
Author: Andy Lutomirski
AuthorDate: Mon, 31 Oct 2016 15:18:48 -0700
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016
Commit-ID: bef8b6da95229f780a0a7f63e23124058bfad6d3
Gitweb: http://git.kernel.org/tip/bef8b6da95229f780a0a7f63e23124058bfad6d3
Author: Andy Lutomirski
AuthorDate: Mon, 31 Oct 2016 15:18:47 -0700
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016
This commit provides apply() callback implementation for i.MX's PWMv2.
Suggested-by: Stefan Agner
Suggested-by: Boris Brezillon
Signed-off-by: Lukasz Majewski
Reviewed-by: Boris Brezillon
On 11/1/2016 9:15 AM, Dong Jia Shi wrote:
> * Alex Williamson [2016-10-29 08:03:01 -0600]:
>
>> On Sat, 29 Oct 2016 16:07:05 +0530
>> Kirti Wankhede wrote:
>>
>>> On 10/29/2016 2:03 AM, Alex Williamson wrote:
On Sat, 29 Oct 2016 01:32:35
Hi Junio,
On Mon, Oct 31, 2016 at 02:49:42PM -0700, Junio C Hamano wrote:
[snip]
> * In some projects, it is common to use "[RFC PATCH]" as the subject
>prefix for a patch meant for discussion rather than application. A
>new option "--rfc" was a short-hand for "--subject-prefix=RFC
Hi Christophe,
Am Montag, den 31.10.2016, 18:59 +0100 schrieb Christophe JAILLET:
> 'drm_dev_alloc()' returns an error pointer in case of error, not NULL
> So test it with IS_ERR.
>
> This behavior has been introduced recently in 0f2886057be3. For some
> reason, this file has not been updated.
>
> From: Thomas Gleixner [mailto:t...@linutronix.de]
> Sent: Monday, October 31, 2016 7:40 PM
>>
>> static unsigned long nps_timer_rate;
>> +static int nps_get_timer_clk(struct device_node *node,
>
>Please don't glue variables and functions together w/o a new line. That's
>horrible to read.
On Mon, Oct 31, 2016 at 11:02:36AM +0100, Geert Uytterhoeven wrote:
> On Mon, Oct 31, 2016 at 10:52 AM, Simon Horman wrote:
> > From: Simon Horman
> > Subject: [PATCH] ARM: shmobile: only call rcar_gen2_clocks_init() if present
> >
> > The RZ/G1M
On Monday, 31 October 2016 16:25:44 GMT Maciej W. Rozycki wrote:
> Complement commit 0ae8dceaebe3 ("Merge with 2.3.10.") and use the local
> `fault' handler to recover from FP sigcontext access violation faults,
> like corresponding code does in r4k_fpu.S. The `bad_stack' handler is
> in
On Tuesday 01 November 2016 01:34 AM, David Lechner wrote:
> This fixes pwm name matching for DA850 familiy devices. When using device
> tree, the da850_auxdata_lookup[] table caused pwm devices to have the exact
> same name, which caused errors when trying to register the devices.
>
> We cannot
Commit-ID: 405c0759712f57b680f66aee9c55cd06ad1cbdef
Gitweb: http://git.kernel.org/tip/405c0759712f57b680f66aee9c55cd06ad1cbdef
Author: Andy Lutomirski
AuthorDate: Mon, 31 Oct 2016 08:11:43 -0700
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016
The rtl8723bu wireless IC shows evidence of a more agressive approach to
power saving, powering down its RF side when there is no wireless
interfacing but leaving USB interfacing intact. This makes the wireless
IC more suitable for use in devices which need to keep their power use
as low as
On 01.11.2016 07:33, Ingo Molnar wrote:
Can you suggest a method to find heavily rowhammer affected hardware? Only by
testing it, or are there some chipset IDs ranges or dmidecode info that will
pinpoint potentially affected machines?
I have worked with many different systems both on running
Hello, I hava a question on cma zone.
When we have cma zone, cma zone will be the highest zone of system.
In android system, the most memory allocator is ION. Media system will
alloc unmovable memory from it.
On low memory scene, will the CMA zone always do balance?
Should we transmit the
On Thu, Oct 27, 2016 at 7:35 PM, Gautham R. Shenoy
wrote:
> From: "Gautham R. Shenoy"
>
> In the current code for powernv_add_idle_states, there is a lot of code
> duplication while initializing an idle state in powernv_states table.
>
> Add an
On 01/11/16 09:08, Songjun Wu wrote:
Release the filehandle in 'isc_open' if it's not the only filehandle
opened for the associated video_device.
What's wrong with that? You should always be able to open the device
multiple times. v4l2-compliance will fail after this patch. I'm not sure
what
On Tue, Nov 01, 2016 at 08:51:57AM +0100, Paul Bolle wrote:
> And as probably everybody capable of hacking on lguest (ie, other
> people than me) came up with doubts similar to yours, these two issues
> never got fixed.
You can always try to fix them and see where it gets ya. I think that's
the
Sorry, my mistake, the device should be able to opened multiple times.
It's a wrong patch.
On 11/1/2016 16:52, Hans Verkuil wrote:
On 01/11/16 09:08, Songjun Wu wrote:
Release the filehandle in 'isc_open' if it's not the only filehandle
opened for the associated video_device.
What's wrong
Hi xiaolong,
Sorry for the late reply.
I think I should need to explain for this.
Firstly, please ignore this bug. Because, this patch has be discarded.
The work of this patch has already in the upstream(f3bf1dbe64).
Secondly, I think the cause of the bug is:
I use the "-EINVAL" incorrectly.
On 01/11/16 00:31, Bjorn Andersson wrote:
On Thu 27 Oct 07:10 PDT 2016, Matt Redfearn wrote:
On 19/10/16 13:05, Matt Redfearn wrote:
It is often desireable to boot a remote processor with different
firmware files, depending on the needs of the system at a particular
time. This series adds a
Hi Stephen,
On Mon, 2016-10-31 at 11:06 -0700, Stephen Boyd wrote:
> On 10/31, James Liao wrote:
> > On Thu, 2016-10-27 at 18:17 -0700, Stephen Boyd wrote:
> > > On 10/21, Erin Lo wrote:
> > > > @@ -244,3 +256,31 @@ void mtk_clk_register_composites(const struct
> > > > mtk_composite *mcs,
> > >
>From: Vineet Gupta [mailto:vineet.gup...@synopsys.com]
>Sent: Tuesday, November 1, 2016 12:48 AM
>ARC timers use aux registers for programming and this paves way for moving ARC
>timer drivers into drivers/clocksource
Maybe in this patch or just another one could you move from timer.c to the
Hi,
On 1.11.2016 00:54, Sakari Ailus wrote:
Hi Pavel,
On Sun, Oct 23, 2016 at 10:33:15PM +0200, Pavel Machek wrote:
Hi!
Thanks, this answered half of my questions already. ;-)
:-).
I'll have to go through the patches, et8ek8 driver is probably not
enough to get useful video.
'i2c_new_dummy()' does not return an error pointer, so the test can be
simplified to be more consistent.
Signed-off-by: Christophe JAILLET
---
drivers/mfd/bcm590xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/bcm590xx.c
The commit a55944ca82d2 ("backlight: update bd state & fb_blank properties
when necessary") has posed some extra restrictions on blanking and
unblanking frame buffer device.
Unfortunately, pwm_bl driver's probe did not initialize members of
struct backlight_device necessary for further
Starting from 4.9-rc1 kernel, I started noticing some test failures
of sendfile(2) and splice(2) (sendfile0N and splice01 from LTP) when
testing on sub-page block size filesystems (tested both XFS and
ext4), these syscalls start to return EIO in the tests. e.g.
sendfile021 TFAIL :
On 01.11.2016 09:10, Pavel Machek wrote:
cpu family : 6
model: 23
model name : Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz
stepping : 10
microcode: 0xa07
so rowhammerjs/native is not available for this system. Bit mapping
for memory hash functions would
Release the filehandle in 'isc_open' if it's not the only filehandle
opened for the associated video_device.
Signed-off-by: Songjun Wu
---
drivers/media/platform/atmel/atmel-isc.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git
On 10/31/2016 10:32 PM, Jann Horn wrote:
> When root activates a swap partition whose header has the wrong endianness,
> nr_badpages elements of badpages are swabbed before nr_badpages has been
> checked, leading to a buffer overrun of up to 8GB.
>
> This normally is not a security issue because
Commit-ID: af25ed59b5616b389d90877f7085dc5d457a3d49
Gitweb: http://git.kernel.org/tip/af25ed59b5616b389d90877f7085dc5d457a3d49
Author: Andy Lutomirski
AuthorDate: Mon, 31 Oct 2016 15:18:49 -0700
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016
Commit-ID: fc560a80bac91e512fc37cdfe03a982ef4543c6b
Gitweb: http://git.kernel.org/tip/fc560a80bac91e512fc37cdfe03a982ef4543c6b
Author: Andy Lutomirski
AuthorDate: Mon, 31 Oct 2016 15:18:43 -0700
Committer: Ingo Molnar
CommitDate: Tue, 1 Nov 2016
On Mon, 31 Oct 2016, Kieran Bingham wrote:
> On 31/10/16 13:55, Peter Rosin wrote:
> > On 2016-10-26 10:53, Lee Jones wrote:
> >> On Tue, 25 Oct 2016, Kieran Bingham wrote:
> >>
> >>> If a user provides a shortened string to match a device to the sysfs i2c
> >>> interface it will match on the
This patch set brings atomic operation to i.MX's PWMv2 driver.
This work has been supported and suggested by Boris Brezillon [1] and
Stefan Agner, by showing how simple the transition could be :-).
It has been divided into several steps:
- Remove ipg clock enable/disable code (as proposed by
The code has been rewritten to remove "generic" calls to
imx_pwm_{enable|disable|config}.
Such approach would facilitate switch to atomic PWM (a.k.a ->apply())
implementation.
Suggested-by: Stefan Agner
Suggested-by: Boris Brezillon
This patch provides separate set of pwm ops utilized by
i.MX's PWMv1 and PWMv2.
Signed-off-by: Lothar Waßmann
Signed-off-by: Bhuvanchandra DV
Signed-off-by: Lukasz Majewski
Acked-by: Shawn Guo
From: Sascha Hauer
The use of the ipg clock was introduced with commit 7b27c160c681
("pwm: i.MX: fix clock lookup").
In the commit message it was claimed that the ipg clock is enabled for
register accesses. This is true for the ->config() callback, but not
for the
On 1 November 2016 at 08:24, John Heenan wrote:
> @@ -5779,6 +5779,12 @@ static int rtl8xxxu_start(struct ieee80211_hw *hw)
>
> ret = 0;
>
> + if(priv->fops == _fops) {
OK, let me be the first. Documentation/CodingStyle also says to use
space between "if" and "(" ;)
On Tue, 2016-11-01 at 00:48 +0100, Borislav Petkov wrote:
> --- a/drivers/lguest/Kconfig
> +++ b/drivers/lguest/Kconfig
> config LGUEST
> tristate "Linux hypervisor example code"
> - depends on X86_32 && EVENTFD && TTY && PCI_DIRECT
> > + depends on X86_32 && EVENTFD && TTY &&
On 10/27/2016 05:29 AM, Kirti Wankhede wrote:
> Added two new callback functions to struct vfio_iommu_driver_ops. Backend
> IOMMU module that supports pining and unpinning pages for mdev devices
> should provide these functions.
> Added APIs for pining and unpining pages to VFIO module. These
Hi Sascha
> On Tue, Nov 01, 2016 at 06:57:23AM +0100, Lukasz Majewski wrote:
> > Hi Sascha,
> >
> > > The current assumption as discussed by Philipp and me is that the
> > > ipg clk is only needed when the pwm output is driven by the ipg
> > > clk (MX3_PWMCR[16:17] = MX3_PWMCR_CLKSRC_IPG)
> >
>
On 10/27/2016 05:29 AM, Kirti Wankhede wrote:
> This series adds Mediated device support to Linux host kernel. Purpose
> of this series is to provide a common interface for mediated device
> management that can be used by different devices. This series introduces
> Mdev core module that creates
On Tue, Nov 01, 2016 at 03:48:50PM +0800, He Chen wrote:
> Before sending a patch, let me check if my understanding is right...
> I will add a helper in scattered.c like:
>
> unsigned int get_scattered_cpuid_features(unsigned int level,
> unsigned int
On Tue, Oct 25, 2016 at 04:45:44PM -0500, Eric W. Biederman wrote:
> Andrei Vagin writes:
> >
> > From 8e0f45c0272aa1f789d1657a0acc98c58919dcc3 Mon Sep 17 00:00:00 2001
> > From: Andrei Vagin
> > Date: Tue, 25 Oct 2016 13:57:31 -0700
> > Subject: [PATCH]
On Mon, Oct 31, 2016 at 10:29:37AM +0100, Sascha Hauer wrote:
> > accesses. This is true for the ->config() callback, but not for the
> > ->set_enable() callback. Given that the ipg clock is not consistently
> > enabled for all register accesses we can assume that either it is not
> > required at
Since commit c4dd1ba355aae2bc3d1213da6c66c53e3c31e028
("mfd: stmpe: Add reset support for all STMPE variant")
we're resetting the STMPE expanders before use.
This caused a regression on the STMP2401 on the Nomadik
NHK8815:
stmpe-i2c 0-0043: stmpe2401 detected, chip id: 0x101
nmk-i2c
On Monday, 31 October 2016 16:27:01 GMT Maciej W. Rozycki wrote:
> Fix a regression introduced with commit 2db9ca0a3551 ("MIPS: Use struct
> mips_abi offsets to save FP context") for MIPS I/I FP signal contexts,
> by converting save/restore code to the updated internal API. Start FGR
> offsets
On Mon, Oct 31, 2016 at 12:53:13PM -0700, Michael Zoran wrote:
> On Mon, 2016-10-31 at 11:40 -0700, Michael Zoran wrote:
> > The comment is easy to change.
> >
> > I don't have the log available ATM, but if I remember the DMA API's
> > bugcheck the first time that are used.
> >
> > I think
Add HWCAP2 for x86 and reserve its bit 0 to expose
ring 3 mwait.
Signed-off-by: Grzegorz Andrejczuk
---
arch/x86/include/asm/elf.h | 9 +
arch/x86/include/uapi/asm/hwcap2.h | 7 +++
arch/x86/kernel/cpu/common.c | 3 +++
3 files changed,
Unfortunately presence of this feature cannot be detected
automatically (by reading some other MSR) therefore it is required
to do explicit check for the family and model of the cpu.
If processor is Intel Xeon Phi x200 RING3MWAIT feature is enabled
by setting cpu cap X86_FEATURE_PHIR3MWAIT and
On Monday 31 October 2016 08:15 PM, Bartosz Golaszewski wrote:
> Create the driver for the da8xx master peripheral priority
> configuration and implement support for writing to the three
> Master Priority registers on da850 SoCs.
>
> Signed-off-by: Bartosz Golaszewski
> On 2016-10-27 15:00:32 [-0400], Charles (Chas) Williams wrote:
>>
>> [snip]
>>
>> But sometimes the topology info is correct and if I get lucky, the
>> package id could be valid for all the CPU's. Given the behavior,
>> I have seen so far it makes me thing the RAPL isn't being emulated.
>> So
Make sure to drop the reference taken by bus_find_device_by_name()
before returning from mfd_clone_cell().
Fixes: a9bbba996302 ("mfd: add platform_device sharing support for mfd")
Signed-off-by: Johan Hovold
---
drivers/mfd/mfd-core.c | 2 ++
1 file changed, 2 insertions(+)
Make sure to drop the reference taken by class_find_device() also on
allocation errors in open().
Fixes: 7bd1d4093c2f ("stm class: Introduce an abstraction for...")
Signed-off-by: Johan Hovold
---
drivers/hwtracing/stm/core.c | 9 ++---
1 file changed, 6 insertions(+), 3
Add comment clarifying that of_find_device_by_node() takes a reference
to the embedded struct device which needs to be dropped after use.
Note that most current users fail to do so.
Signed-off-by: Johan Hovold
---
drivers/of/platform.c | 3 +++
1 file changed, 3 insertions(+)
> From: Thomas Gleixner [mailto:t...@linutronix.de]
> Sent: Monday, October 31, 2016 8:13 PM
>>
>> -static unsigned long nps_timer_rate;
>> +static unsigned long nps_timer1_freq;
>This should be either in the previous patch or seperate.
Will fix in V4
>> @@ -101,3 +101,215 @@ static
On Tue, Nov 01, 2016 at 12:36:29AM +, Kuninori Morimoto wrote:
>
> Hi Russell again
>
> > > > +static struct platform_driver snd_dw_hdmi_driver = {
> > > > + .probe = snd_dw_hdmi_probe,
> > >
> > > The driver must have a .remove function, because the platform device it
> > > is
The gpio-keys supports the EV_ABS event type, but does not actually
configure the input device to work with that mode.
This patch configures the axis corresponding to button->code as being
in the range [-1,+1]. This makes it possible to use gpio-keys to
implement a hat (using the ABS_HAT0X
On Monday 31 October 2016 08:18 PM, David Lechner wrote:
> On 10/31/2016 05:18 AM, Sekhar Nori wrote:
>> On Tuesday 25 October 2016 11:24 PM, David Lechner wrote:
>>> This fixes pwm name matching for DA850 familiy devices. When using
>>> device
>>> tree, the da850_auxdata_lookup[] table caused pwm
Make sure to drop the reference taken by class_find_device() after
opening the rtc device.
Fixes: 77437fd4e61f ("pm: boot time suspend selftest")
Signed-off-by: Johan Hovold
---
kernel/power/suspend_test.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Update the comment to of_platform_device_destroy() to reflect that it no
longer returns a status value.
Fixes: 75f353b61342 ("of/platform: Fix of_platform_device_destroy...")
Signed-off-by: Johan Hovold
---
drivers/of/platform.c | 3 ---
1 file changed, 3 deletions(-)
diff
Make sure to drop the references taken by of_get_child_by_name() and
bus_find_device() before returning from cpsw_phy_sel().
Note that there is no guarantee that the devres-managed struct
cpsw_phy_sel_priv will continue to be valid until this function returns
regardless of this change.
Fixes:
Make sure to drop the reference taken by bus_find_device_by_name()
before returning from phy_connect() and phy_attach().
Note that both function still take a reference to the phy device
through phy_attach_direct().
Fixes: e13934563db0 ("[PATCH] PHY Layer fixup")
Signed-off-by: Johan Hovold
Am 31. Oktober 2016 22:54:54 MEZ, schrieb Joerg Roedel :
>On Mon, Oct 31, 2016 at 09:44:51PM +0100, Martin Kepplinger wrote:
>> This is one machine booting a bad kernel. I could provide another
>> example later this week.
>
>You have an Intel system without any IOMMU (enabled),
On 01.11.2016 07:45, Christophe JAILLET wrote:
> 'ubifs_fast_find_freeable()' can not return an error pointer, so this test
> can be removed.
>
> Signed-off-by: Christophe JAILLET
> ---
> fs/ubifs/gc.c | 4
> 1 file changed, 4 deletions(-)
>
> diff --git
On Tue, 01 Nov 2016, Martin Kepplinger wrote:
> Am 31. Oktober 2016 22:54:54 MEZ, schrieb Joerg Roedel :
>>On Mon, Oct 31, 2016 at 09:44:51PM +0100, Martin Kepplinger wrote:
>>> This is one machine booting a bad kernel. I could provide another
>>> example later
On Mon, Oct 31, 2016 at 04:36:33PM -0600, Baicar, Tyler wrote:
> Hello Russell,
>
> On 10/31/2016 4:02 AM, Russell King - ARM Linux wrote:
> >The subject line on this patch is misleading - it's not only ARM64
> >specific...
> Thank you for the feedback!
>
> I only put ARM64 in the subject line
> --- a/drivers/net/dsa/mv88e6xxx/port.c
> +++ b/drivers/net/dsa/mv88e6xxx/port.c
> @@ -61,6 +61,8 @@ int mv88e6xxx_port_set_state(struct mv88e6xxx_chip *chip,
> int port, u8 state)
> return 0;
> }
>
> +/* Offset 0x05: Port Control 1 */
> +
> /* Offset 0x06: Port Based VLAN Map */
>
>
Hello.
On 10/31/2016 7:56 PM, Neil Armstrong wrote:
Add Ethernet node with Internal PHY selection for the Amlogic GXL SoCs
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 45 ++
1 file changed, 45
On Tuesday 01 November 2016 02:17 AM, David Lechner wrote:
> Up to this point, the USB phy clock configuration was handled manually in
> the board files and in the usb drivers. This adds proper clocks so that
> the usb drivers can use clk_get and clk_enable and not have to worry about
> the
Previously, the clocks with a fixed divider would report their rate
as being the same as the one of their parent, independently of the
divider in use. This commit fixes this behaviour.
This went unnoticed as neither the jz4740 nor the jz4780 CGU code
have clocks with fixed dividers yet.
These patches enable Intel Xeon Phi x200 feature to use MONITOR/MWAIT
instruction in ring 3 (userspace) Patches set MSR 0x140 for all logical CPUs.
Then expose it as CPU feature and introduces elf HWCAP capability for x86.
Reference:
1 - 100 of 1184 matches
Mail list logo