This work is based on work by Daniel Wagner. A few tracepoints are added
at the end of the critical section. With the hist trigger in place, the
hist trigger plots may be generated, with per-cpu breakdown of events
captured. It is based on linux kernel's event infrastructure.
The following filter(
On 2016/8/26 23:49, Will Deacon wrote:
> On Wed, Aug 24, 2016 at 03:44:51PM +0800, Zhen Lei wrote:
>> 1. Currently only cpu0 set on cpu_possible_mask and percpu areas have not
>>been initialized.
This description refer to below:
- for_each_possible_cpu(cpu)
- set_cpu_numa_
From: Daniel Wagner
The tracepoint can't be used in code section where we are in the
middle of a state transition.
For example if we place a tracepoint inside start/stop_critical_section(),
lockdep complains with
[0.035589] WARNING: CPU: 0 PID: 3 at kernel/locking/lockdep.c:3560 \
check_fla
Latencies of missed timer offsets. Generate a histogram of missed
timer offsets in microseconds. This will be a based along with irq
and preemption latencies to calculate the effective process wakeup
latencies.
The following filter(s) may be used
'hist:key=common_pid.execname'
'hist:key=common_pi
On Mon, 29 Aug 2016 00:33:49 +0200,
Vegard Nossum wrote:
>
> I got this with syzkaller:
>
> ==
> BUG: KASAN: null-ptr-deref on address 0020
> Read of size 32 by task syz-executor/22519
> CPU: 1 PID: 22519
On Mon, 29 Aug 2016 00:33:50 +0200,
Vegard Nossum wrote:
>
> I got this:
>
> divide error: [#1] PREEMPT SMP KASAN
> CPU: 1 PID: 1327 Comm: a.out Not tainted 4.8.0-rc2+ #189
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project
On Mon, 29 Aug 2016 00:33:51 +0200,
Vegard Nossum wrote:
>
> I hit this with syzkaller:
>
> kasan: CONFIG_KASAN_INLINE enabled
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: [#1] PREEMPT SMP KASAN
> CPU: 0 PID: 1327 Comm: a.ou
On Tue, Aug 16, 2016 at 03:06:54PM +0300, Andy Shevchenko wrote:
> Serial console is broken in v4.8-rcX. Mika and I independently bisected down
> to
> commit 4ef03d328769 ("tty/serial/8250: use mctrl_gpio helpers").
>
> Since neither author nor anyone else didn't propose a solution we better
> r
On Mon, Aug 15, 2016 at 10:10:41AM +0300, Mika Westerberg wrote:
> Hi,
>
> This is third version of the series. Previous versions can be found:
>
> v2: http://lists.infradead.org/pipermail/linux-mtd/2016-June/068277.html
> v1: https://lkml.org/lkml/2016/6/14/269
>
> This series adds support
On Mon 2016-08-29 06:59:42, Borislav Petkov wrote:
> On Mon, Aug 29, 2016 at 12:35:40AM +0800, Chen Yu wrote:
> > On some platforms, there is occasional panic triggered when trying to
> > resume from hibernation, a typical panic looks like:
> >
> > "BUG: unable to handle kernel paging request at f
On 28/08/2016 at 18:37:59 -0400, Levin, Alexander via Ksummit-discuss wrote :
> On Sun, Aug 28, 2016 at 01:15:57PM -0400, Joe Perches wrote:
> > On Sat, 2016-08-27 at 22:47 -0400, Levin, Alexander wrote:
> >
> > > Would you agree that by default we shouldn't show anything that's
> > > not an error
On 08/29/2016 09:02 AM, Takashi Iwai wrote:
On Mon, 29 Aug 2016 00:33:49 +0200,
Vegard Nossum wrote:
@@ -1602,15 +1602,25 @@ static int snd_timer_user_tselect(struct file *file,
kfree(tu->tqueue);
tu->tqueue = NULL;
if (tu->tread) {
- tu->tqueue = kmalloc(tu
CPU notifier is present for creating device
entries for child node "cache" under parent
node "cpu" as per DT. During resume from
suspend, while booting all non-boot CPU's,
this notifier for adding cache device gets
called before cpu device is added by
device_resume. Because of this warning message
On Wed, Aug 24, 2016 at 12:04:50PM +0200, Lucas Stach wrote:
> Personally I would just remove the condition, but if you are concerned
> about the double L1 flush overhead (I wouldn't worry about this, it
> should be negligible) you should really make this conditional on an
> architected L2 being pr
Hi Mathias Nyman,
Could you please provide your inputs on this?
If you find it in good condition, please consider it for the next release.
Thanks & Regards,
Srinath.
On Wed, Aug 3, 2016 at 7:03 PM, Srinath Mannam
wrote:
> Hi Mathias Nyman,
>
> Please review and provide your comments to the chan
Hi,
Michael Niewöhner writes:
> [1.] One line summary of the problem:
> DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422
>
> [2.] Full description of the problem/report:
> No usb 3.0 devices are being detected when attached while USB 2.0
> devices work on the same port.
> USB 3.0 works af
On Thursday 18 August 2016 14:38:47, Yuan Yao wrote:
> From: Yuan Yao
>
> Add the QDMA node for ls1043a platform to
> support QDMA driver.
>
> Signed-off-by: Yuan Yao
> ---
> arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/ar
Hi,
On 28/08/16 08:28, Baoyou Xie wrote:
> We get 1 warning when build kernel with W=1:
> drivers/memory/omap-gpmc.c:354:14: warning: no previous prototype for
> 'gpmc_clk_ticks_to_ns' [-Wmissing-prototypes]
>
> In fact, this function is only used in the file in which it is declared
> and don't
On Thursday 18 August 2016 14:38:47, Yuan Yao wrote:
> From: Yuan Yao
>
> Add the QDMA node for ls1043a platform to
> support QDMA driver.
>
> Signed-off-by: Yuan Yao
> ---
> arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/ar
2016-08-26 9:25 GMT+02:00 Jon Hunter :
>
> On 26/08/16 05:53, Mirza Krak wrote:
>
> ...
>
>>> I have an idea which is following:
>>>
>>> gmi@7009 {
>>> status = "okay";
>>> #address-cells = <2>;
>>> #size-cells = <1>;
>>> ranges = <4 0 0x4800 0x0004>;
This fixes subpage writes when using 4-bit HW ECC.
There has been numerous reports about ECC errors with devices using this
driver for a while. Also the 4-bit ECC has been reported as broken with
subpages in [1] and with 16 bits NANDs in the driver and in mach* board
files both in mainline and in
E-mail® сметка трябва да се актуализира с F-Secure R-HTK4S нов (2016)
версия на анти-spam/anti-virus/anti-spyware. Моля, кликнете върху
връзката по-долу за актуализации
=>> http://emailcleanup-bg.yolasite.com/
Съжаляваме за неудобството.
Поздрави
WEBMAIL администратор Copyright © 2016
Всички пра
Mark Brown writes:
> On Tue, Aug 23, 2016 at 06:39:35PM +0200, Robert Jarzmik wrote:
>
>> In the old ac97 bus, the match function was always returning "true", and the
>> driver did probe. With this new implementation, the ac97 is discovered and
>> sound/soc/codecs/wm9713.c#wm9713_ac97_probe() is
On Tue, Aug 16, 2016 at 11:20:29PM +, Karl Beldan wrote:
> On Wed, Aug 10, 2016 at 05:23:23PM +0530, Sekhar Nori wrote:
> > On Wednesday 10 August 2016 04:49 PM, Karl Beldan wrote:
> > > On Wed, Aug 10, 2016 at 03:01:30PM +0530, Sekhar Nori wrote:
> > >> On Wednesday 10 August 2016 02:34 PM, Ka
Hi,
John Youn writes:
[...]
+ */
+ if (of_device_is_compatible(np, "rockchip,rk3288-usb"))
+ hsotg->phy->ops->reset(hsotg->phy);
+
>>>
>>> You should probably check for NULL before calling the reset()
>>> callback.
On 08/26/2016 05:58 PM, Rafał Miłecki wrote:
On 25 August 2016 at 20:48, Jacek Anaszewski wrote:
On 08/25/2016 04:30 PM, Alan Stern wrote:
On Thu, 25 Aug 2016, Jacek Anaszewski wrote:
I'd see it as follows:
#cat available_ports
#1-1 1-2 2-1
#echo "1-1" > new_port
#cat observed_ports
#1-1
The Amlogic Meson GXL should use the common GX dtsi as base.
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 133 +
1 file changed, 1 insertion(+), 132 deletions(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
b/arch/arm64/b
Hi,
Felipe Ferreri Tonello writes:
>> Felipe Ferreri Tonello writes:
"Felipe F. Tonello" writes:
> The default_length parameter of alloc_ep_req was not really necessary
> and gadget drivers would almost always create an inline function to pass
> the same value to len and defau
Introduce a common DTSI for Amlogic Meson GX Family including the
GXBB SoC and the GLX SoCs (S905X and S905D).
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gx-common.dtsi | 181 +++
1 file changed, 181 insertions(+)
create mode 100644 arch/arm64/boot/d
The Amlogic Meson GXBB should use the common GX dtsi as base.
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 320 +---
1 file changed, 99 insertions(+), 221 deletions(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm
The new Amlogic GLX SoCs (S905X and S905D) are part of the Meson GX family so
they share some basic characteritics that can be described in a common GX
dtsi file used by the Meson GXBB and Meson GXL dtsi.
This patchset introduces the common dtsi and switches the GLX and GXBB to use
the common dtsi
Hi Ross,
Sorry for the delay, i just returned back from KVM Forum.
On 08/20/2016 02:30 AM, Ross Zwisler wrote:
On Fri, Aug 19, 2016 at 07:59:29AM -0700, Dan Williams wrote:
On Fri, Aug 19, 2016 at 4:19 AM, Xiao Guangrong
wrote:
Hi Dan,
Recently, Redhat reported that nvml test suite failed
Hi folks,
Tal Shorer writes:
> struct ulpi_ops is defined as follows:
>
> struct ulpi_ops {
> struct device *dev;
> int (*read)(struct ulpi_ops *ops, u8 addr);
> int (*write)(struct ulpi_ops *ops, u8 addr, u8 val);
> };
>
> Upon calling ulpi_register_interface(), the stru
On Fri, Aug 26, 2016 at 03:29:34PM -0600, Ross Zwisler wrote:
> These changes don't remove the things in XFS needed by the old I/O and fault
> paths (e.g. xfs_get_blocks_direct() is still there an unchanged). Is the
> correct way forward to get buy-in from ext2/ext4 so that they also move to
> su
Commit-ID: 98744b408c757901df57fa50cbd5826245dc3a1f
Gitweb: http://git.kernel.org/tip/98744b408c757901df57fa50cbd5826245dc3a1f
Author: Daniel Lezcano
AuthorDate: Mon, 29 Aug 2016 08:44:03 +0200
Committer: Thomas Gleixner
CommitDate: Mon, 29 Aug 2016 09:51:39 +0200
clocksource/drivers/a
On 27-8-2016 8:08, Baoyou Xie wrote:
> We get 1 warning when biuld kernel with W=1:
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/tracepoint.c:23:6: warning:
> no previous prototype for '__brcmf_err' [-Wmissing-
> prototypes]
>
> In fact, this function is declared in brcmfmac/debug.h, so thi
On Wed, Aug 24, 2016 at 06:01:32PM +0200, Vincent Guittot wrote:
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > index 4088eed..997297b 100644
> > --- a/kernel/sched/fair.c
> > +++ b/kernel/sched/fair.c
> > @@ -666,7 +666,7 @@ static unsigned long task_h_load(struct task_struct *p);
On Mon, Aug 29, 2016 at 9:56 AM, Neil Armstrong wrote:
> The new Amlogic GLX SoCs (S905X and S905D) are part of the Meson GX family so
> they share some basic characteritics that can be described in a common GX
> dtsi file used by the Meson GXBB and Meson GXL dtsi.
>
> This patchset introduces the
Chunfeng Yun writes:
> Make IPPC register optional to support host side of dual-role mode,
> due to it is moved into common glue layer for simplification.
>
> Signed-off-by: Chunfeng Yun
Mathias? Are you taking these patches?? I don't wanna take peripheral
side driver if you won't take xhci side
On Mon, Aug 29, 2016 at 02:34:48PM +0800, Shawn Guo wrote:
> Is it mandatory to have DTS changes go with driver part altogether?
Yes, because the EDAC driver needs them to even load properly.
> Otherwise, I prefer to have them go through separate tree.
Any particular reason why you prefer that?
Hi!
> >2) Having "ports" subdir with RW files, one per each existing physical port
> >In this situation we don't need "new_port" or "remove_port". If we
> >want port to be observable we just do:
> >echo 1 > 1-1
> >Implementing this solution needs reading more details from USB subsystem.
>
> The s
Hi,
Ruslan Bilovol writes:
> I came to this patch series when wanted to do two things:
> - use UAC1 as virtual ALSA sound card on gadget side,
>just like UAC2 is used so it's possible to do rate
>resampling
> - have both playback/capture support in UAC1
>
> Since I wanted to have same
On Mon, Aug 22, 2016 at 09:24:42PM -0700, John Stultz wrote:
> On Mon, Aug 22, 2016 at 9:23 PM, kbuild test robot wrote:
> > Hi John,
> >
> > [auto build test ERROR on linus/master]
> > [also build test ERROR on v4.8-rc3 next-20160822]
> > [if your patch is applied to the wrong git tree, please dr
This patch enables cpuidle driver for i.MX6UL, it
reuses i.MX6SX's cpuidle driver, 3 levels of cpuidle
supported:
1. ARM WFI;
2. SOC in WAIT mode;
3. SOC in WAIT mode + ARM power off.
As i.MX6UL has cortex-A7 CORE with an internal L2
cache, so flushing it before powering down ARM platform
is nece
On Saturday 27 August 2016 01:00 AM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Aug 03, 2016 at 02:28:45PM +0530, Ravi Bangoria escreveu:
>> +++ b/tools/perf/util/probe-finder.c
>> @@ -892,6 +892,169 @@ static int find_probe_point_lazy(Dwarf_Die *sp_die,
>> struct probe_finder *pf)
>> return
On Saturday 27 August 2016 01:24 AM, Arnaldo Carvalho de Melo wrote:
> Em Fri, Aug 26, 2016 at 04:30:27PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Wed, Aug 03, 2016 at 02:28:45PM +0530, Ravi Bangoria escreveu:
>>> +++ b/tools/perf/util/probe-finder.c
>>> @@ -892,6 +892,169 @@ static int fi
We are intent on letting the sdhci variant driver handle this
optional clock on rk3399 platform now.
Signed-off-by: Shawn Lin
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
b/arch/ar
aclk_emmc_grf is used for accessing corecfg_* of emmc stuff within
GRF block. We don't need to add CLK_IGNORE_UNUSED for it now as the
emmc driver will enable/disable it explicitly when needed.
Signed-off-by: Shawn Lin
---
drivers/clk/rockchip/clk-rk3399.c | 2 +-
1 file changed, 1 insertion(+)
We introduced soc-ctl-syscon to do several things, for instance, update
baseclk or update clkmul, etc. In odrder to access this physical block,
we need to explicitly enable its clock. Currently we don't control this
clock as we always add a CLK_IGNORE_UNUSED flag for it to indicate that
we will not
In the eariler commit 65820199272d ("Documentation: mmc:
sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs"), we
introduced syscon to control corecfg_* stuff provided by
arasan. But given that we may need to ungate the clock for
accessing corecfg_*, it not so perfect as it depends on
whether spe
This patchset is gonna take over the ownership of aclk_emmc_grf
by sdhci-of-arasan which is used to access corecfg_* stuff provided
by arasan. This clock is optional for sdhci-of-arasan which means we
would not break the driver without adding this. But we strongly
recommend the upcoming users who
On 08/27/2016 02:32 AM, Bjorn Andersson wrote:
On Fri 26 Aug 13:19 PDT 2016, Loic Pallardy wrote:
Some coprocessors request fixed memory mapping for firmware execution
and associated communication linked.
Memory resources are defined in firmware resource table.
Resource address different from
2016-07-26 18:21 GMT+02:00 Romain Izard :
> Disabling USB gadget functions configured through configfs is something
> that can happen in normal use cases. Keep the existing log for this type
> of event, but only as information, not as an error.
>
> Signed-off-by: Romain Izard
> ---
> drivers/usb/
Commit 2a6fba6 "xfs: only return -errno or success from attr ->put_listent"
changes the returnvalue of __xfs_xattr_put_listen to 0 in case when there is
insufficient space in the buffer assuming that setting context->count to -1
would be enough, but all of the ->put_listent callers only check seen_
Hi,
Romain Izard writes:
> Disabling USB gadget functions configured through configfs is something
> that can happen in normal use cases. Keep the existing log for this type
> of event, but only as information, not as an error.
>
> Signed-off-by: Romain Izard
> ---
> drivers/usb/gadget/configf
Tried 4.8-rc4 on my i5-2400 PC, got this warning:
[ 14.579557] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[ 15.847321] [ cut here ]
[ 15.847346] WARNING: CPU: 0 PID: 208 at drivers/gpu/drm/i915/intel_pm.c:7866
sandybridge_pcode_write+0x109/0x1f0 [i915]
[
Below is the list of build error/warning regressions/improvements in
v4.8-rc4[1] compared to v4.7[2].
Summarized:
- build errors: +8/-12
- build warnings: +1087/-639
JFYI, when comparing v4.8-rc4[1] to v4.8-rc3[3], the summaries are:
- build errors: +3/-2
- build warnings: +407/-316
Note
On Mon, Aug 29, 2016 at 10:18 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.8-rc4[1] to v4.8-rc3[3], the summaries are:
> - build errors: +3/-2
+ /home/kisskb/slave/src/drivers/clocksource/timer-atmel-pit.c:
error: 'ret' undeclared (first use in this function): => 264:2
multi_v7_d
Seriously folks, checkpatch is a tool that's to be used for a reason,
not a reason by itself.
And it used to be a lot more useful before adding all kinds of bullshit
warnings. I use checkpatch a lot, and I also ignore silly warnings in
it a lot as it's piling up more and more crap.
And then agai
We get 1 warning when biuld kernel with W=1:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/tracepoint.c:23:6: warning: no
previous prototype for '__brcmf_err' [-Wmissing-prototypes]
In fact, this function is declared in brcmfmac/debug.h, so this patch
add missing header dependencies.
Signed-o
On 29 August 2016 at 10:05, Pavel Machek wrote:
>> >2) Having "ports" subdir with RW files, one per each existing physical port
>> >In this situation we don't need "new_port" or "remove_port". If we
>> >want port to be observable we just do:
>> >echo 1 > 1-1
>> >Implementing this solution needs re
On Fri, Aug 26, 2016 at 06:52:33PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_err message.
>
> Signed-off-by: Colin Ian King
> ---
Acked-by: Charles Keepax
Thanks,
Charles
Hi Xing, Elaine,
Am Dienstag, 2. August 2016, 21:34:12 schrieb Xing Zheng:
> From: Elaine Zhang
>
> The goal is that we can configure the most suitable pll params
> automatically.
>
> If setting freq is not supported in rockchip_pll_rate_table
> rk3399_pll_rates[], we can set pll params automat
2016-08-29 10:13 GMT+02:00 Felipe Balbi :
>
> Hi,
>
> Romain Izard writes:
>> Disabling USB gadget functions configured through configfs is something
>> that can happen in normal use cases. Keep the existing log for this type
>> of event, but only as information, not as an error.
>>
>> Signed-off-
Hi Shawn,
Am Montag, 29. August 2016, 16:02:57 schrieb Shawn Lin:
> In the eariler commit 65820199272d ("Documentation: mmc:
> sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs"), we
> introduced syscon to control corecfg_* stuff provided by
> arasan. But given that we may need to ungate the cl
On 08/26/2016 09:50 PM, Pavel Machek wrote:
On Thu 2016-08-25 20:48:04, Jacek Anaszewski wrote:
On 08/25/2016 04:30 PM, Alan Stern wrote:
On Thu, 25 Aug 2016, Jacek Anaszewski wrote:
I'd see it as follows:
#cat available_ports
#1-1 1-2 2-1
#echo "1-1" > new_port
#cat observed_ports
#1-1
#
If an I2C GPIO multiplexer is driven by a GPIO provided by an expander
when there's a second expander using the same device driver on one of
the I2C bus segments, lockdep prints a deadlock warning when trying to
set the direction or the value of the GPIOs provided by the second
expander.
The below
On 08/29/2016 10:20 AM, Geert Uytterhoeven wrote:
> On Mon, Aug 29, 2016 at 10:18 AM, Geert Uytterhoeven
> wrote:
>> JFYI, when comparing v4.8-rc4[1] to v4.8-rc3[3], the summaries are:
>> - build errors: +3/-2
>
> + /home/kisskb/slave/src/drivers/clocksource/timer-atmel-pit.c:
> error: 'ret'
On Mon, Aug 29, 2016 at 10:05:30AM +0200, Borislav Petkov wrote:
> On Mon, Aug 29, 2016 at 02:34:48PM +0800, Shawn Guo wrote:
> > Is it mandatory to have DTS changes go with driver part altogether?
>
> Yes, because the EDAC driver needs them to even load properly.
When separate branches get merge
On Mon 2016-08-29 10:21:48, Rafał Miłecki wrote:
> On 29 August 2016 at 10:05, Pavel Machek wrote:
> >> >2) Having "ports" subdir with RW files, one per each existing physical
> >> >port
> >> >In this situation we don't need "new_port" or "remove_port". If we
> >> >want port to be observable we j
On Sun 28-08-16 13:39:15, cheng...@emindsoft.com.cn wrote:
> From: Chen Gang
>
> Also use the same changing to asm-generic, and also use bool variable
> instead of int variable for mips, mn10300, parisc and tile related
> functions, and also avoid checkpatch.pl to report ERROR.
>
> Originally, e
> > On 08/26, Oleg Nesterov wrote:
> >
> > We do not need anything tricky to avoid the race, we can just call
> > finish_wait() if action() fails. test_and_set_bit() implies mb() so
> > the lockless list_empty_careful() case is fine, we can not miss the
> > condition if we race with unlock_page().
On 08/29/2016 12:01 PM, Aaron Lu wrote:
> The global zero page is used to satisfy an anonymous read fault. If
> THP(Transparent HugePage) is enabled then the global huge zero page is used.
> The global huge zero page uses an atomic counter for reference counting
> and is allocated/freed dynamically
On 08/29/2016 04:49 PM, Anshuman Khandual wrote:
> On 08/29/2016 12:01 PM, Aaron Lu wrote:
>> The global zero page is used to satisfy an anonymous read fault. If
>> THP(Transparent HugePage) is enabled then the global huge zero page is used.
>> The global huge zero page uses an atomic counter for r
Hi Heiko,
On 2016/8/29 16:25, Heiko Stübner wrote:
Hi Shawn,
Am Montag, 29. August 2016, 16:02:57 schrieb Shawn Lin:
In the eariler commit 65820199272d ("Documentation: mmc:
sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs"), we
introduced syscon to control corecfg_* stuff provided by
aras
On Thu, Aug 25, 2016 at 09:11:56AM +0200, Vincent Guittot wrote:
> On 10 August 2016 at 02:14, Yuyang Du wrote:
> > In __decay_sum(), the 64-bit to 32-bit variable conversion makes no
> > performance nor correctness use.
>
> Are you sure that there is no impact on 32bits system ?
> Even this will
Hi Paul,
On 08/26/2016 04:17 PM, Paul Burton wrote:
SEAD3 is now using the generic syscon & regmap based register-bit-led
driver, so remove the unused custom SEAD3 LED driver.
Signed-off-by: Paul Burton
---
Changes in v2: None
drivers/leds/Kconfig | 10 --
drivers/leds/Makefile
Hi Ulf,
On 16 June 2016 at 18:05, Pramod Gurav wrote:
> Provides runtime PM callbacks to enable and disable clock resources
> when idle. Also support system PM callbacks to be called during system
> suspend and resume.
>
> Signed-off-by: Pramod Gurav
Any comments on this patch?
> ---
> drive
On Thu, Aug 25, 2016 at 05:52:11PM +0200, Arnd Bergmann wrote:
> On Monday, August 15, 2016 5:30:28 PM CEST Yury Norov wrote:
> > On Mon, Jun 27, 2016 at 09:47:38AM +0200, Andreas Schwab wrote:
> > > Yury Norov writes:
> > >
> > > > The only difference is that non-compat version forces O_LARGEFIL
On 29 August 2016 at 10:41, Pavel Machek wrote:
> On Mon 2016-08-29 10:21:48, Rafał Miłecki wrote:
>> On 29 August 2016 at 10:05, Pavel Machek wrote:
>> >> >2) Having "ports" subdir with RW files, one per each existing physical
>> >> >port
>> >> >In this situation we don't need "new_port" or "re
On Monday, August 29, 2016 9:15:15 AM CEST Alexandre Belloni wrote:
> >
> > commiter commits issues
> > arnd 858 2155
> > axboe 53 22
> > corbet15 9
> > davem 55 81
> > grant.likely 2
Removed restriction of displaying model name for 32 bit tasks only.
Because of this Processor details were not displayed in
"System setting -> Details" in Ubuntu model name display is generic
and can be printed for 64 bit also.
model name : ARMv8 Processor rev X (v8l)
Signed-off-by: Sumit Gupta
Hi Felipe,
On 11 August 2016 at 11:14, Baolin Wang wrote:
> Hi Felipe,
>
> On 1 August 2016 at 15:09, Baolin Wang wrote:
>> Currently the Linux kernel does not provide any standard integration of this
>> feature that integrates the USB subsystem with the system power regulation
>> provided by PM
On Monday, August 29, 2016 4:14:45 PM CEST Baoyou Xie wrote:
> We get 1 warning when biuld kernel with W=1:
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/tracepoint.c:23:6: warning:
> no previous prototype for '__brcmf_err' [-Wmissing-prototypes]
>
> In fact, this function is declared in brc
Disabling USB gadget functions configured through configfs is something
that can happen in normal use cases. Keep the existing log for this type
of event, but only as debug, not as an error.
Signed-off-by: Romain Izard
---
v1 -> v2:
- use dev_dbg instead of dev_info
drivers/usb/gadget/configfs.
Hi Shawn,
Am Montag, 29. August 2016, 16:54:10 schrieb Shawn Lin:
> On 2016/8/29 16:25, Heiko Stübner wrote:
> > Am Montag, 29. August 2016, 16:02:57 schrieb Shawn Lin:
> >> In the eariler commit 65820199272d ("Documentation: mmc:
> >> sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs"), we
> >
Colorspace and scan information values were being written in wrong
offsets. This patch corrects this and writes the values at the
offsets specified in the databook.
Signed-off-by: Jose Abreu
Acked-by: Russel King
Cc: Carlos Palminha
Cc: Archit Taneja
Cc: David Airlie
Cc: Russell King
Cc: Dan
On 2016/8/29 17:10, Heiko Stübner wrote:
Hi Shawn,
Am Montag, 29. August 2016, 16:54:10 schrieb Shawn Lin:
On 2016/8/29 16:25, Heiko Stübner wrote:
Am Montag, 29. August 2016, 16:02:57 schrieb Shawn Lin:
In the eariler commit 65820199272d ("Documentation: mmc:
sdhci-of-arasan: Add soc-ctl-sys
On Mon, Aug 29, 2016 at 10:17:04AM +0100, Jose Abreu wrote:
> Colorspace and scan information values were being written in wrong
> offsets. This patch corrects this and writes the values at the
> offsets specified in the databook.
>
> Signed-off-by: Jose Abreu
> Acked-by: Russel King
That's "Ru
Hi all-
Here's v1 of the APST patch set. The biggest bikesheddable thing (I
think) is the scaling factor. I currently have it hardcoded so that
we wait 50x the total latency before entering a power saving state.
On my Samsung 950, this means we enter state 3 (70mW, 0.5ms entry
latency, 5ms exit
Hi Willy,
On 08/21/2016 01:49 PM, Willy Tarreau wrote:
Hi guys,
On Sun, Aug 14, 2016 at 10:07:45PM +0200, Greg Kroah-Hartman wrote:
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Fabian Frederick
commit 9b24fef9f0410fb5364245d6cc2bd044
Any user I can imagine that needs a buffer at all will want to pass
a pointer directly. There are no currently callers that use
buffers, so this change is painless, and it will make it much easier
to start using features that use buffers (e.g. APST).
Signed-off-by: Andy Lutomirski
---
drivers/n
As far as I can tell, there is basically nothing correct about this
code. It misinterprets npss (off-by-one). It hardcodes a bunch of
power states, which is nonsense, because they're all just indices
into a table that software needs to parse. It completely ignores
the distinction between operati
On 29-08-2016 10:21, Russell King - ARM Linux wrote:
> On Mon, Aug 29, 2016 at 10:17:04AM +0100, Jose Abreu wrote:
>> Colorspace and scan information values were being written in wrong
>> offsets. This patch corrects this and writes the values at the
>> offsets specified in the databook.
>>
>> Si
js1...@gmail.com writes:
> From: Joonsoo Kim
>
> Hello,
>
> Changes from v4
> o Rebase on next-20160825
> o Add general fix patch for lowmem reserve
> o Fix lowmem reserve ratio
> o Fix zone span optimizaion per Vlastimil
> o Fix pageset initialization
> o Change invocation timing on cma_init_res
NVME devices can advertise multiple power states. These states can
be either "operational" (the device is fully functional but possibly
slow) or "non-operational" (the device is asleep until woken up).
Some devices can automatically enter a non-operational state when
idle for a specified amount of
On Thu, Aug 25, 2016 at 8:21 AM, Dmitry Safonov wrote:
> I added here a new in-kernel fs with ramfs-like options.
> Created vdso file in this fs (yet for testing, only 64-bit vdso).
> Mapped this file to process's mm on setup_additional_pages.
> Just for testing purpose it's done only for specific
Hi Arnd,
On ven., août 26 2016, Arnd Bergmann wrote:
> The SPI controller in the arch/arm/boot/dts/armada-39x.dtsi file has moved
> to a different location in the hierarchy, which breaks the overrides
> in the board specific file:
>
> Warning (reg_format): "reg" property in
> /soc/internal-re
Depending on the kernel configuration, up to 3 syscall tables can be
used in parallel - so set the number properly to ensure syscall tracing
is set up properly.
Signed-off-by: Marcin Nowakowski
---
arch/mips/include/asm/unistd.h | 4
1 file changed, 4 insertions(+)
diff --git a/arch/mips/i
Syscall metadata makes an assumption that only a single syscall number
corresponds to a given method. This is true for most archs, but
can break tracing otherwise.
For MIPS platforms, depending on the choice of supported ABIs, up to 3
system call numbers can correspond to the same call - depending
1 - 100 of 712 matches
Mail list logo
