Commit-ID: a58e2ecd019d9ffb9f1813faf6151716fdecbae5
Gitweb: http://git.kernel.org/tip/a58e2ecd019d9ffb9f1813faf6151716fdecbae5
Author: Denys Vlasenko
AuthorDate: Sun, 20 Sep 2015 16:03:10 +0200
Committer: Ingo Molnar
CommitDate: Sun, 20 Sep 2015 16:19:01 +0200
x86/fpu/math-emu,
* Alex Snast wrote:
> What's the benefit of having that diverge check script as on every commit
> you'll
> either add the new stuff to tools/include/linux/rbtree.h or add an exception
> to
> that script as in rb_link_node_rcu case.
The benefit is that things do not diverge - diff or md5sum
> On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos wrote:
> > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots,
> > sometimes it fails to boot with looping errors and finally a watchdog
> > timeout. This console log from a failure. Config is below.
> >
[...]
> > [ 90.956986]
Ping!
-Original Message-
From: Bharat Kumar Gogada [mailto:bharat.kumar.gog...@xilinx.com]
Sent: Thursday, August 27, 2015 5:14 PM
To: robh...@kernel.org; pawel.m...@arm.com; mark.rutl...@arm.com;
ijc+devicet...@hellion.org.uk; ga...@codeaurora.org; Michal Simek; Soren
Brinkmann;
On 17/09/15 16:22, Javier Martinez Canillas wrote:
> Commit b483a4a5a711 ("ARM: OMAP4+: hwmod data: Don't prevent RESET of
> USB Host module") added the SYSC_HAS_RESET_STATUS flag to both OMAP4
> and OMAP5 USB host module hwmon sysconfig but that flag was already
> set for OMAP5. So now the flag
Dear Sebastian,
On Sun, 20 Sep 2015 21:32:37 +0200
Sebastian Hesselbarth wrote:
> On 19.09.2015 12:02, Jisheng Zhang wrote:
> > Add the pin-controller driver for Marvell Berlin BG4CT SoC, with definition
> > of its groups and functions. This uses the core Berlin pinctrl driver.
> >
> >
Around Mon 21 Sep 2015 12:09:01 +0530 or thereabout, Sudip Mukherjee wrote:
> On Mon, Sep 21, 2015 at 08:09:42AM +0200, Hans-Christian Egtvedt wrote:
>> Around Sat 19 Sep 2015 22:42:57 +0530 or thereabout, Sudip Mukherjee wrote:
>> > While building avr32 with allmodconfig, the build used to fail
On Mon, Sep 21, 2015 at 01:07:21PM +0600, Alexander Kuleshov wrote:
> Hello Greg,
>
> On Mon, Sep 21, 2015 at 8:25 AM, Greg Kroah-Hartman
> wrote:
> > On Mon, Aug 24, 2015 at 03:27:36PM +0300, Tomas Winkler wrote:
> >> From: "Signed-off-by: Alexander Kuleshov"
> >
> > I kind of doubt that's the
On Mon, Sep 21, 2015 at 3:26 PM, Meelis Roos wrote:
>> On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos wrote:
>> > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots,
>> > sometimes it fails to boot with looping errors and finally a watchdog
>> > timeout. This console log from a
On Fri, Sep 18, 2015 at 06:12:40PM +0100, e...@felipetonello.com wrote:
> From: "Felipe F. Tonello"
>
> _ep_queue() didn't check for errors when using add_td_to_list()
> which can fail if dma_pool_alloc fails, thus causing a kernel
Would you find the root cause why dma_pool_alloc fails?
>
locks_get_lock_context() uses cmpxchg() to install i_flctx.
cmpxchg() is a release operation which is correct. But it uses
a plain load to load i_flctx. This is incorrect. Subsequent loads
from i_flctx can hoist above the load of i_flctx pointer itself
and observe uninitialized garbage there. This
On Fri, Sep 18, 2015 at 06:12:41PM +0100, e...@felipetonello.com wrote:
> From: "Felipe F. Tonello"
>
> f_midi is not checking weather the is an error on usb_ep_queue
%s/weather/whether
%s/the/there
> request, ignoring potential problems, such as memory leaks.
>
> Signed-off-by: Felipe F.
On Sun, Sep 20, 2015 at 04:29:18AM -0700, tip-bot for Kees Cook wrote:
> Commit-ID: 3dc33bd30f3e1c1bcaaafa3482737694debf0f0b
> Gitweb: http://git.kernel.org/tip/3dc33bd30f3e1c1bcaaafa3482737694debf0f0b
> Author: Kees Cook
> AuthorDate: Wed, 12 Aug 2015 17:55:19 -0700
> Committer: Ingo
> /sbin/setpci -s $NAME 0x1a.b=0
> N=`find /sys/devices/pci:"$BUS"/"$NAME"/remove -name "remove"`
> echo $N
> echo -n 1 > "$N"
> sleep 1s
> done
> done
>
Thanks for the script!
>
>>
>> I will test next monday.
>
> Good. Please check current upstream and my
On Sat, Sep 19, 2015 at 06:26:23PM +0200, Michal Hocko wrote:
> On Fri 18-09-15 18:43:23, Vladimir Davydov wrote:
> [...]
> > Fixes: acc067d59a1f9 ("mm: make optimistic check for swapin readahead")
>
> This sha will not exist after the patch gets merged to the Linus tree
> from the Andrew tree.
> -Original Message-
> From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
> Sent: Monday, September 21, 2015 10:37
> To: Alexander Kuleshov
> Cc: Winkler, Tomas; Arnd Bergmann; Usyskin, Alexander; LKML
> Subject: Re: [char-misc 1/2] mei: Fix debugfs filename in error output
>
On (09/18/15 14:19), Joonsoo Kim wrote:
[..]
> + /*
> + * Prepare to use crypto decompress_noctx API. One tfm is required
> + * to initialize crypto algorithm properly and fetch corresponding
> + * function pointer. But, it is sharable for multiple concurrent
> + *
On Mon 21-09-15 14:10:39, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm-current tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> mm/vmscan.c: In function 'sane_reclaim':
> mm/vmscan.c:178:2: error: implicit declaration of function 'cgroup_on_dfl'
>
On Mon, Sep 21, 2015 at 02:10:39PM +1000, Stephen Rothwell wrote:
> After merging the akpm-current tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> mm/vmscan.c: In function 'sane_reclaim':
> mm/vmscan.c:178:2: error: implicit declaration of function 'cgroup_on_dfl'
>
From: Alexander Kuleshov
Signed-off-by: Alexander Kuleshov
Signed-off-by: Tomas Winkler
---
V2: fixed author address
drivers/misc/mei/debugfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/mei/debugfs.c b/drivers/misc/mei/debugfs.c
index
Commit-ID: 93f13a9f96771a064c716364aebc6e283b186eb8
Gitweb: http://git.kernel.org/tip/93f13a9f96771a064c716364aebc6e283b186eb8
Author: Borislav Petkov
AuthorDate: Mon, 21 Sep 2015 09:48:29 +0200
Committer: Ingo Molnar
CommitDate: Mon, 21 Sep 2015 09:56:59 +0200
x86/entry/vsyscall: Fix
On Mon, Sep 21, 2015 at 09:33:00AM +0200, Hans-Christian Egtvedt wrote:
> Around Mon 21 Sep 2015 12:09:01 +0530 or thereabout, Sudip Mukherjee wrote:
> > On Mon, Sep 21, 2015 at 08:09:42AM +0200, Hans-Christian Egtvedt wrote:
> >> Around Sat 19 Sep 2015 22:42:57 +0530 or thereabout, Sudip
Dave Hansen wrote:
> On 09/17/2015 11:09 PM, Greg Thelen wrote:
>> I'm not denying the issue, bug the WARNING splat isn't necessarily
>> catching a problem. The corresponding code comes from your debug patch:
>> +
>>
On Fri, Sep 18, 2015 at 06:58:21PM +0200, Luis de Bethencourt wrote:
> This platform driver has a OF device ID table but the OF module
> alias information is not created so module autoloading won't work.
>
> Signed-off-by: Luis de Bethencourt
> ---
>
>
> Hello,
>
> This patch adds the missing
rhashtable_rehash_one() uses plain writes to update entry->next,
while it is being concurrently accessed by readers.
Unfortunately, the compiler is within its rights to (for example) use
byte-at-a-time writes to update the pointer, which would fatally confuse
concurrent readers.
Use WRITE_ONCE to
On Sun, Sep 20, 2015 at 08:13:48PM +0200, Sebastian Hesselbarth wrote:
> On 17.09.2015 12:13, Antoine Tenart wrote:
> >Add a PWM controller driver for the Marvell Berlin SoCs. This PWM
> >controller has 4 channels.
> >
> >Signed-off-by: Antoine Tenart
> >Acked-by: Sebastian Hesselbarth
>
>
> -Original Message-
> From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
> Sent: Monday, September 21, 2015 05:25
> To: Prarit Bhargava
> Cc: linux-kernel@vger.kernel.org; Winkler, Tomas; Joe Perches; David S.
> Miller; Jiri
> Kosina; Sharon Dvir; Suthikulpanit, Suravee;
On Thu, Sep 17, 2015 at 12:13:05PM +0200, Antoine Tenart wrote:
> Following the addition of a Berlin PWM driver, this patch adds the
> corresponding documentation.
>
> Signed-off-by: Antoine Tenart
> Acked-by: Sebastian Hesselbarth
> ---
> Documentation/devicetree/bindings/pwm/pwm-berlin.txt |
Hi Chen,
On Mon, Sep 21, 2015 at 7:30 AM, Peter Chen wrote:
> On Fri, Sep 18, 2015 at 06:12:41PM +0100, e...@felipetonello.com wrote:
>> From: "Felipe F. Tonello"
>>
>> f_midi is not checking weather the is an error on usb_ep_queue
>
> %s/weather/whether
> %s/the/there
I fixed it on v3. Did
On Wed, Sep 16, 2015 at 6:40 PM, wrote:
> From: "Felipe F. Tonello"
>
> This fixes a duplicated pin control causing this error:
>
> imx6q-pinctrl 20e.iomuxc: pin MX6Q_PAD_GPIO_1 already
> requested by regulators:regulator@2; cannot claim for 2184000.usb
> imx6q-pinctrl 20e.iomuxc:
On 09/20/2015 09:18 PM, Jonathan Cameron wrote:
> On 14/09/15 17:08, Vaishali Thakkar wrote:
>> Use resourced managed function devm_iio_device_register to
>> make error path simpler. To be compatible with the change,
>> the remove function is removed as it is now redundant.
>>
>> Signed-off-by:
Hi David,
Applied both patches.
Thanks,
Miklos
--
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/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 21/09/15 08:29, Fu, Zhonghui wrote:
>
>
> On 2015/8/24 15:07, Fu, Zhonghui wrote:
>>
>> On 2015/8/17 14:48, Adrian Hunter wrote:
>>> On 17/08/15 06:26, Fu, Zhonghui wrote:
Hi,
Any comments are welcome.
Thanks,
Zhonghui
On 2015/7/30 15:40, Fu,
From: Santosh Shilimkar
> Sent: 20 September 2015 00:05
> Even with per bucket locking scheme, in a massive parallel
> system with active rds sockets which could be in excess of multiple
> of 10K, rds_bin_lookup() workload is siginificant because of smaller
> hashtable size.
>
> With some tests,
On Sat, Sep 19, 2015 at 10:27:15AM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.89 release.
> There are 20 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Monday 14 September 2015 16:26:07 Andrew F. Davis wrote:
> The MODULE_DEVICE_TABLE macro automatically adds all needed
> i2c MODULE_ALIASes so remove the extra MODULE_ALIAS.
>
> Signed-off-by: Andrew F. Davis
Acked-by: Pali Rohár
> ---
> drivers/power/bq27x00_battery.c | 4
> 1 file
On Monday 14 September 2015 16:26:12 Andrew F. Davis wrote:
> Reorganize the logic checking battery health and add under temperature
> condition checking.
>
> Signed-off-by: Andrew F. Davis
Acked-by: Pali Rohár
> ---
> drivers/power/bq27xxx_battery.c | 64
>
> -Original Message-
> From: Wood Scott-B07421
> Sent: Sunday, September 20, 2015 5:45 AM
> To: Aggrwal Poonam-B10812
> Cc: linuxppc-...@lists.ozlabs.org; linux-kernel@vger.kernel.org; devicetree-
> disc...@lists.ozlabs.org
> Subject: Re: [PATCH 2/4] powerpc/device-tree: bindings for
On Monday 14 September 2015 16:26:10 Andrew F. Davis wrote:
> Fix typos and change "relative state of charge" to "state of charge" as not
> all supported devices use relative state of charge.
>
> Signed-off-by: Andrew F. Davis
Acked-by: Pali Rohár
> ---
> drivers/power/bq27xxx_battery.c | 28
On 09/18/2015 11:11 PM, Cormier, Jonathan wrote:
> diff --git a/sound/soc/codecs/tlv320aic26.c b/sound/soc/codecs/tlv320aic26.c
> index 620ab9ea1ef0..91fdd96648bd 100644
> --- a/sound/soc/codecs/tlv320aic26.c
> +++ b/sound/soc/codecs/tlv320aic26.c
> @@ -370,10 +370,20 @@ static int
On Thu, Sep 17, 2015 at 12:13:04PM +0200, Antoine Tenart wrote:
> Add a PWM controller driver for the Marvell Berlin SoCs. This PWM
> controller has 4 channels.
>
> Signed-off-by: Antoine Tenart
> Acked-by: Sebastian Hesselbarth
> ---
> drivers/pwm/Kconfig | 9 ++
> drivers/pwm/Makefile
On Monday 14 September 2015 16:26:09 Andrew F. Davis wrote:
> When initialized as a platform device the initializer must now specify
> a device. An empty device name is no longer valid.
>
> Signed-off-by: Andrew F. Davis
> ---
> drivers/power/bq27xxx_battery.c | 9 ++---
>
On 21/09/15 11:15, Adrian Hunter wrote:
> On 21/09/15 08:29, Fu, Zhonghui wrote:
>>
>>
>> On 2015/8/24 15:07, Fu, Zhonghui wrote:
>>>
>>> On 2015/8/17 14:48, Adrian Hunter wrote:
On 17/08/15 06:26, Fu, Zhonghui wrote:
> Hi,
>
> Any comments are welcome.
>
>
> Thanks,
On Monday 14 September 2015 16:26:11 Andrew F. Davis wrote:
> Add support for additional devices and register equivalent family devices
> including the bq27010, bq27210, bq27500, bq27510, bq27520, bq27530,
> bq27531, bq27541, bq27542, bq27546, bq27545, bq27441, bq27421, and the
> bq27641.
>
> To
From: Alexander Usyskin
Use || instead && in state check.
The latter is bogus and leads to following warning:
drivers/misc/mei/hbm.c:1212:46: warning: logical ‘and’ of mutually exclusive
tests is always false [-Wlogical-op]
Fixes: 70ef835c84b3 ("mei: support for dynamic clients")
Reported-by:
* Andy Lutomirski wrote:
> On Sep 20, 2015 5:15 PM, "Linus Torvalds"
> wrote:
> >
> > On Sun, Sep 20, 2015 at 5:02 PM, Andy Lutomirski wrote:
> > > This demotes an OOPS and likely panic due to a failed non-"safe" MSR
> > > access to a WARN_ON_ONCE and a return of zero (in the RDMSR case).
>
On Sat, Sep 19, 2015 at 01:07:56AM +0200, Rafael J. Wysocki wrote:
> On Fri, Sep 18, 2015 at 5:55 PM, Thierry Reding
> wrote:
[...]
> > Of course there's still the matter of some types of devices physically
> > disappearing (USB, PCI, ...).
>
> Right. In some cases removal is simply necessary
Hi Eduardo, Rui,
On Mon, Sep 14, 2015 at 04:55:01AM +0100, Eduardo Valentin wrote:
> Hello Rui,
>
> (apologize for duplicates, now copying the mailing lists)
>
> Please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
> fixes
>
> to receive Thermal-SoC
Hi Paolo & Alex,
I find that there is a build error in the following two cases:
- KVM is configured as 'M' and VFIO as 'Y'
The reason is the build of irqbypass manager is triggered in
arch/x86/kvm/Makefile, and VFIO is built before KVM, hence
it cannot find the symbols in irqbypass manager.
-
I'm announcing the release of the 3.4.109 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
Hi,
I've just built and booted 4.3.0-rc2 and I'm seeing the following new messages
on the console during boot up:
[2.481399] EXT4-fs (sda2): couldn't mount as ext3 due to feature
incompatibilities
[2.482426] EXT4-fs (sda2): couldn't mount as ext2 due to feature
incompatibilities
They
Force threading of interrupts does not really deal with interrupts
which are requested with a primary and a threaded handler. The current
policy is to leave them alone and let the primary handler run in
interrupt context, but we set the ONESHOT flag for those interrupts as
well.
Kohji Okuno
On Thu, Sep 17, 2015 at 12:38:25PM +0200, Peter Zijlstra wrote:
> On Fri, Sep 11, 2015 at 06:22:47PM +0100, Morten Rasmussen wrote:
>
> > While at it, should I include Yuyang's patch redefining the SCALE/SHIFT
> > mess?
>
> I suspect his patch will fail to compile on ARM which uses
>
On Sun, 20 Sep 2015, Marc Zyngier wrote:
> > Uff... in one of earliest reviews i was asked to add lock..
> > I also was asked to add asm9260 to some existing driver. Not sure if it
> > is still making sense.
>
> Adding or removing a lock is not about what people ask you to do. It is
> about
2015-09-19 19:56 GMT+02:00 Mark Brown :
> On Fri, Sep 18, 2015 at 02:38:27PM +0200, Jean-Michel Hautbois wrote:
>> Hi,
>>
>> I am wondering why in spi-imx the spi_imx_pio_transfer() function is
>> calling wait_for_completion() and not wait_for_completion_timeout() as
>> in the
Since the commit to have an allocated list of virtual descriptors was
reverted, the pxa_dma driver is broken, as it assumes the descriptor is
placed on the allocated list upon allocation.
Fix the issue in pxa_dma by making an allocated virtual descriptor a
singleton.
Fixes: 8c8fe97b2b8a ("Revert
Move all pointer-formatting documentation to one place instead of
keeping it in three places with different level of completeness.
Signed-off-by: Martin Kletzander
---
Documentation/printk-formats.txt | 27 +
lib/vsprintf.c | 123
On Mon, Sep 21, 2015 at 04:45:44PM +0800, Yakir Yang wrote:
> Hi Heiko,
>
> On 09/02/2015 10:15 AM, Yakir Yang wrote:
> >Hi Heiko,
> >
> >在 09/02/2015 05:47 AM, Heiko Stuebner 写道:
> >>Hi Yakir,
> >>
> >>Am Dienstag, 1. September 2015, 13:46:11 schrieb Yakir Yang:
> >>>The Samsung Exynos eDP
On Mon, Sep 21, 2015 at 09:16:05AM +0100, Felipe Tonello wrote:
> Hi Chen,
>
> On Mon, Sep 21, 2015 at 7:30 AM, Peter Chen wrote:
> > On Fri, Sep 18, 2015 at 06:12:41PM +0100, e...@felipetonello.com wrote:
> >> From: "Felipe F. Tonello"
> >>
> >> f_midi is not checking weather the is an error
Hi Peter,
On Mon, Sep 21, 2015 at 7:29 AM, Peter Chen wrote:
> On Fri, Sep 18, 2015 at 06:12:40PM +0100, e...@felipetonello.com wrote:
>> From: "Felipe F. Tonello"
>>
>> _ep_queue() didn't check for errors when using add_td_to_list()
>> which can fail if dma_pool_alloc fails, thus causing a
Hi Peter,
On Mon, Sep 21, 2015 at 8:49 AM, Peter Chen wrote:
> On Mon, Sep 21, 2015 at 09:16:05AM +0100, Felipe Tonello wrote:
>> Hi Chen,
>>
>> On Mon, Sep 21, 2015 at 7:30 AM, Peter Chen wrote:
>> > On Fri, Sep 18, 2015 at 06:12:41PM +0100, e...@felipetonello.com wrote:
>> >> From: "Felipe F.
On Mon, 2015-09-21 at 11:13 +0200, Martin Kletzander wrote:
> Move all pointer-formatting documentation to one place instead of
> keeping it in three places with different level of completeness.
>
I think we still need at least one in the code. I, for example, often
read it from the actual
Hi Balbi,
On Fri, Sep 18, 2015 at 6:36 PM, wrote:
> From: "Felipe F. Tonello"
>
> f_midi is not checking whether there is an error on usb_ep_queue
> request, ignoring potential problems, such as memory leaks.
>
> Signed-off-by: Felipe F. Tonello
> ---
>
> Changes for v2:
> - Update code
On Fri, 18 Sep 2015 14:41:20 -0700
"Paul E. McKenney" wrote:
> On Tue, Sep 15, 2015 at 10:09:41AM -0700, Paul E. McKenney wrote:
> > On Tue, Sep 15, 2015 at 06:30:28PM +0200, Peter Zijlstra wrote:
> > > On Tue, Sep 15, 2015 at 08:34:48AM -0700, Paul E. McKenney wrote:
> > > > On Tue, Sep 15,
On Sat 19-09-15 08:17:14, Dave Chinner wrote:
> On Thu, Sep 17, 2015 at 11:04:03PM -0700, Linus Torvalds wrote:
> > On Thu, Sep 17, 2015 at 10:40 PM, Dave Chinner wrote:
> > > PS: just hit another "did this just get broken in 4.3-rc1" issue - I
> > > can't run blktrace while there's a IO load
On Sat, Sep 19, 2015 at 05:44:37PM +0900, Jungseok Lee wrote:
> On Sep 19, 2015, at 12:31 AM, Catalin Marinas wrote:
> > On Fri, Sep 18, 2015 at 04:03:02PM +0100, Catalin Marinas wrote:
> >> On Fri, Sep 18, 2015 at 09:57:56PM +0900, Jungseok Lee wrote:
> >>> On Sep 18, 2015, at 1:21 AM, Catalin
On 21/09/2015 10:56, Wu, Feng wrote:
> Hi Paolo & Alex,
>
> I find that there is a build error in the following two cases:
> - KVM is configured as 'M' and VFIO as 'Y'
> The reason is the build of irqbypass manager is triggered in
> arch/x86/kvm/Makefile, and VFIO is built before KVM, hence
>
When requested by a user, the PWM is assigned a default period and polarity
extracted from the DT, the platform data or statically set by the driver.
Those default values are currently stored in the period and polarity
fields of the pwm_device struct, but they will be stored somewhere else
once we
The PWM state, represented by its period, duty_cycle and polarity,
is currently directly stored in the PWM device.
Declare a pwm_state structure embedding those field so that we can later
use this struct to atomically update all the PWM parameters at once.
Signed-off-by: Boris Brezillon
---
From: Heiko Stübner
The pwm-states make it possible to also output the polarity, duty cycle
and period information in the debugfs pwm summary-outout.
This makes it easier to gather overview information about pwms without
needing to walk through the sysfs attributes of every pwm.
Signed-off-by:
Implement the ->enable(), ->disable() and ->is_enabled methods and remove
the PWM call in ->set_voltage_sel().
This is particularly important for critical regulators tagged as always-on,
because not claiming the PWM (and its dependencies) might lead to
unpredictable behavior (like a system hang
Implement the ->apply() function to add support for atomic update.
Signed-off-by: Boris Brezillon
---
drivers/pwm/pwm-rockchip.c | 53 +-
1 file changed, 29 insertions(+), 24 deletions(-)
diff --git a/drivers/pwm/pwm-rockchip.c
The ->state field is currently initialized to 0, thus referencing the
voltage selector at index 0, which might not reflect the current voltage
value.
If possible, retrieve the current voltage selector from the PWM state, else
return -EINVAL.
Signed-off-by: Boris Brezillon
---
On 2015/9/19 0:18, Ross Zwisler wrote:
On Fri, Sep 18, 2015 at 03:46:30PM +0800, Lin Yongting wrote:
In embed devices, user space applications will use reserved memory
(i.e. persistent memory) to store business data, the data is kept
in this memory region after system rebooting or panic.
Implement the ->reset_state() function to expose initial state.
Signed-off-by: Boris Brezillon
---
drivers/pwm/pwm-rockchip.c | 66 ++
1 file changed, 66 insertions(+)
diff --git a/drivers/pwm/pwm-rockchip.c b/drivers/pwm/pwm-rockchip.c
index
On 2015/9/19 0:41, Dan Williams wrote:
On Fri, Sep 18, 2015 at 9:18 AM, Ross Zwisler
wrote:
On Fri, Sep 18, 2015 at 03:46:30PM +0800, Lin Yongting wrote:
In embed devices, user space applications will use reserved memory
(i.e. persistent memory) to store business data, the data is kept
in
Add a ->reset_state() function to the pwm_ops struct to let PWM drivers
initialize the PWM state attached to a PWM device.
Signed-off-by: Boris Brezillon
---
drivers/pwm/core.c | 3 +++
include/linux/pwm.h | 4
2 files changed, 7 insertions(+)
diff --git a/drivers/pwm/core.c
On Mon, 2015-09-21 at 14:51 +0800, Fu, Zhonghui wrote:
> Now, PM core supports asynchronous suspend/resume mode for devices
> during system suspend/resume, and the power state transition of one
> device may be completed in separate kernel thread. PM core ensures
> all power state transition timing
Prepare the addition of the PWM initial state retrieval by adding a default
state where all the parameters retrieved from DT, platform data or
statically forced by the hardware will be stored.
Once done we will be able to store the initial state in the ->state field
without risking to loose the
Prepare the transition to PWM atomic update by moving the enabled/disabled
state into the pwm_state struct. This way we can easily update the whole
PWM state by copying the new state in the ->state field.
Signed-off-by: Boris Brezillon
---
drivers/pwm/core.c | 15 ---
The PWM period will be set when calling pwm_config. Remove this useless
call to pwm_set_period, which might mess up with the initial PWM state
once we have added proper support for PWM init state retrieval.
Signed-off-by: Boris Brezillon
---
drivers/video/backlight/pwm_bl.c | 8 +---
1 file
Add an ->apply() method to the pwm_ops struct to allow PWM drivers to
implement atomic update.
This method will be preferred over the ->enable(), ->disable() and
->config() methods if available.
Add the pwm_get_state(), pwm_get_default_state() and pwm_apply_state()
functions for PWM users to be
Hello,
This series adds support for atomic PWM update, or IOW, the capability
to update all the parameters of a PWM device (enabled/disabled, period,
duty and polarity) in one go.
Best Regards,
Boris
Changes since v2:
- rebased on top of 4.3-rc2
- reintroduced pwm-regulator patches
Changes
From: Dave Airlie
This is enough to enable DRI3.
Signed-off-by: Dave Airlie
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/Makefile| 2 +-
drivers/gpu/drm/virtio/virtgpu_drv.c | 13 +-
drivers/gpu/drm/virtio/virtgpu_drv.h | 12 ++
From: Dave Airlie
Also add DRM_RENDER_ALLOW to the ioctls.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_drv.c | 2 +-
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 18 +-
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git
Add helper function to handle the submission of fenced control requests.
Make sure we initialize the fence while holding the virtqueue lock, so
requests can't be reordered.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_fence.c | 2 +-
drivers/gpu/drm/virtio/virtgpu_vq.c|
Add the bits needed for opengl rendering support: query
capabilities, new virtio commands, drm ioctls.
Signed-off-by: Dave Airlie
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/Makefile| 3 +-
drivers/gpu/drm/virtio/virtgpu_drv.c | 10 +
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_display.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c
b/drivers/gpu/drm/virtio/virtgpu_display.c
index 4e160ef..97e5274 100644
--- a/drivers/gpu/drm/virtio/virtgpu_display.c
+++
Add virtio_gpu_queue_ctrl_buffer_locked function, which does the same as
virtio_gpu_queue_ctrl_buffer but does not take the virtqueue lock. The
caller must hold the lock instead.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_vq.c | 17 +
1 file changed, 13
On Wed, Sep 16, 2015 at 01:41:38PM -0700, Douglas Anderson wrote:
> There's a member in 'struct dw_hdmi' called cable_plugin. It's never
> set to anything anywhere so thus is always false. There's a bit of code
> checking it, but since it's always false this must be dead code.
> Eliminate it.
>
On 21 September 2015 09:18:39 BST, Karol Wrona wrote:
>On 09/20/2015 09:18 PM, Jonathan Cameron wrote:
>> On 14/09/15 17:08, Vaishali Thakkar wrote:
>>> Use resourced managed function devm_iio_device_register to
>>> make error path simpler. To be compatible with the change,
>>> the remove
The goal of this patch is to reproduce on kdbus the same behavior
that is expressed by Unix Domain Sockets when it comes to restricting
ability to pass opened file descriptors.
Signed-off-by: Paul Osmialowski
---
ipc/kdbus/message.c | 31 ++-
1 file changed, 22
On 16/09/15 18:54, Gwendal Grignou wrote:
[snip]
>> +static int mmc_blk_ioctl_multi_cmd(struct block_device *bdev,
>> + struct mmc_ioc_multi_cmd __user *user)
>> +{
>> + struct mmc_blk_ioc_data **idata = NULL;
>> + struct mmc_ioc_cmd __user *cmds =
Hello,
We are working on a data race detector for kernel, KernelThreadSanitizer (KTSAN.
I am getting the following reports (on 4.2 rc2) between
__scsi_init_queue and ata_sg_setup. The reports suggest that
dev->dma_parms->max_segment_size is being used before it is
initialized. I would expect that
Add 1GHz 64-bit Numachip2 clocksource timer support for accurate
system-wide timekeeping, as core TSCs are unsynchronised.
Additionally, add a per-core clockevent mechanism that interrupts via the
platform IPI vector after a programmed period.
v2: Fix whitespace and wrapping issue
I got a report about unkillable task eating CPU. Thge further
investigation shows, that the problem is in the fuse_fill_write_pages()
function. If iov's first segment has zero length, we get an infinite
loop, because we never reach iov_iter_advance() call.
Fix this by calling iov_iter_advance()
Here is another data race in add_disk, maybe it is related.
ThreadSanitizer: data-race in sysfs_create_dir_ns
Write at 0x88048374eca8 of size 8 by thread 829 on CPU 4:
[] sysfs_create_dir_ns+0x7b/0xd0 fs/sysfs/dir.c:63
[< inline >] create_dir lib/kobject.c:71
[]
Add berlin4ct to existing berlin pinctrl device tree binding.
Signed-off-by: Jisheng Zhang
---
Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt
Add the avio, soc, sm pinctrl nodes for Marvell berlin4ct SoC.
Signed-off-by: Jisheng Zhang
---
arch/arm64/boot/dts/marvell/berlin4ct.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/marvell/berlin4ct.dtsi
This series adds support for Marvell berlin4ct pin-controller, allowing
to configure the pin muxing from the device tree.
Since v1:
- use generic name for pin functions
- a new commit to add pinmux for uart0
- correct pinctrl usage in dts
Jisheng Zhang (6):
pinctrl: berlin: regmap as an
901 - 1000 of 1754 matches
Mail list logo
