> From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
> Sent: Sunday, November 01, 2015 10:44 PM
> Please add an entry in the clocksource's Kconfig.
> eg:
OK
> Are you sure all the headers are needed ?
Thanks, will revise this part.
> Why do you need to disable the interrupt here ?
Thanks,
> On Oct 30, 2015, at 21:47, Jiri Kosina wrote:
>
> From: Jiri Kosina
>
> Freeze all filesystems during hibernation in favor of dropping kthread
> freezing completely.
>
> Kthread freezing has a history of not very well defined semantics.
> Historically, it has been established to make sure t
Hi Heiko,
On 2015年10月30日 16:54, Heiko Stuebner wrote:
> Hi Zain,
>
> Am Freitag, 30. Oktober 2015, 16:22:47 schrieb Zain Wang:
>> set an id for crypto clk, so that it can be called in other part.
>>
>> Signed-off-by: Zain Wang
>> ---
>> drivers/clk/rockchip/clk-rk3288.c | 2 +-
>> 1 file changed
On Saturday 31 October 2015 06:52 PM, Noam Camus wrote:
> From: Tal Zilcer
>
> Since the CTOP is SMT hardware multi-threaded, we need to hint
> the HW that now will be a very good time to do a hardware
> thread context switching. This is done by issuing the schd.rw
> instruction (binary coded here
According to [1], 'perf state' should avoid output too much information
if '-v' not set, only 'Ok', 'FAIL' or 'Skip' need to be printed.
This patch removes sereval stderr output to make output clean.
Before this patch:
# perf test dummy
23: Test using a dummy software event to keep tracking
On Saturday 31 October 2015 06:53 PM, Noam Camus wrote:
> From: Noam Camus
>
> We add IPI irq definition to be used later by any
> irqchip such NPS400 IC.
>
> Signed-off-by: Noam Camus
Again this break bisectability - it needs to be placed before you use this
#define
in patch 3/20.
Anyhow since
On 28.10.2015 19:45, Luis Henriques wrote:
> On Tue, Oct 27, 2015 at 11:10:29AM +0900, Michel Dänzer wrote:
>> On 26.10.2015 22:42, Luis Henriques wrote:
>>> 3.16.7-ckt19 -stable review patch. If anyone has any objections, please
>>> let me know.
>>>
>>> --
>>>
>>> From: =TF-8?q?M
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/entry_compat
commit 21e1317765f4e19c6bfe63a148d41cc665aa0977 ("x86/entry/64: Fix irqflag
tracing wrt context tracking")
+++
On 10/30/2015 01:45 PM, Arnd Bergmann wrote:
> On Friday 30 October 2015 12:58:33 Hannes Reinecke wrote:
>>> @@ -1076,7 +1069,7 @@ static int stex_ss_handshake(struct st_hba *hba)
>>> h->req_cnt = cpu_to_le16(hba->rq_count+1);
>>> h->status_sz = cpu_to_le16(sizeof(struct status_msg));
>
+CC Peter.
On Saturday 31 October 2015 06:53 PM, Noam Camus wrote:
> From: Tal Zilcer
>
> In SMT system like we have the generic "sync" is not working with
> HW threads. The replacement is "schd.rw" instruction that is served
> as cpu barrier for HW threads.
> Signed-off-by: Noam Camus
> ---
>
On Sun, 01 Nov 2015 20:53:14 +0100,
Ondrej Zary wrote:
>
> ESS Allegro (marked ES1989S), [125d:1988] (rev 10) is mute after
> loading snd-maestro3 and running alsactl restore. Touching master
> volume or mute makes it work.
>
> Looks like a bug in the AC'97 codec integrated into the chip.
>
> Wr
On Mon 02-11-15 07:20:37, Huang, Ying wrote:
> Michal Hocko writes:
>
> > On Fri 30-10-15 16:21:40, Huang, Ying wrote:
> >> Michal Hocko writes:
> >>
> >> > On Wed 28-10-15 13:36:02, kernel test robot wrote:
> >> >> FYI, we noticed the below changes on
> >> >>
> >> >> https://git.kernel.org/pu
On Fri, Oct 30, 2015 at 4:22 AM, Daniel Lezcano
wrote:
> Instead of having the clocksource's Kconfig depending on the arch, let the
> arch to select the timer it needs.
Is this the prescribed way to do things nowadays? It leads to more
options showing up in 'make menuconfig'. Why do I need to see
On Fri, Oct 30, 2015 at 08:40:52AM -0700, Alexander Duyck wrote:
>On 10/29/2015 08:48 PM, Wei Yang wrote:
>>On Thu, Oct 29, 2015 at 05:22:54PM -0500, Bjorn Helgaas wrote:
>>>ines: 115
>>>
>>>From: Alexander Duyck
>>>
>>>The enumeration path should leave NumVFs set to zero. But after
>>>4449f07972
On Thu, Oct 22, 2015 at 01:14:14PM -0500, Tom Zanussi wrote:
> Allow users to specify trace event fields to use in aggregated sums
> via a new 'vals=' keyword. Before this addition, the only aggregated
> sum supported was the implied value 'hitcount'. With this addition,
> 'hitcount' is also supp
Hello,
On Sun, Nov 01, 2015 at 06:32:56PM -0800, Guenter Roeck wrote:
> Since commit 7d8c70d8048c ("serial: mctrl-gpio: rename init function"),
> crisv32 either do not build or crash as follows.
>
> Unable to handle kernel NULL pointer dereference
> Linux 4.3.0-rc7-next
Ouch! The notifier.h must be included. I didn't notice this error in ARM
architecture. Let me fix this error in next patch-set.
Thanks a lot for catching this!
Best regards,
Milo
diff --git a/include/linux/mfd/ti-lmu.h b/include/linux/mfd/ti-lmu.h
index eeb6b9e..44268c7 100644
--- a/include/lin
Hello!
> > --- cut exynos5410.dtsi ---
> > sromc: sromc@1225 {
> > #address-cells = <2>;
> > #size-cells = <1>;
> > ranges = <0 0 0x0400 0x2
> > 1 0 0x0500 0x2
> >
Hi!
One more thing: in my config, I get ton of warnings. I'm not using
modules, so everything is built-in.
Best regards,
Pavel
In file included from drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c:24:0:
drivers/gpu/drm/amd/amdgpu/amdgpu.h:1
Hello Philipp,
On Thu, Oct 29, 2015 at 10:10:17AM +0100, Philipp Zabel wrote:
> Since this array is static const, it should be marked as __initconst.
independent of your change sunxi_reset_init can be moved to .init.text,
too.
Best regards
Uwe
--
Pengutronix e.K. | Uw
>
> Therefore please adjust the variable name appropriately, thanks.
David,
Thanks for the feedback, I will send out a v3.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
On Mon, 2 Nov 2015, Takashi Sakamoto wrote:
> Hi,
>
> On Nov 02 2015 15:55, Julia Lawall wrote:
> > Move constant to the right of binary operators.
> >
> > Generated by: scripts/coccinelle/misc/compare_const_fl.cocci
> >
> > CC: Takashi Sakamoto
> > Signed-off-by: Fengguang Wu
> > Signed-off-
Hello!
> > On certain hardware after software reboot the chip may get stuck and fail
> > to reinitialize during reset. This can be fixed by ensuring that PHY is
> > reset too.
> >
> > Old PHY resetting method required operational MDIO interface, therefore
> > the chip should have been already set
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Sunday, November 01, 2015 8:59 PM
>
> On Sun, Nov 01, 2015 at 11:11:23AM +, Kweh, Hock Leong wrote:
> > Hmm If I combine these 2 flags to become one as
> > "NO_MORE_WRITE_ACTION" to better describing the
Hi Tom,
On Thu, Oct 29, 2015 at 01:35:43PM -0500, Tom Zanussi wrote:
> Hi Namhyung,
>
> On Thu, 2015-10-29 at 17:31 +0900, Namhyung Kim wrote:
> > Hi Tom,
> >
> > On Thu, Oct 22, 2015 at 01:14:12PM -0500, Tom Zanussi wrote:
> > > Add tracing_map, a special-purpose lock-free map for tracing.
> >
On Nov 01 '15 19:13, Greg KH wrote:
> On Sun, Nov 01, 2015 at 09:56:18PM +0100, Valentin Rothberg wrote:
> > On Nov 01 '15 11:45, Greg KH wrote:
> > > On Sun, Nov 01, 2015 at 07:30:14PM +0100, Valentin Rothberg wrote:
> > > > On Nov 01 '15 10:13, Greg KH wrote:
> > > > > On Sun, Nov 01, 2015 at 01:
Hi,
On Nov 02 2015 15:55, Julia Lawall wrote:
Move constant to the right of binary operators.
Generated by: scripts/coccinelle/misc/compare_const_fl.cocci
CC: Takashi Sakamoto
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
Depends on personal taste, but the modified version do
On Sunday 01 November 2015 04:51 AM, Alexey Brodkin wrote:
> As of today default .dtb will be built (and subsequently will be built-in
> kernel binary) even if CONFIG_ARC_BUILTIN_DTB_NAME is not set.
>
> But it is possible we're going to use external .dtb and so we don't want to
> have .dtb built-i
Move constant to the right of binary operators.
Generated by: scripts/coccinelle/misc/compare_const_fl.cocci
CC: Takashi Sakamoto
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
Depends on personal taste, but the modified version does look a little
nicer to me, since one can bett
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Sunday, November 01, 2015 6:30 PM
> >
> > Example method to load the capsule binary:
> > cat firmware.bin > /dev/efi_capsule_loader
>
> $ cat "some_dumb_file" > /dev/efi_capsule_loader
> Killed
>
> and in dmesg:
Hi Jiri,
On Sat, Oct 31, 2015 at 12:09:46PM +0100, Jiri Olsa wrote:
> On Sat, Oct 31, 2015 at 02:15:38AM +0900, Namhyung Kim wrote:
>
> SNIP
>
> >
> > if (!rem_sq_bracket)
> > return ret;
> >
> > + if (callchain_param.value == CCVAL_COUNT) {
> > +
On Saturday 31 October 2015 06:50 PM, Noam Camus wrote:
> From: Tal Zilcer
>
> At cpu_kick() we call res_service which can be implement by each
> platform and override gerneric weak definition.
>
> Signed-off-by: Noam Camus
> ---
> arch/arc/include/asm/smp.h |2 +-
> arch/arc/kernel/smp.c
On Tue, 2015-10-27 at 16:59 +0800, Liguo Zhang wrote:
> This series contain two patches, first is to optimize Mediatek I2C driver to
> use WRRD
> if hardware support auto restart. Because auto restart will issue auto restart
> interrupt, change to use WRRD can reduce interrupt latency. The second
On Saturday 31 October 2015 06:50 PM, Noam Camus wrote:
> From: Noam Camus
>
> External clock source can be used if included by one of
> DTS file of a chosen platform.
> Signed-off-by: Noam Camus
Acked-by: Vineet Gupta
> ---
> arch/arc/kernel/time.c |4
> 1 files changed, 4 insertion
Hi Sergey,
[Excess quoted for new cc's]
On Mon, 2 Nov 2015 14:58:16 +0900 Sergey Senozhatsky
wrote:
>
> unregister_trace_sched_switch/register_trace_prio_sched_switch/etc.
> (see the log below. 80-cols unfriendly. sorry.)
> expect proto to contain 'bool preempt'
>
> TRACE_EVENT(sched_switch,
>
On 10/30/2015 07:51 PM, Andrzej Hajda wrote:
On 10/06/2015 11:24 AM, Archit Taneja wrote:
A driver calling mipi_dsi_device_new might want to unregister the device
once it's done. It might also require it in an error handling path in
case something didn't go right.
When the dsi host driver cal
From: Vineet Gupta [mailto:vineet.gup...@synopsys.com]
Sent: Monday, November 02, 2015 8:24 AM
> For bisectability, please squash this with patch 4/20, and append the
> changelog of this patch to 4/20
OK
- Noam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
On Saturday 31 October 2015 06:49 PM, Noam Camus wrote:
> From: Noam Camus
>
> PGDIR_SIZE() cannot use "1UL" since it is called from mm/tlbex.S
> by VMALLOC_START. _BITUL() solves this build error.
>
> Signed-off-by: Noam Camus
> ---
> arch/arc/include/asm/pgtable.h |2 +-
> 1 files changed,
This patch adds supporting utility functions
for selftest. The intention is to share the self
test code between different drivers.
Supported test cases include:
1. dma_map_single
2. streaming DMA
3. coherent DMA
4. scatter-gather DMA
Signed-off-by: Sinan Kaya
---
drivers/dma/dmaengine.h | 2
This patch adds support for hidma engine. The driver
consists of two logical blocks. The DMA engine interface
and the low-level interface. The hardware only supports
memcpy/memset and this driver only support memcpy
interface. HW and driver doesn't support slave interface.
Signed-off-by: Sinan Kay
The Qualcomm Technologies HIDMA device has been designed
to support virtualization technology. The driver has been
divided into two to follow the hardware design. The management
driver is executed in hypervisor context and is the main
management entity for all channels provided by the device.
The c
On (11/02/15 15:40), Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20151101:
>
Hi,
unregister_trace_sched_switch/register_trace_prio_sched_switch/etc.
(see the log below. 80-cols unfriendly. sorry.)
expect proto to contain 'bool preempt'
TRACE_EVENT(sched_switch,
Hi, Shawn,
Could you help to review this patch? If it's ok, could you help to
merge it?
Thanks.
Best Regards,
Alison Wang
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: Thursday, October 29, 2015 9:11 PM
> To: Wang Huan-B18965
> Cc: Shawn
Hi Milo,
[auto build test ERROR on ljones-mfd/for-mfd-next -- if it's inappropriate
base, please suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Milo-Kim/Support-TI-LMU-devices/20151102-130804
config: mips-allyesconfig (attached as .config)
r
On 11/02/2015 12:49 PM, kbuild test robot wrote:
> Hi Bob,
>
> [auto build test ERROR on v4.3-rc7 -- if it's inappropriate base, please
> suggest rules for selecting the more suitable base]
>
> url:
> https://github.com/0day-ci/linux/commits/Bob-Liu/xen-block-multi-hardware-queues-rings-sup
My apologies for sending without no-chain-reply-to option.
So, I've resent the patch-set named 'PATCH RESEND 00/16 .. 16/16'.
Best regards,
Milo
On 11/2/2015 2:01 PM, Milo Kim wrote:
TI LMU(Lighting Management Unit) driver supports lighting devices below.
Enable pin Backlights HWMO
This patch describes overall binding for TI LMU MFD devices.
Cc: devicet...@vger.kernel.org
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo Kim
---
Documentation/devicetree/bindings/mfd/ti-lmu.txt | 282 +++
1 file changed, 282 insertions(+)
create mode 1
LM3633 LED device is one of TI LMU device list.
Cc: devicet...@vger.kernel.org
Cc: Jacek Anaszewski
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Cc: linux-l...@vger.kernel.org
Signed-off-by: Milo Kim
---
.../devicetree/bindings/leds/leds-lm3633.txt | 28 ++
1 file c
This binding supports LM3631 and LM3632 regulator configuration.
Cc: devicet...@vger.kernel.org
Cc: Lee Jones
Cc: Mark Brown
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo Kim
---
.../bindings/regulator/lm363x-regulator.txt| 28 ++
1 file changed, 28 insertion
LM3631 has 2 backlight strings and 11 bit dimming is supported.
PWM brightness control is also supported.
Common backlight driver is controlled by TI LMU backlight driver.
Only LM3631 specific code is implemented here.
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by:
LM3532 has 3 backlight strings and 8 bit dimming is supported.
PWM brightness control is also supported.
Common backlight driver is controlled by TI LMU backlight driver.
Only LM3532 specific code is implemented here.
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by:
On 10/30/2015 06:22 PM, Andrzej Hajda wrote:
On 10/06/2015 11:24 AM, Archit Taneja wrote:
We don't check whether a previously registered mipi_dsi_device under the
same host shares the same virtual channel.
Before registering, check if any of the registered devices doesn't
already have the sam
LM3633 has 3 backlight strings and 11 bit dimming is supported.
PWM brightness control is also supported.
LM3633 MFD has HWMON driver which monitors hardware fault detection.
After this monitoring is done, LM3633 backlight device should be
reinitialized. To enable this, 'hwmon_notifier_used' is se
This commit adds an example directory with a simple and verbose
Makefile, and some trivial example programs.
As always this could probably be improved but it's a start.
Signed-off-by: Michael Ellerman
---
Some folks at kernel summit expressed an interest in an example of how to add a
test case.
LM3633 LED driver supports generic LED functions and pattern generation.
Pattern is generated through the sysfs. ABI documentation is also added.
Device creation from device tree
LED channel name, LED string usage and max current settings are
configured inside
LM3632 has 2 backlight strings and 11 bit dimming is supported.
PWM brightness control is also supported.
Common backlight driver is controlled by TI LMU backlight driver.
Only LM3632 specific code is implemented here.
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by:
LM3697 has 3 backlight strings and 11 bit dimming is supported.
PWM brightness control is also supported.
LM3697 MFD has HWMON driver which monitors hardware fault detection.
After this monitoring is done, LM3697 backlight device should be
reinitialized. To enable this, 'hwmon_notifier_used' is se
LM363X regulator driver supports LM3631 and LM3632.
LM3631 has 5 regulators. LM3632 provides 3 regulators.
One boost output and LDOs are used for the display module.
Boost voltage is configurable but always on.
Supported operations for LDOs are enabled/disabled and voltage change.
Two LDOs of LM36
LM3695 has 2 backlight strings and 11 bit dimming is supported.
Common backlight driver is controlled by TI LMU backlight driver.
Only LM3695 specific code is implemented here.
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo Kim
---
drivers/video/backlight/Kc
LM3633 and LM3697 are TI LMU MFD device.
Those device have hardware monitoring feature which detects opened or
shorted circuit case.
Attributes
--
Two attributes are registered.
open_fault: check backlight output channel is opened or not
short_fault: check backlight output chann
Hardware fault monitoring driver is used in LM3633 and LM3697 device.
Just 'compatible' property is required to describe the driver.
Cc: devicet...@vger.kernel.org
Cc: Guenter Roeck
Cc: Jean Delvare
Cc: Lee Jones
Cc: lm-sens...@lm-sensors.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo
TI LMU(Lighting Management Unit) driver supports lighting devices below.
LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
LMU devices have common features.
- I2C interface for accessing device registers
- Hardware enable pin control
- Backlight brightness control
- Max current convers
On 10/30/2015 06:12 PM, Andrzej Hajda wrote:
On 10/06/2015 11:24 AM, Archit Taneja wrote:
Add a device name field in mipi_dsi_device. This name is different from
the actual dev name (which is of the format "hostname.reg"). When the
device is created via DT, this name is set to the modalias str
TI LMU backlight driver provides common driver features.
Chip specific configuration is handled by each backlight driver such like
LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
It supports common features as below.
- Backlight subsystem control
- Consistent device control flow
- Control
LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697 use common dt-bindings
for describing device.
Cc: devicet...@vger.kernel.org
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo Kim
---
.../bindings/video/backlight/ti-lmu-backlight.txt | 67 +
TI LMU(Lighting Management Unit) driver supports lighting devices below.
Enable pin Backlights HWMON LEDs Regulators
-- -- -
LM3532 o o x xx
LM3631 o o x x5 regulato
LM3633 LED device is one of TI LMU device list.
Cc: devicet...@vger.kernel.org
Cc: Jacek Anaszewski
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Cc: linux-l...@vger.kernel.org
Signed-off-by: Milo Kim
---
.../devicetree/bindings/leds/leds-lm3633.txt | 28 ++
1 file c
TI LMU backlight driver provides common driver features.
Chip specific configuration is handled by each backlight driver such like
LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
It supports common features as below.
- Backlight subsystem control
- Consistent device control flow
- Control
LM3532 has 3 backlight strings and 8 bit dimming is supported.
PWM brightness control is also supported.
Common backlight driver is controlled by TI LMU backlight driver.
Only LM3532 specific code is implemented here.
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by:
LM3632 has 2 backlight strings and 11 bit dimming is supported.
PWM brightness control is also supported.
Common backlight driver is controlled by TI LMU backlight driver.
Only LM3632 specific code is implemented here.
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by:
Hardware fault monitoring driver is used in LM3633 and LM3697 device.
Just 'compatible' property is required to describe the driver.
Cc: devicet...@vger.kernel.org
Cc: Guenter Roeck
Cc: Jean Delvare
Cc: Lee Jones
Cc: lm-sens...@lm-sensors.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo
LM3633 and LM3697 are TI LMU MFD device.
Those device have hardware monitoring feature which detects opened or
shorted circuit case.
Attributes
--
Two attributes are registered.
open_fault: check backlight output channel is opened or not
short_fault: check backlight output chann
TI LMU(Lighting Management Unit) driver supports lighting devices below.
LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
LMU devices have common features.
- I2C interface for accessing device registers
- Hardware enable pin control
- Backlight brightness control
- Max current convers
LM3633 has 3 backlight strings and 11 bit dimming is supported.
PWM brightness control is also supported.
LM3633 MFD has HWMON driver which monitors hardware fault detection.
After this monitoring is done, LM3633 backlight device should be
reinitialized. To enable this, 'hwmon_notifier_used' is se
LM3631 has 2 backlight strings and 11 bit dimming is supported.
PWM brightness control is also supported.
Common backlight driver is controlled by TI LMU backlight driver.
Only LM3631 specific code is implemented here.
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by:
LM3633 LED driver supports generic LED functions and pattern generation.
Pattern is generated through the sysfs. ABI documentation is also added.
Device creation from device tree
LED channel name, LED string usage and max current settings are
configured inside
LM363X regulator driver supports LM3631 and LM3632.
LM3631 has 5 regulators. LM3632 provides 3 regulators.
One boost output and LDOs are used for the display module.
Boost voltage is configurable but always on.
Supported operations for LDOs are enabled/disabled and voltage change.
Two LDOs of LM36
This patch describes overall binding for TI LMU MFD devices.
Cc: devicet...@vger.kernel.org
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo Kim
---
Documentation/devicetree/bindings/mfd/ti-lmu.txt | 282 +++
1 file changed, 282 insertions(+)
create mode 1
LM3697 has 3 backlight strings and 11 bit dimming is supported.
PWM brightness control is also supported.
LM3697 MFD has HWMON driver which monitors hardware fault detection.
After this monitoring is done, LM3697 backlight device should be
reinitialized. To enable this, 'hwmon_notifier_used' is se
LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697 use common dt-bindings
for describing device.
Cc: devicet...@vger.kernel.org
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo Kim
---
.../bindings/video/backlight/ti-lmu-backlight.txt | 67 +
This binding supports LM3631 and LM3632 regulator configuration.
Cc: devicet...@vger.kernel.org
Cc: Lee Jones
Cc: Mark Brown
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo Kim
---
.../bindings/regulator/lm363x-regulator.txt| 28 ++
1 file changed, 28 insertion
LM3695 has 2 backlight strings and 11 bit dimming is supported.
Common backlight driver is controlled by TI LMU backlight driver.
Only LM3695 specific code is implemented here.
Cc: Jingoo Han
Cc: Lee Jones
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo Kim
---
drivers/video/backlight/Kc
TI LMU(Lighting Management Unit) driver supports lighting devices below.
Enable pin Backlights HWMON LEDs Regulators
-- -- -
LM3532 o o x xx
LM3631 o o x x5 regulato
On Sat, Oct 31, 2015 at 03:42:46PM -0700, Guenter Roeck wrote:
> On 10/30/2015 02:56 AM, Huang Rui wrote:
> >This patch enables power1_input attribute for Carrizo platform.
> >
> >Signed-off-by: Huang Rui
> >Cc: Borislav Petkov
> >Cc: Guenter Roeck
> >Cc: Peter Zijlstra
> >Cc: Ingo Molnar
>
>
Update "implemention" as "implementation" because it generating warning
while test with scripts/checkpatch.pl.
Signed-off-by: Jitendra Kumar Khasdev
---
kernel/relay.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/relay.c b/kernel/relay.c
index 0b4570c..074efbc 10064
Hi Bob,
[auto build test ERROR on v4.3-rc7 -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Bob-Liu/xen-block-multi-hardware-queues-rings-support/20151102-122806
config: x86_64-allyesconfig (attached as .c
On Fri, Oct 30, 2015 at 06:33:42PM +0800, kbuild test robot wrote:
> Hi Huang,
>
> [auto build test WARNING on hwmon/hwmon-next -- if it's inappropriate base,
> please suggest rules for selecting the more suitable base]
>
> url:
> https://github.com/0day-ci/linux/commits/Huang-Rui/hwmon-fam1
Hi all,
Changes since 20151101:
The pci tree still had its build failure for which I disabled a driver.
The device-mapper tree lost its build failure.
The battery tree still had its build failure so I used the version from
next-20150925.
The iommu tree lost its build failure.
The mailbox
Before the dynamically allocated struct pages from devm_memremap_pages()
can be put to use outside the driver, we need a mechanism to track
whether they are still in use at teardown. Towards that goal reorder
the initialization sequence to allow the 'q_usage_counter' from the
request_queue to be u
The core has developed a need for a "pfn_t" type [1]. Move the existing
pfn_t in KVM to kvm_pfn_t [2].
[1]: https://lists.01.org/pipermail/linux-nvdimm/2015-September/002199.html
[2]: https://lists.01.org/pipermail/linux-nvdimm/2015-September/002218.html
Cc: Paolo Bonzini
Acked-by: Christoffer
The DAX implementation needs to protect new calls to ->direct_access()
and usage of its return value against unbind of the underlying block
device. Use blk_queue_enter()/blk_queue_exit() to either prevent
blk_cleanup_queue() from proceeding, or fail the dax_map_atomic() if the
request_queue is bei
Both, __dax_pmd_fault, and clear_pmem() were taking special steps to
clear memory a page at a time to take advantage of non-temporal
clear_page() implementations. However, x86_64 does not use
non-temporal instructions for clear_page(), and arch_clear_pmem() was
always incurring the cost of __arch_
dax_clear_blocks is currently performing a cond_resched() after every
PAGE_SIZE memset. We need not check so frequently, for example md-raid
only calls cond_resched() at stripe granularity. Also, in preparation
for introducing a dax_map_atomic() operation that temporarily pins a dax
mapping move
Similar to the file_inode() helper, provide a helper to lookup the inode for a
raw block device itself.
Cc: Al Viro
Suggested-by: Jan Kara
Reviewed-by: Jan Kara
Reviewed-by: Jeff Moyer
Signed-off-by: Dan Williams
---
fs/block_dev.c | 19 ---
1 file changed, 12 insertions(+)
This masking prevents access to the end of the device via dax_do_io(),
and is unnecessary as arch_add_memory() would have rejected an unaligned
allocation.
Cc:
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
drivers/nvdimm/pmem.c | 17 +++--
1 file changed, 3 insertions(+), 14 d
The core has developed a need for a "pfn_t" type [1]. Convert the usage
of pfn_t by usermode-linux to an unsigned long, and update pfn_to_phys()
to drop its expectation of a typed pfn.
[1]: https://lists.01.org/pipermail/linux-nvdimm/2015-September/002199.html
Cc: Dave Hansen
Cc: Jeff Dike
Cc:
For the normal (make_request) I/O path writes are always synchronously
flushed through to media. However, when DAX is in use it is possible
that userspace leaves dirty data in the cache. Ideally userspace uses
cache-writeback and persistent-commit instructions directly to flush
writes to media.
Now that we have the ability to dynamically enable DAX for a raw block
inode, make the behavior opt-in by default. DAX does not have feature
parity with pagecache backed mappings, so applications should knowingly
enable DAX semantics.
Note, this is only for mappings returned to userspace. For th
Before we allow ZONE_DEVICE pages to be put into active use outside of
the pmem driver, we need a mechanism to revoke access and assert they
are idle when the driver is shutdown. devm_memunmap_pages() checks that
the reference count passed in at devm_memremap_pages() time is dead, and
then uses zo
DAX-enabled block device drivers can use hints from fs/dax.c to
optimize their internal tracking of potentially dirty cpu cache lines.
If a DAX mapping is being used for synchronous operations, dax_do_io(),
a dax-enabled block-driver knows that fs/dax.c will handle immediate
flushing. For asynchro
1 - 100 of 368 matches
Mail list logo
