On Tue, Jun 19, 2018 at 08:47:33PM +0200, Maciej S. Szmigiero wrote:
> Integrating verify_patch_size() into verify_patch() allows us to check
> whether the indicated patch size makes sense for its indicated CPU family -
> for all CPU families known to the driver.
>
> If we spot a patch that is
On Thu, Jun 21, 2018 at 5:25 PM Huang, Ying wrote:
> Do you have interest in some other comparison?
No, I think the overhead of the strong stackprotector is a bit sad,
but I assume it's because of the nasty code to load the stack canary
from a cacheline that has absolutely nothing else in it.
Hi Will, Wei,
On 20/06/18 17:25, Wei Xu wrote:
> On 2018/6/20 23:54, James Morse wrote:
> I have disabled CONFIG_ARM64_RAS_EXTN and reverted that commit.
> But I still got the stack overflow issue sometimes.
> Do you have more hint?
> The log is as below:
> [ 0.00] Booting Linux on
From: Russ Dill
SoCs like AM43XX lose clock registers context during RTC-only
suspend. Hence add functions to save/restore the clock registers
context.
Signed-off-by: Keerthy
Signed-off-by: Russ Dill
---
Changes in v2:
* Replaced clk_dflt_restore instances to
On Thu, Jun 21, 2018 at 3:17 AM, Ming Lei wrote:
> On Fri, Jun 15, 2018 at 02:59:19PM +0200, Gi-Oh Kim wrote:
>> >
>> > - bio size can be increased and it should improve some high-bandwidth IO
>> > case in theory[4].
>> >
>>
>> Hi,
>>
>> I would like to report your patch set works well on my
Hi Dmitry,
I think I can answer some of your questions (not all).
cc'ing the new Thierry's address and Gwendal.
On 21/06/18 01:05, Dmitry Torokhov wrote:
> On Mon, Nov 20, 2017 at 8:18 AM Thierry Escande
> wrote:
>>
>> The cros_ec_dev module is responsible for registering the MFD devices
>>
Hi!
> As security becomes more and more important, we add the in-kernel
> encryption support for hibernation.
...
> There was a discussion on the mailing list on whether this key should
> be derived in kernel or in user space. And it turns out to be generating
> the key by user space is more
Hi guys,
On 21/06/18 07:39, Ard Biesheuvel wrote:
> On 21 June 2018 at 04:51, Jun Yao wrote:
>> On Wed, Jun 20, 2018 at 12:09:49PM +0200, Ard Biesheuvel wrote:
>>> On 20 June 2018 at 10:57, Jun Yao wrote:
Move {idmap_pg_dir,tramp_pg_dir,swapper_pg_dir} to .rodata
section. And update
On 21/06/18 09:38, James Morse wrote:
>> (joyx@Turing-Arch-b) (gcc version 4.9.1 20140505 (prerelease) (crosstool-NG
>> linaro-1.13.1-4.9-2014.05 - Linaro GCC 4.9-2014.05)) #10 SMP PREEMPT Wed Jun
>> 20
>> 23:59:05 CST 2018
>
>> [ 0.00] CPU0: using LPI pending table
On Wed 2018-06-20 17:40:51, Chen Yu wrote:
> crypto_hibernate is a user-space utility to generate
> 512bits AES key and pass it to the kernel via ioctl
> for hibernation encryption.(We can also add the key
> into kernel via keyctl if necessary, but currently
> using ioctl seems to be more
From: Ludovic Barre
This patch adds compatible data to manage pclk clock by
compatible. Adds stm32mp1 support which requires pclk clock.
Signed-off-by: Ludovic Barre
---
drivers/watchdog/stm32_iwdg.c | 116 +++---
1 file changed, 74 insertions(+), 42
From: Ludovic Barre
This patch series updates stm32_iwdg driver to manage pclk
clock by compatible. stm32mp1 requires a pclk clock.
v4:
-dt-bindings: split and review
v3:
-remove stm32_iwdg_config structure, just assign the
boolean directly to .dat
Ludovic Barre (4):
dt-bindings: watchdog:
From: Ludovic Barre
This patch adds independent watchdog support for stm32mp157c.
Signed-off-by: Ludovic Barre
---
arch/arm/boot/dts/stm32mp157c.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi
b/arch/arm/boot/dts/stm32mp157c.dtsi
index
From: Ludovic Barre
This patch adds support of stm32mp1.
stm32mp1 requires 2 clocks lsi and pclk.
Signed-off-by: Ludovic Barre
---
.../devicetree/bindings/watchdog/st,stm32-iwdg.txt | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git
From: Ludovic Barre
This patch activates independent watchdog support for
stm32mp157c board.
Signed-off-by: Ludovic Barre
---
arch/arm/boot/dts/stm32mp157c-ed1.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c-ed1.dts
On Wed, Jun 20, 2018 at 10:32:43PM +0530, Srikar Dronamraju wrote:
> task_numa_compare() helps choose the best cpu to move or swap the
> selected task. To achieve this task_numa_compare() is called for every
> cpu in the node. Currently it evaluates if the task can be moved/swapped
> for each of
On Wed, Jun 20, 2018 at 10:32:45PM +0530, Srikar Dronamraju wrote:
> Currently preferred node is set to dst_nid which is the last node in the
> iteration whose group weight or task weight is greater than the current
> node. However it doesn't guarantee that dst_nid has the numa capacity
> to move.
Hi Kyuho,
Comment inline.
Thanks,
Sayali
-Original Message-
From: Kyuho Choi [mailto:chlrb...@gmail.com]
Sent: Friday, June 15, 2018 8:28 AM
To: Sayali Lokhande
Cc: subha...@codeaurora.org; c...@codeaurora.org; vivek.gau...@codeaurora.org;
rna...@codeaurora.org;
Please reply me back I have something to tell you, I am Sgt.Sherri,
On Thu, Jun 21, 2018 at 09:38:53AM +0100, James Morse wrote:
> On 20/06/18 17:25, Wei Xu wrote:
> > [ 0.042421] Insufficient stack space to handle exception!
> > [ 0.042423] ESR: 0x9646 -- DABT (current EL)
> > [ 0.043730] FAR: 0x093a80e0
> > [ 0.044714]
On 20/06/18 13:20, Mikko Perttunen wrote:
> The Tegra Combined UART (TCU) is a mailbox-based mechanism that allows
> multiplexing multiple "virtual UARTs" into a single hardware serial
> port. The TCU is the primary serial port on Tegra194 devices.
>
> Add a TCU driver utilizing the mailbox
Hi James,
On 2018/6/21 9:38, James Morse wrote:
> Hi Will, Wei,
>
> On 20/06/18 17:25, Wei Xu wrote:
>> On 2018/6/20 23:54, James Morse wrote:
>> I have disabled CONFIG_ARM64_RAS_EXTN and reverted that commit.
>> But I still got the stack overflow issue sometimes.
>> Do you have more hint?
>
>>
On Wed, Jun 20, 2018 at 07:25:19PM +0200, Jirka Hladky wrote:
> Hi Mel and others,
>
> I would like to let you know that I have tested following patch
>
Understood. FWIW, there is a lot in flight at the moment but the first
likely patch is removing rate limiting entirely and see what falls out.
On Thu 21-06-18 09:45:37, Michal Hocko wrote:
> On Wed 20-06-18 13:34:52, David Rientjes wrote:
> > On Wed, 20 Jun 2018, Michal Hocko wrote:
[...]
> > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > > index 6bcecc325e7e..ac08f5d711be 100644
> > > --- a/arch/x86/kvm/x86.c
> > > +++
+Rafael
On 20/06/18 18:30, Samuel Morris wrote:
> On Wed, Jun 20, 2018 at 8:58 AM, Roger Quadros wrote:
>> Tony,
>>
>> On 20/06/18 13:29, Tony Lindgren wrote:
>>> Hi,
>>>
>>> * Naresh Kamboju [180620 05:55]:
Linux next (4.18.0-rc1-next-20180619) boot failed on beagle board x15.
>>>
>>>
Hi Enric,
On 2018년 06월 20일 19:32, Enric Balletbo i Serra wrote:
> Hi Chanwoo,
>
> On 20/06/18 02:47, Chanwoo Choi wrote:
>> Hi Enric,
>>
>> On 2018년 06월 19일 17:22, Enric Balletbo i Serra wrote:
>>> Hi Chanwoo,
>>>
>>> On 18/06/18 11:02, Enric Balletbo Serra wrote:
Hi Chanwoo,
Missatge
On Thu, Jun 21, 2018 at 3:06 AM, Andy Shevchenko
wrote:
> On Wed, Jun 20, 2018 at 3:55 PM, Dmitry Vyukov wrote:
>> From: Dmitry Vyukov
>>
>> KERN_CONT leads to split lines in kernel output
>> and complicates useful changes to printk like
>> printing context before each line.
>>
>> Only
This implements oversampling support for the SAMA5d2 ADC device.
Enabling oversampling : OSR can improve resolution from 12 bits to
13 or 14 bits.
Changing the channel specification to have 14 bits, and we shift the value
1 bit to the left if we have oversampling for just one extra bit, and two
On 20/06/18 13:20, Mikko Perttunen wrote:
> HSP interrupts can be routed through exposed "shared interrupts". These
> interrupts can be mapped to various internal interrupt lines. Add
> interrupt properties for shared interrupts to the tegra186-hsp device
> tree bindings. At the same time, add
Hi Chanwoo,
Missatge de Chanwoo Choi del dia dj., 21 de
juny 2018 a les 9:58:
>
> Hi Enric,
>
> On 2018년 06월 20일 19:32, Enric Balletbo i Serra wrote:
> > Hi Chanwoo,
> >
> > On 20/06/18 02:47, Chanwoo Choi wrote:
> >> Hi Enric,
> >>
> >> On 2018년 06월 19일 17:22, Enric Balletbo i Serra wrote:
> >>>
perf stat command line flag -T to display transaction counters is
currently supported for x86 only.
Add support for s390. It is based on the metrics flag -M transaction
using the architecture dependend json files This requires a metric
named transaction in the json files for the platform.
As
This reverts commit 038586c34301578e538f6c5aa79ca82bce1b9152.
Fix the support of detailed/verbose PMU event description
by using the "Unit": keyword in the json files to address
event names refering to the /sys/devices/cpum_[cs]f
devices.
Signed-off-by: Thomas Richter
Reviewed-by: Hendrik
Correct the support of detailed/verbose PMU event description
by using the "Unit": keyword in the json files to address
event names refering to the /sys/devices/cpum_[cs]f
devices.
Signed-off-by: Thomas Richter
Reviewed-by: Hendrik Brueckner
---
perf stat displays transactional counters using flag -T on x86.
On s390 use a json file defined metric named transaction to
achieve the same result.
Output before:
none
Output after:
[root@s35lp76 perf]# ./perf stat -M transaction -- \
~/mytesttx 1 >/tmp/111
On 20/06/18 13:20, Mikko Perttunen wrote:
> Add bindings for the Tegra Combined UART device used to talk to the
> UART console on Tegra194 systems.
>
> Signed-off-by: Mikko Perttunen
> Reviewed-by: Rob Herring
> ---
>
> Notes:
> v2:
> - Added Rob's Reviewed-by.
>
>
On Thu, Jun 21, 2018 at 11:56:56AM +0800, Xunlei Pang wrote:
> >> Fixes: 51f2176d74ac ("sched/fair: Fix unlocked reads of some
> >> cfs_b->quota/period")
> >> Cc: Ben Segall
> >
> > Reviewed-By: Ben Segall
>
> Thanks Ben :-)
>
> Hi Peter, could you please have a look at them?
I grabbed
This is an updated version with feedback from Johannes integrated. Still
not runtime tested but I am posting it to make further review easier.
>From ed2796dc3894f93ddf0fc9ec74b83c58abc2b4ff Mon Sep 17 00:00:00 2001
From: Michal Hocko
Date: Wed, 20 Jun 2018 10:25:10 +0200
Subject: [PATCH] memcg,
Deep enough power saving mode can result into losing context of the clock
registers also, and they need to be restored once coming back from the power
saving mode. Hence add functions to save/restore clock context.
Tested for DS0 on am437x-gp-evm
Based on top of linux-next
Changes in v2:
From: Russ Dill
SoCs like AM43XX lose clock registers context during RTC-only
suspend. Hence add functions to save/restore the clock registers
context.
Signed-off-by: Keerthy
Signed-off-by: Russ Dill
---
Changes in v2:
* Replaced clk_dflt_restore instances to
From: Russ Dill
Deep enough power saving mode can result into losing context of the clock
registers also, and they need to be restored once coming back from the power
saving mode. Hence add functions to save/restore clock context.
Signed-off-by: Keerthy
Signed-off-by: Russ Dill
---
No
Save/restore clk context based on enable_off_mode setting.
The context needs to be saved at the very end of suspend path
and restored at the beginning of resume path.
Signed-off-by: Keerthy
---
No Changes in v2
arch/arm/mach-omap2/pm33xx-core.c| 15 +++
drivers/soc/ti/pm33xx.c
On Thursday 21 June 2018 01:40 PM, Keerthy wrote:
> Deep enough power saving mode can result into losing context of the clock
> registers also, and they need to be restored once coming back from the power
> saving mode. Hence add functions to save/restore clock context.
>
Seems like there is
On 20/06/18 13:20, Mikko Perttunen wrote:
> The HSP driver is currently in many places written with the assumption
> of only supporting doorbells. Prepare for the addition of shared
> mailbox support by removing these assumptions and cleaning up the code.
>
> Signed-off-by: Mikko Perttunen
>
The clock gate restore context function enables or disables
the gate clocks based on the enable_count. This is done in cases
where the clock context is lost and based on the enable_count
the clock either needs to be enabled/disabled.
Signed-off-by: Keerthy
---
Changes in v2:
* Renamed
The clock gate restore context function enables or disables
the gate clocks based on the enable_count. This is done in cases
where the clock context is lost and based on the enable_count
the clock either needs to be enabled/disabled.
Signed-off-by: Keerthy
---
Changes in v2:
* Renamed
From: Russ Dill
Deep enough power saving mode can result into losing context of the clock
registers also, and they need to be restored once coming back from the power
saving mode. Hence add functions to save/restore clock context.
Signed-off-by: Keerthy
Signed-off-by: Russ Dill
---
No
Save/restore clk context based on enable_off_mode setting.
The context needs to be saved at the very end of suspend path
and restored at the beginning of resume path.
Signed-off-by: Keerthy
---
No Changes in v2
arch/arm/mach-omap2/pm33xx-core.c| 15 +++
drivers/soc/ti/pm33xx.c
Deep enough power saving mode can result into losing context of the clock
registers also, and they need to be restored once coming back from the power
saving mode. Hence add functions to save/restore clock context.
Tested for DS0 on am437x-gp-evm
Based on top of linux-next
Changes in v2:
On (06/21/18 09:59), Dmitry Vyukov wrote:
> >
> >> + printk(KERN_ALERT "BUG: unable to handle kernel %s at %px\n",
> >> + (address < PAGE_SIZE ? "NULL pointer dereference" :
> >> + "paging request"), (void *) address);
> >
> > Perhaps pr_alert() ?
>
> It's the
On Thu, Jun 21, 2018 at 5:10 PM kernel test robot wrote:
>
> FYI, we noticed a -5.6% regression of netperf.Throughput_total_tps due to
> commit 050e9b ("Kbuild: rename CC_STACKPROTECTOR[_STRONG] config variables")
That's perhaps a surprisingly large cost to stack protector, but you
did move
From: Bartosz Golaszewski
This driver is no longer used as an early platform driver. Remove the
registration macro.
Signed-off-by: Bartosz Golaszewski
Acked-by: Arnd Bergmann
Acked-by: Daniel Lezcano
---
drivers/clocksource/timer-ti-dm.c | 1 -
1 file changed, 1 deletion(-)
diff --git
On Thu, Jun 21, 2018 at 06:42:52AM +0200, Chris Opperman wrote:
> Hi Dan,
>
> I agree completely. I was concerned whether the preprocessor definitions in
> p80211metadef.h were named according to some convention as there are
> many definitions named similarly there.
>
Yeah, sure but in that
From: Bartosz Golaszewski
SuperH is the only user of the current implementation of early platform
device support. We want to introduce a more robust approach to early
probing. As the first step - move all the current early platform code
to arch/sh.
In order not to export internal drivers/base
From: Bartosz Golaszewski
Old early platform device support is now sh-specific. Before moving on
to implementing new early platform framework based on real platform
devices, prefix all early platform symbols with 'sh_'.
Signed-off-by: Bartosz Golaszewski
---
arch/sh/drivers/platform_early.c
Dear God select,
My name is Mrs.Raymond Mabel, an elderly widow who suffers from a prolonged
illness,l I am contacting you in regards to a Charity Project for helping Less
privileged people,orphanages, widows and propagating the word of God.
which I want to entrust into your care as my
Hi, Linus,
Linus Torvalds writes:
> On Thu, Jun 21, 2018 at 5:10 PM kernel test robot
> wrote:
>>
>> FYI, we noticed a -5.6% regression of netperf.Throughput_total_tps
>> due to commit 050e9b ("Kbuild: rename CC_STACKPROTECTOR[_STRONG]
>> config variables")
>
> That's perhaps a surprisingly
I recently started a discussion about the need for a proper early device
probing mechanism[1]. One that would be based on real platform drivers
and support both platform data and device tree.
While we're far from reaching any consensus on the implementation, Arnd
suggested that I start off by
On (06/20/18 13:32), Dmitry Vyukov wrote:
> >>
> >> So this is another reason to get rid of pr_cont entirely, right?
> >
> > Getting rid of pr_cont() from important output would be totally cool.
> > Quoting Linus:
> >
> > Only acceptable use of continuations is basically boot-time testing,
> >
On 20/06/18 13:20, Mikko Perttunen wrote:
> The Tegra HSP block supports 'shared mailboxes' that are simple 32-bit
> registers consisting of a FULL bit in MSB position and 31 bits of data.
> The hardware can be configured to trigger interrupts when a mailbox
> is empty or full. Add support for
On Intel platforms (Skylake and newer), ASPM support in r8169 is the
last missing puzzle to let CPU's Package C-State reaches PC8. Without
ASPM support, the CPU cannot reach beyond PC3. PC8 can save additional
~3W in comparison with PC3 on a Coffee Lake platform, Dell G3 3779.
This is based on
[Cc Reza Arbab - I remember he was able to hit some bugs in memblock
registration code when I was reworking that area previously]
On Fri 01-06-18 14:53:17, osalva...@techadventures.net wrote:
> From: Oscar Salvador
>
>
> Hi,
>
> I wanted to give it a try and do a small cleanup in the
On (06/20/18 19:26), Namit Gupta wrote:
[..]
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 512f7c2..53952ce 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -1348,71 +1348,80 @@ static int syslog_print_all(char __user *buf, int
> size, bool clear)
Randy Dunlap writes:
> On 06/20/2018 11:55 AM, Dirk Gouders wrote:
>> Randy Dunlap writes:
>>
>>> Hi,
>>>
>>> On 06/20/2018 01:42 AM, Dirk Gouders wrote:
Operation
-
The TAB key is reserved to toggle the focus between menu and bottons.
Focus is on the buttons
The argument "gfp_t flags" is not used in kasan_unpoison_element()
and remove_element(), so remove it.
Signed-off-by: Jia-Ju Bai
---
mm/mempool.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/mm/mempool.c b/mm/mempool.c
index 5c9dce34719b..3076ab3f7bc4 100644
Christoph Hellwig 於 2018年6月21日 週四 下午2:40寫道：
>
> On Thu, Jun 21, 2018 at 09:41:41AM +0800, Zong Li wrote:
> > The DMA32 is for 64-bit usage.
> >
> > Signed-off-by: Zong Li
> > ---
> > arch/riscv/mm/init.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/arch/riscv/mm/init.c
> > - s64 offset = (void *)v - (void *)location;
> > + uintptr_t offset = (void *)v - (void *)location;
>
> s64 is signed, uintptr is not, so this might change behavior and needs
> an explanation.
>
Yes, it should be intptr_t. Thanks!
On Wed, 20 Jun 2018 21:12:02 +
Chris Packham wrote:
> On 20/06/18 19:54, Boris Brezillon wrote:
> > On Wed, 20 Jun 2018 17:05:43 +1200
> > Chris Packham wrote:
> >
> >> Some Micron NAND chips (MT29F1G08ABAFAWP-ITE:F) report 00 00 for the
> >> revision number field of the ONFI parameter
On Thu, Jun 21, 2018 at 03:03:32PM +0800, Jia-Ju Bai wrote:
> The argument "gfp_t flags" is not used in kasan_unpoison_element()
> and remove_element(), so remove it.
>
> Signed-off-by: Jia-Ju Bai
Reviewed-by: Matthew Wilcox
On Wed, Jun 20, 2018 at 11:39:38PM -0700, Christoph Hellwig wrote:
> > +ifeq ($(CONFIG_FPU),y)
> > KBUILD_AFLAGS += -march=$(KBUILD_MARCH)$(KBUILD_ARCH_A)fd$(KBUILD_ARCH_C)
> > +else
> > +KBUILD_AFLAGS += -march=$(KBUILD_MARCH)$(KBUILD_ARCH_A)$(KBUILD_ARCH_C)
> > +endif
>
> Can we refactor that
On 21 June 2018 at 07:59, Andrzej Hajda wrote:
> On 20.06.2018 21:34, Krzysztof Kozlowski wrote:
>> On Tue, Jun 19, 2018 at 09:59:04AM +0200, Krzysztof Kozlowski wrote:
>>> On 19 June 2018 at 09:26, Marek Szyprowski wrote:
Hi Krzysztof,
On 2018-06-18 19:42, Krzysztof Kozlowski
On 06/20/2018 09:14 PM, Rob Herring wrote:
On Wed, Jun 20, 2018 at 03:51:36PM +0200, Ludovic Barre wrote:
From: Ludovic Barre
This patch adds config data to manage specific properties by
compatible. Adds stm32mp1 config which requires pclk clock.
Signed-off-by: Ludovic Barre
---
Hi Jacek and Bjorn,
> OK, I've revised the discussion under Qualcomm LPG patch set and
> it seems that we have almost ready solution in [0], except the
> pattern_repeat file you mention in [1]. So probably Baolin could
> address your remarks from [1] and add pattern_repeat file to the
> patch
Hello,
A new open project has been created to collect the list of computer hardware
devices with poor Linux compatibility based on the Linux-Hardware.org data:
https://github.com/linuxhw/HWInfo
There are about 29 thousands of depersonalized hwinfo reports
(https://github.com/openSUSE/hwinfo)
On Wed 20-06-18 15:36:45, David Rientjes wrote:
[...]
> That makes me think that "oom_notify_list" isn't very intuitive: it can
> free memory as a last step prior to oom kill. OOM notify, to me, sounds
> like its only notifying some callbacks about the condition. Maybe
> oom_reclaim_list and
On Wed, Jun 20, 2018 at 09:41:35PM -0400, Pavel Tatashin wrote:
> > I don't think __try_online_node() will ever return a value greater than
> > zero. I assume what was meant was
>
> Hi Andrew and Oscar,
>
> Actually, the new __try_online_node() returns:
> 1 -> a new node was allocated
> 0 ->
On Thu, Jun 21, 2018 at 11:14:49AM +0800, Jia-Ju Bai wrote:
> The kernel may sleep with holding a spinlock.
> The function call path (from bottom to top) in Linux-4.16.7 is:
>
> [FUNC] schedule
> kernel/locking/rtmutex.c, 1223: schedule in rt_mutex_handle_deadlock
> kernel/locking/rtmutex.c,
On Wed 20-06-18 15:38:36, Johannes Weiner wrote:
> On Wed, Jun 20, 2018 at 05:31:48PM +0200, Michal Hocko wrote:
> > * Please note that mem_cgroup_oom_synchronize might fail to find a
> > * victim and then we have rely on mem_cgroup_oom_synchronize otherwise
> > * we would fall back
From: Bartosz Golaszewski
These are the remaining patches that still need to be merged in order
to complete the conversion of the davinci dsp driver to using the reset
framework.
They apply on top of v4.18-rc1 with David Lechner's remaining patches
merged.
v1 -> v2:
- fixed the device tree
From: Bartosz Golaszewski
Switch to using the reset framework instead of handcoded reset routines
we used so far.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Sekhar Nori
Reviewed-by: Philipp Zabel
---
drivers/remoteproc/da8xx_remoteproc.c | 34 +++
1 file
From: Bartosz Golaszewski
The davinci-rproc driver will soon use the reset framework. Add the
resets property to the dsp node in da850.dtsi.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/boot/dts/da850.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Bartosz Golaszewski
This code is no longer used. Remove it.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
Acked-by: Stephen Boyd
---
arch/arm/mach-davinci/include/mach/clock.h | 21 -
drivers/clk/davinci/psc.c | 18
From: Bartosz Golaszewski
The psc driver registers with the reset framework as a provider. Add
the #reset-cells property to the psc0 node.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: David Lechner
---
arch/arm/boot/dts/da850.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git
On Wed 20-06-18 13:34:52, David Rientjes wrote:
> On Wed, 20 Jun 2018, Michal Hocko wrote:
>
> > On Tue 19-06-18 10:33:16, Michal Hocko wrote:
> > [...]
> > > As I've said, if you are not willing to work on a proper solution, I
> > > will, but my nack holds for this patch until we see no other
On 2018-06-21 11:40, Mawanda Henry wrote:
> including the SPDX license identifier header makes it easy for
> developers and machines to know the lecense that is governing the file
If you do changes like this, you should also remove the actual
license text (it follows later in the comment in this
When atomic_inc_not_zero(v) isn't defined, will define
it as falling back to atomic_add_unless((v), 1, 0), so there's no need
for arch code to do so.
There should be no functional change as a result of this patch.
Signed-off-by: Mark Rutland
Acked-by: Peter Zijlstra (Intel)
Acked-by: Palmer
Hi Rohit,
On 21-06-18, 16:23, Rohit kumar wrote:
> +static struct sdm845_snd_data *sdm845_sbc_parse_of(struct snd_soc_card *card)
> +{
> + struct device *dev = card->dev;
> + struct snd_soc_dai_link *link;
> + struct device_node *np, *codec, *platform, *cpu, *node;
> + int ret,
Hello,
I believe that this patch
fpga: manager: change api, don't use drvdata
7085e2a94f7df5f419e3cfb2fe809ce6564e9629
is incomplete and buggy.
I completely agree that drvdata should not be used by the FPGA manager
or any other subsystem like that.
What is buggy is the function
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-4.18-rc2
with top-most commit b51e001385f1c861445af3efeab766811ee8db29
Merge branch 'pm-tools'
on top of commit ce397d215ccd07b8ae3f71db689aedb85d56ab40
Linux 4.18-rc1
to receive
This patch adds support to SLIMbus stream apis for slimbus device.
SLIMbus streaming involves adding support to Data Channel Management and
channel Reconfiguration Messages to slim core plus few stream apis.
>From slim device side the apis are very simple mostly inline with other
stream apis.
This patch adds support to stream support, this involve implementing
user specific implementation of Data channel management and channel
management SLIMbus messages.
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/qcom-ngd-ctrl.c | 144 +++-
1 file
This pixel format is a fully packed and 10bits variant of NV12.
A luma pixel would take 10bits in memory, without any
filled bits between pixels in a stride. The color gamut
follows the BT.2020 standard.
Signed-off-by: Randy Li
---
drivers/gpu/drm/drm_fourcc.c | 1 +
This patchset adds basic stream support for SLIMbus devices and
controllers. Mostly inspired by soundwire stream patches. But slimbus
stream is much simpler compared to soundwire
>From slim_device side, we have below 6 new apis.
slim_stream_allocate() - allocating runtime slim stream
including the SPDX license identifier header makes it easy for
developers and machines to know the lecense that is governing the file
Signed-off-by: Mawanda Henry
---
drivers/i2c/i2c-core-slave.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/i2c/i2c-core-slave.c
On Wed, Jun 20, 2018 at 10:32:54PM +0530, Srikar Dronamraju wrote:
> Currently resetting the migrate rate limit is under a spinlock.
> The spinlock will only serialize the migrate rate limiting and something
> similar can actually be achieved by a simpler xchg.
>
> Running SPECjbb2005 on a 4 node
On Wed, Jun 20, 2018 at 10:32:55PM +0530, Srikar Dronamraju wrote:
> The metrics for updating scan periods are local or task specific.
> Currently this updation happens under numa_group lock which seems
> unnecessary. Hence move this updation outside the lock.
>
> Running SPECjbb2005 on a 4 node
On Thu, 21 Jun 2018 22:33:25 +1200
Chris Packham wrote:
> Add defines for the ONFI version bits and use them in
> nand_flash_detect_onfi().
>
> Signed-off-by: Chris Packham
Reviewed-by: Boris Brezillon
> ---
> Changes in v4:
> - New
>
> drivers/mtd/nand/raw/nand_base.c | 10 +-
>
Hi Bartosz,
On Thursday 21 June 2018 01:07 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> These are the remaining patches that still need to be merged in order
> to complete the conversion of the davinci dsp driver to using the reset
> framework.
>
> They apply on top of
Architectures with atomic64_fetch_add_unless() provide a preprocessor
symbol if they do so, and all other architectures have trivial C
implementations of atomic64_add_unless() which are near-identical.
Let's unify the trivial definitions of atomic64_fetch_add_unless() in
, so that we always have
The conditional inc/dec ops differ for atomic_t and atomic64_t:
* atomic_inc_unless_positive() is optional for atomic_t, and doesn't exist for
atomic64_t.
* atomic_dec_unless_negative() is optional for atomic_t, and doesn't exist for
atomic64_t.
* atomic_dec_if_positive is optional for
Some of the atomics return the result of a test applied after the atomic
operation, and almost all architectures implement these as trivial
wrappers around the underlying atomic. Specifically:
* _inc_and_test(v) is (_inc_return(v) == 0)
* _dec_and_test(v) is (_dec_return(v) == 0)
*
1 - 100 of 1302 matches
Mail list logo
