On (Mon) 07 Jul 2014 [11:23:52], Amit Shah wrote:
On (Sun) 06 Jul 2014 [21:41:47], Kees Cook wrote:
On Fri, Jul 4, 2014 at 10:34 PM, Amit Shah amit.s...@redhat.com wrote:
Commit d9e7972619334 hwrng: add randomness to system from rng sources
added a call to rng_get_data() from the
The size of the buffer program has been increased from 256 to 512 , 2ms maximum
timeout for do_write_buffer can not adapt to all the different vendor's
norflash.There maximum timeout information in the CFI area,so the best way is
to choose the result calculated according to timeout field of
On pią, 2014-07-04 at 22:24 +0200, Javier Martinez Canillas wrote:
The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms.
This patch adds support for the RTC and is based on a driver
added by Simon Glass to the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas
On pią, 2014-07-04 at 22:24 +0200, Javier Martinez Canillas wrote:
The MAX77686 RTC chip has two features called SMPL (Sudden Momentary
Power Loss) and WTSR (Watchdog Timeout and Software Resets).
Support for these features seems to be implemented in the driver but
compilation is disabled
On Sun, Jul 6, 2014 at 10:51 PM, Amit Shah amit.s...@redhat.com wrote:
On (Sun) 06 Jul 2014 [21:38:36], Kees Cook wrote:
On Fri, Jul 4, 2014 at 10:34 PM, Amit Shah amit.s...@redhat.com wrote:
The hwrng core asks for random data in the hwrng_register() call itself
from commit d9e7972619.
Hi Gleb,
Thanks for all the advices. Please see below.
On 07/04/2014 06:13 PM, Gleb Natapov wrote:
..
+static void vmx_set_apic_access_page_addr(struct kvm *kvm, hpa_t hpa)
+{
+ if (vm_need_virtualize_apic_accesses(kvm))
This shouldn't even been called if apic access page is not
Signed-off-by: xiaofeng.yan xiaofeng@huawei.com
---
kernel/sched/deadline.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index fc4f98b1..6541565 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@
Hi,
On Fri, Jul 4, 2014 at 10:10 PM, Mark Rutland mark.rutl...@arm.com wrote:
On Tue, Jun 24, 2014 at 07:44:10AM +0100, sundeep subbaraya wrote:
Ping
Thanks,
Sundeep.B.S.
On Tue, Jun 10, 2014 at 5:34 PM, subbaraya.sundeep.bha...@xilinx.com
wrote:
From: Subbaraya Sundeep Bhatta
On Tue, Jun 10, 2014 at 11:57:02PM +0900, Roman Pen wrote:
In case of reboot my olinuxino imx23 board does not see
mmc card any more. mmc_rescan is being called by delayed
work in loop, but mxs_mmc_get_cd always returns 0, so we
will never pass the card detection check and will not do
further
For many profiling tasks we need the callgraph. For example we often
need to see the caller of a lock or the caller of a memcpy or other
library function to actually tune the program. Frame pointer unwinding
is efficient and works well. But frame pointers are off by default on
64bit code (and on
Hi Felipe,
On Wed, Jul 2, 2014 at 10:16 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Sun, May 25, 2014 at 11:10:30PM +0530, sundeep subbaraya wrote:
Hi Felipe,
Please take a look at below about how this IP works:
IN:
req.buf --- DMA (transfers from ddr to IP buffer, raise DMA
done
If two tasks were both forked from the same parent task, Events in
their perf task contexts can be the same. Perf core may leave out
switching the perf event contexts.
Previous patch inroduces pmu specific data. The data is for saving
the LBR stack, it is task specific. So we need to switch the
make later patch more readable, no logic change.
Signed-off-by: Yan, Zheng zheng.z@intel.com
---
arch/x86/kernel/cpu/perf_event.c | 59
1 file changed, 29 insertions(+), 30 deletions(-)
diff --git a/arch/x86/kernel/cpu/perf_event.c
Haswell has a new feature that utilizes the existing Last Branch Record
facility to record call chains. When the feature is enabled, function
call will be collected as normal, but as return instructions are executed
the last captured branch record is popped from the on-chip LBR registers.
The LBR
If a task specific event wants user space callchain but does not want
branch stack sampling, enable the LBR call stack facility implicitly.
The LBR call stack facility can help perf to get user space callchain
in case of there is no frame pointer.
Note: this feature only affects how to get user
LBR callstack is designed for PEBS, It does not work well with
FREEZE_LBRS_ON_PMI for non PEBS event. If FREEZE_LBRS_ON_PMI is set for
non PEBS event, PMIs near call/return instructions may cause superfluous
increase/decrease of LBR_TOS.
This patch modifies __intel_pmu_lbr_enable() to not enable
Haswell has a new feature that utilizes the existing Last Branch Record
facility to record call chains. When the feature is enabled, function
call will be collected as normal, but as return instructions are executed
the last captured branch record is popped from the on-chip LBR registers.
The LBR
Zero length call uses the attribute of the call instruction to push
the immediate instruction pointer on to the stack and then pops off
that address into a register. This is accomplished without any matching
return instruction. It confuses the hardware and make the recorded call
stack incorrect.
event-attr.branch_sample_type is non-zero no matter branch stack
is enabled explicitly or is enabled implicitly. we can use it to
replace intel_pmu_needs_lbr_smpl(). This avoids duplicating code
that implicitly enables the LBR.
Signed-off-by: Yan, Zheng zheng.z@intel.com
---
When the LBR call stack is enabled, it is necessary to save/restore
the LBR stack on context switch. The solution is saving/restoring
the LBR stack to/from task's perf event context.
The LBR stack is saved/restored only when there are events that use
the LBR call stack. If no event uses LBR call
When the LBR call stack is enabled, it is necessary to save/restore
the LBR stack on context switch. We can use pmu specific data to
store LBR stack when task is scheduled out. This patch adds code
that allocates the pmu specific data.
Signed-off-by: Yan, Zheng zheng.z@intel.com
Reviewed-by:
When enabling/disabling an event, check if the event uses the LBR
callstack feature, adjust the LBR callstack usage count accordingly.
Later patch will use the usage count to decide if LBR stack should
be saved/restored.
Signed-off-by: Yan, Zheng zheng.z@intel.com
---
When enabling/disabling an event, check if the event uses the LBR
callstack feature, adjust the LBR callstack usage count accordingly.
Later patch will use the usage count to decide if LBR stack should
be saved/restored.
Signed-off-by: Yan, Zheng zheng.z@intel.com
---
When the LBR call stack is enabled, it is necessary to save/restore
the LBR stack on context switch. We can use pmu specific data to
store LBR stack when task is scheduled out. This patch adds code
that allocates the pmu specific data.
Signed-off-by: Yan, Zheng zheng.z@intel.com
Reviewed-by:
The index of lbr_sel_map is bit value of perf branch_sample_type.
PERF_SAMPLE_BRANCH_MAX is 1024 at present, so each lbr_sel_map uses
4096 bytes. By using bit shift as index, we can reduce lbr_sel_map
size to 40 bytes. This patch defines 'bit shift' for branch types,
and use 'bit shift' to define
Introduce a new flag PERF_ATTACH_TASK_DATA for perf event's attach
stata. The flag is set by PMU's event_init() callback, it indicates
that perf event needs PMU specific data.
The PMU specific data are initialized to zeros. Later patches will
use PMU specific data to save LBR stack.
Haswell has a new feature that utilizes the existing LBR facility to
record call chains. To enable this feature, bits (JCC, NEAR_IND_JMP,
NEAR_REL_JMP, FAR_BRANCH, EN_CALLSTACK) in LBR_SELECT must be set to 1,
bits (NEAR_REL_CALL, NEAR-IND_CALL, NEAR_RET) must be cleared. Due to
a hardware bug of
The callback is invoked when process is scheduled in or out.
It provides mechanism for later patches to save/store the LBR
stack. For the schedule in case, the callback is invoked at
the same place that flush branch stack callback is invoked.
So it also can replace the flush branch stack callback.
Previous commit introduces context switch callback, its function
overlaps with the flush branch stack callback. So we can use the
context switch callback to flush LBR stack.
This patch adds code that uses the flush branch callback to
flush the LBR stack when task is being scheduled in. The
On (Sun) 06 Jul 2014 [23:09:49], Kees Cook wrote:
On Sun, Jul 6, 2014 at 10:51 PM, Amit Shah amit.s...@redhat.com wrote:
On (Sun) 06 Jul 2014 [21:38:36], Kees Cook wrote:
On Fri, Jul 4, 2014 at 10:34 PM, Amit Shah amit.s...@redhat.com wrote:
The hwrng core asks for random data in the
please ignore this patch
On 07/07/2014 02:28 PM, Yan, Zheng wrote:
When the LBR call stack is enabled, it is necessary to save/restore
the LBR stack on context switch. We can use pmu specific data to
store LBR stack when task is scheduled out. This patch adds code
that allocates the pmu
please ignore this patch
On 07/07/2014 02:28 PM, Yan, Zheng wrote:
When enabling/disabling an event, check if the event uses the LBR
callstack feature, adjust the LBR callstack usage count accordingly.
Later patch will use the usage count to decide if LBR stack should
be saved/restored.
On (Mon) 07 Jul 2014 [11:34:58], Amit Shah wrote:
On (Mon) 07 Jul 2014 [11:23:52], Amit Shah wrote:
On (Sun) 06 Jul 2014 [21:41:47], Kees Cook wrote:
On Fri, Jul 4, 2014 at 10:34 PM, Amit Shah amit.s...@redhat.com wrote:
Commit d9e7972619334 hwrng: add randomness to system from rng
Hi all,
Changes since 20140704:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The net tree still had its build failure for which I reverted a commit.
The mvebu tree gained a conflict against the arm tree.
The renesas tree gained a conflict against
Guys, please pull the following fix from Ard that stops the arm64 EFI
stub being rebuilt on every arm64 kernel build by removing the
dependency on the generated header files.
The following changes since commit 783ee43118dc773bc8b0342c5b230e017d5a04d0:
efi-pstore: Fix an overflow on 32-bit
From: Roger Quadros rog...@ti.com
Some PHYs can be powered by an external power regulator.
e.g. USB_HS PHY on DRA7 SoC. Make the PHY core support a
power regulator.
Signed-off-by: Roger Quadros rog...@ti.com
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/phy/phy-core.c | 26
From: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Allow phy-exynos-usb2 to be autoloaded based on devicetree information.
Tested on Odroid X2 with its USB subsystem build as modules.
Signed-off-by: Sjoerd Simons sjoerd.sim...@collabora.co.uk
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
From: Roger Quadros rog...@ti.com
phy-supply is a phandle to the regulator that provides power to the
PHY. This regulator is managed during the PHY power on/off sequence
by the phy core driver.
Signed-off-by: Roger Quadros rog...@ti.com
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
From: Himangi Saraogi himangi...@gmail.com
devm_ioremap_resource returns an ERR_PTR value, not NULL, on failure.
A simplified version of the semantic match that finds this problem is as
follows:
// smpl
@@
expression e,e1;
statement S;
@@
*e = devm_ioremap_resource(...);
if (!e1) S
// /smpl
From: Roger Quadros rog...@ti.com
Prevent resources from being freed twice in case device_add() call
fails within phy_create(). Also use ida_simple_remove() instead of
ida_remove() as we had used ida_simple_get() to allocate the ida.
Signed-off-by: Roger Quadros rog...@ti.com
Signed-off-by:
From: Roger Quadros rog...@ti.com
If probe fails then we need to call pm_runtime_disable() to balance
out the previous pm_runtime_enable() call. Else it will cause
unbalanced pm_runtime_enable() call in the succeding probe call.
This anomaly was observed when the call to devm_phy_create() failed
Hi Greg,
Please find the pull requeust for 3.16 -rc cycle for PHY subsystem.
It contains few fixes in phy-core and few other PHY drivers. It also adds
regulatore support in PHY core which is needed to get USB and SATA working in
DRA7xx.
Please consider merging this for this -rc cylce. Let me
From: Kamil Debski k.deb...@samsung.com
The Exynos4412 USB 2.0 PHY hardware differs from the description provided
in the documentation. Some register bits have different function. This
patch fixes the defines of register bits and changes the way how phys are
powered on and off.
Signed-off-by:
From: Maxime Ripard maxime.rip...@free-electrons.com
The driver depend on the reset framework in a mandatory way. Make sure
reset_control_get is defined by adding this dependency in Kconfig
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
Reported-by: Arnd Bergmann a...@arndb.de
Hello Krzysztof,
On 07/07/2014 08:06 AM, Krzysztof Kozlowski wrote:
On pią, 2014-07-04 at 22:24 +0200, Javier Martinez Canillas wrote:
The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms.
This patch adds support for the RTC and is based on a driver
added by Simon Glass to the Chrome
From: Matwey V. Kornilov mat...@sai.msu.ru
Date: Wed, 25 Jun 2014 00:53:54 +0400
Subject: [PATCHv3 0/2] parport: parport_pc: Introduce option to disable
checking for Intel bug
Hi,
The following patch series is to deal with the issue on false-positives
of Intel EPP bug check [1].
More than a
From c89138e2c968c07dd11b3c6bfc05a803d0c5434d Mon Sep 17 00:00:00 2001
From: Matwey V. Kornilov matwey.korni...@gmail.com
Date: Wed, 25 Jun 2014 00:53:54 +0400
Subject: [PATCHv3 1/2] Introduce intel_bug_present function.
Put the code to check present of the Intel bug from parport_EPP_supported
From cf37d0cc4d51da5c0b368e1f5ab05082c041d1e1 Mon Sep 17 00:00:00 2001
From: Matwey V. Kornilov matwey.korni...@gmail.com
Date: Wed, 25 Jun 2014 01:08:45 +0400
Subject: [PATCHv3 2/2] Add force_epp module option for parport_pc.
The detection of Intel EPP bug is known to produce much false
Am Montag, 7. Juli 2014, 09:42:52 schrieb addy ke:
On Tue, Jul 01, 2014 at 09:03:59AM +0800, addy ke wrote:
+static const struct of_device_id rockchip_spi_dt_match[] = {
+ { .compatible = rockchip,rk3066-spi, },
+ { },
+};
+MODULE_DEVICE_TABLE(of, rockchip_spi_dt_match);
Your DT
Use standard debug features instead of relying on the custom
configuration option CONFIG_RTS5208_DEBUG and a series of home grown
macros.
Changes in v2:
* defined rtsx_hex_dump macro to produce output only if DEBUG is defined
Fabio Falzoi (4):
Staging: rts5208: Replace custom macro with
Fix an incorrect use of the %d format specifier in dev_err that caused a
warning.
Signed-off-by: Fabio Falzoi fabio.falzo...@gmail.com
---
drivers/staging/rts5208/rtsx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rts5208/rtsx.c
Use print_hex_dump_bytes to have memory properly dumped only when
DEBUG is defined.
Signed-off-by: Fabio Falzoi fabio.falzo...@gmail.com
---
drivers/staging/rts5208/ms.c| 4 ++--
drivers/staging/rts5208/rtsx_chip.c | 4 ++--
drivers/staging/rts5208/rtsx_scsi.c | 9 -
CONFIG_RTS5208_DEBUG is no more needed, we rely on dynamic debug config options
instead.
Signed-off-by: Fabio Falzoi fabio.falzo...@gmail.com
---
drivers/staging/rts5208/Kconfig | 7 ---
drivers/staging/rts5208/sd.c| 5 +
2 files changed, 1 insertion(+), 11 deletions(-)
diff --git
On Mon, Jul 07, 2014 at 09:42:52AM +0800, addy ke wrote:
The driver shouldn't be doing this, if it needs a delay it needs to
implement it itself. delay_usecs can be set by devices if they need a
delay between transfers, it should be in addition to the time taken for
the transfer to
On Mon, Jul 07, 2014 at 09:08:41AM +0200, Heiko Stübner wrote:
Am Montag, 7. Juli 2014, 09:42:52 schrieb addy ke:
Your DT binding defined some additional compatible strings, please add
those to the driver.
citing Mark Rutland (one of the dt maintainers):
--
That's why I said in
Am Montag, 7. Juli 2014, 08:21:40 schrieb Mark Brown:
On Mon, Jul 07, 2014 at 09:08:41AM +0200, Heiko Stübner wrote:
Am Montag, 7. Juli 2014, 09:42:52 schrieb addy ke:
Your DT binding defined some additional compatible strings, please add
those to the driver.
citing Mark Rutland
* Robert Nelson robertcnel...@gmail.com [140704 09:59]:
On Fri, Jul 4, 2014 at 11:51 AM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
On 07/03/2014 09:34 AM, Tony Lindgren wrote:
Heh. Just to summarize the reason ttyO needs to be a separate name
and device entry from ttyS is
On Friday 04 July 2014 15:26:12 Bjorn Helgaas wrote:
On Fri, Jul 04, 2014 at 09:55:20AM +0200, Federico Vaga wrote:
I assume these ports don't support hotplug. If they *did*
support
hotplug, those ports would have to exist because they handle the
hotplug events (presence detect,
On Fri, Jul 04 2014 at 3:54:14 pm BST, Alex Bennée alex.ben...@linaro.org
wrote:
For correct guest suspend/resume behaviour we need to ensure we include
the generic timer registers for 64 bit guests. As CONFIG_KVM_ARM_TIMER is
always set for arm64 we don't need to worry about null
Hi,
On Tue, Nov 12, 2013 at 6:33 PM, Steven J. Hill steven.h...@imgtec.com wrote:
Imagination Technologies is pleased to announce the release of its 3.10 LTS
(Long-Term Support) MIPS kernel. The changelog below is based off the stable
Linux 3.10.14 release done by Greg Kroah-Hartman in commit
At Sat, 05 Jul 2014 13:02:02 -0700,
Joe Perches wrote:
print_nid_path has a possible buffer overflow if
struct nid_path.path values are 256.
Avoid this and neaten the output to remove the leading ':'
Neaten debug_badness to always verify arguments.
Signed-off-by: Joe Perches
Some machines'(E,G Lenovo Z480) ECs are not stable during boot up
and causes battery driver fails to be loaded due to failure of getting
battery information from EC sometimes. After several retries, the
operation will work. This patch is to retry to get battery information 5
times if the first try
On Thu, Jul 03, 2014 at 11:15:21PM +0200, Rickard Strandqvist wrote:
diff --git a/drivers/video/fbdev/sis/init.c b/drivers/video/fbdev/sis/init.c
index bd40f5e..9e2dd96 100644
--- a/drivers/video/fbdev/sis/init.c
+++ b/drivers/video/fbdev/sis/init.c
@@ -355,12 +355,12 @@ SiS_GetModeID(int
2014-07-07 0:42 GMT+03:00 Eric Dumazet eric.duma...@gmail.com:
/* Queue packet (standard) */
+ sock_hold(sock);
+ skb-destructor = atalk_skb_destructor;
skb-sk = sock;
This part is not needed : sock_queue_rcv_skb() already does the right
thing : It calls
On Thu, Jul 03, 2014 at 11:24:35AM -0500, Dan Murphy wrote:
+static int tas2552_power(struct tas2552_data *data, u8 power)
+{
+ int ret = 0;
+
+ mutex_lock(data-mutex);
+
+ if (power) {
+ if (data-enable_gpio)
+
Signed-off-by: Cristian Stoica cristian.sto...@freescale.com
---
Documentation/driver-model/devres.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/driver-model/devres.txt
b/Documentation/driver-model/devres.txt
index 1525e30..7a48896 100644
---
* Nicholas Krause xerofo...@gmail.com [140704 10:03]:
This patch fixes the call to ompa_cfg_reg(USB2_SPEED) in the case
that the cpu is a omap16xx and the nwires are not equal to 3.
This is most likely unsafe to do as the pin is probably
shared with some other device and we have to rely for
the
On Mon, Jul 07, 2014 at 11:28:53AM +1000, Stephen Rothwell wrote:
diff --cc arch/arm/mach-mvebu/headsmp-a9.S
index 7c91ddb6f1f7,da5bb292b91c..
--- a/arch/arm/mach-mvebu/headsmp-a9.S
+++ b/arch/arm/mach-mvebu/headsmp-a9.S
@@@ -14,8 -14,9 +14,10 @@@
#include linux/linkage.h
On Sat, Jun 28, 2014 at 02:44:09PM +0200, Fabian Frederick wrote:
Cc: Johan Hovold jhov...@gmail.com
Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
Cc: linux-...@vger.kernel.org
Signed-off-by: Fabian Frederick f...@skynet.be
Applied, thanks.
Johan
---
drivers/usb/serial/mos7840.c | 5
2014-07-04 오후 4:57, Joonsoo Kim 쓴 글:
If pageblock of page on pcp are isolated now, we should free it to isolate
buddy list to prevent future allocation on it. But current code doesn't
do this.
I think it is strage that pcp can have isolated page.
I remember that The purpose of pcp is having
From: Joe Perches
Because gcc issues a complaint about any pointer format with %#p,
remove the use of SPECIAL to prefix 0x to various pointer types.
There are no uses in the kernel tree of %#p.
I know you guys don't really care about them, but there might
be uses in out of tree drivers.
Hi Guenter,
On Sun, 6 Jul 2014 20:55:12 -0700, Guenter Roeck wrote:
SMBus block commands are different to I2C block commands since
the returned data is not normally accessible with byte or word
commands on other command offsets. Add linked list of 'block'
commands to support those commands.
* Roger Quadros rog...@ti.com [140704 02:57]:
After clarification from the hardware team it was found that
this 1.8V PHY supply can't be switched OFF when SoC is Active.
Since the PHY IPs don't contain isolation logic built in the design to
allow the power rail to be switched off, there is a
On Fri, Jun 27, 2014 at 02:50:11PM +0200, and...@mail.sth.sze.hu wrote:
From: Andras Kovacs and...@sth.sze.hu
Corsair USB Dongles are shipped with Corsair AXi series PSUs.
These are cp210x serial usb devices, so make driver detect these.
I have a program, that can get information from these
* Roger Quadros rog...@ti.com [140704 02:58]:
The ldousb_reg regulator provides power to the USB1 and USB2
High Speed PHYs.
Signed-off-by: Roger Quadros rog...@ti.com
This too:
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/boot/dts/dra7-evm.dts | 8
1 file changed, 8
On Sun, Jul 06, 2014 at 01:27:37PM -0400, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following spew:
[10062.200152] BUG: spinlock recursion on CPU#11, trinity-c194/2414
[10062.201897] lock:
On Tue, Jun 24, 2014 at 07:27:14PM +0530, Varun Sethi wrote:
This patch set contains fixes for the PAMU driver.
The patches are based on 3.16-rc1.
Varun Sethi (3):
Fix PAMU window size check.
Fix the device domain attach condition.
Fix the error condition during iommu group
Currently map_vm_area() takes (struct page *** pages) as third argument,
and after mapping, it moves (*pages) to point to (*pages + nr_mappped_pages).
It looks like this kind of increment is useless to its caller these
days. The callers don't care about the increments and actually they're
trying
On Wed, Jul 02, 2014 at 12:36:48PM +0300, Bernd Wachter wrote:
Add ID of the Telewell 4G v2 hardware to option driver to get legacy
serial interface working
Signed-off-by: Bernd Wachter bernd.wach...@jolla.com
Applied, thanks.
Johan
---
---
Hi Tony,
On 07/07/2014 11:29 AM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [140704 02:57]:
After clarification from the hardware team it was found that
this 1.8V PHY supply can't be switched OFF when SoC is Active.
Since the PHY IPs don't contain isolation logic built in the design
On 06/10/14 07:30, Konrad Rzeszutek Wilk wrote:
On Thu, Jun 05, 2014 at 11:43:14AM -0700, Matt Rushton wrote:
Instead of ballooning up and down dom0 memory this remaps the existing mfns
that were replaced by the identity map. The reason for this is that the
existing implementation ballooned
On Fri, Jun 27, 2014 at 03:37:16PM +0200, Jiri Kosina wrote:
On Thu, 26 Jun 2014, Pavel Machek wrote:
Ok, so I have set up machines for ktest / autobisect, and found out that
3.16-rc1 no longer has that problem. Oh well, bisect would not be fun,
anyway...
I am still seeing the
On Fri, Jun 27, 2014 at 09:03:12AM +0200, Thierry Reding wrote:
From: Thierry Reding tred...@nvidia.com
This structure is read-only data and should never be modified.
Signed-off-by: Thierry Reding tred...@nvidia.com
---
Changes in v2:
- add missing hunk from include/device.h
Hi Will,
On Fri, Jun 27 2014 at 2:10:18 pm BST, Will Deacon will.dea...@arm.com wrote:
Hi Marc,
On Wed, Jun 25, 2014 at 10:28:43AM +0100, Marc Zyngier wrote:
When a peripheral is shared between virtual machines, its interrupt
state becomes part of the guest's state, and must be switched
On Fri, Jul 04, 2014 at 12:02:21PM +, xiaofeng.yan wrote:
It could be wrong for the precision of runtime and deadline
when the precision is within microsecond level. For example:
Task runtime deadline period
P1 200us 500us 500us
This case need enbale HRTICK feature by the next
Paul,
On 07/06/2014 03:23 AM, Paul Walmsley wrote:
Hi
On Fri, 4 Jul 2014, Roger Quadros wrote:
On 07/03/2014 10:48 PM, Paul Walmsley wrote:
On Thu, 3 Jul 2014, Roger Quadros wrote:
This module is needed for the SATA and PCIe PHYs.
Signed-off-by: Roger Quadros rog...@ti.com
* Roger Quadros rog...@ti.com [140707 01:36]:
Hi Tony,
On 07/07/2014 11:29 AM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [140704 02:57]:
After clarification from the hardware team it was found that
this 1.8V PHY supply can't be switched OFF when SoC is Active.
Since the PHY
On Sun, Jul 06, 2014 at 08:56:07PM -0400, Bandan Das wrote:
[...]
How about revert commit b6b8a1451 and try if the bug which you mentioned
is still there?
Sorry, didn't get time at all to look at this over the weekend but thought of
putting down what I have so far..
So, as mentioned in
On Mon, Jun 30, 2014 at 07:59:55AM +0100, Chris Wilson wrote:
On Sat, Jun 28, 2014 at 11:55:19PM -0400, Ed Tomlinson wrote:
On Saturday 28 June 2014 15:28:22 Ed Tomlinson wrote:
Resend without html krud which causes list to bounce the message.
Hi
This commit (
On Fri, Jul 04, 2014 at 03:54:14PM +0100, Alex Bennée wrote:
For correct guest suspend/resume behaviour we need to ensure we include
the generic timer registers for 64 bit guests. As CONFIG_KVM_ARM_TIMER is
always set for arm64 we don't need to worry about null implementations.
However I have
ION need HAS_DMA (e.g. need DMA_SHARED_BUFFER), so it has to depend on
HAS_DMA, or can not pass compiling with allmodconfig under score which
NO_DMA. And the related error:
CC drivers/staging/android/ion/ion_cma_heap.o
drivers/staging/android/ion/ion_cma_heap.c: In function
On 06/10/14 07:30, Konrad Rzeszutek Wilk wrote:
On Thu, Jun 05, 2014 at 11:43:14AM -0700, Matt Rushton wrote:
Instead of ballooning up and down dom0 memory this remaps the existing mfns
that were replaced by the identity map. The reason for this is that the
existing implementation ballooned
This patch fixes a memory leak that appears when caam_jr module is unloaded.
Cc: sta...@vger.kernel.org # 3.13+
Signed-off-by: Cristian Stoica cristian.sto...@freescale.com
---
drivers/crypto/caam/jr.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git
Hi Linus,
here are two pin control fixes for v3.16. I'm a bit snowed under
by mail but these have boiled in linux-next and should propagate
to you.
Please pull them in!
Yours,
Linus Walleij
The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
Linux 3.16-rc1
On Sun, Jun 01, 2014 at 11:31:17AM +0200, Johan Hovold wrote:
On Sat, May 31, 2014 at 01:03:00PM -0300, Peter Senna Tschudin wrote:
This patch remove the function klsi_105_tiocmset which was only
returning -EINVAL. It also removes the function prototype and
the .tiocmset entry in the struct
Thanks Joerg.
-Original Message-
From: Joerg Roedel [mailto:j...@8bytes.org]
Sent: Monday, July 07, 2014 2:02 PM
To: Sethi Varun-B16395
Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org;
linuxppc-...@lists.ozlabs.org; alex.william...@redhat.com
Subject: Re: [PATCH
On Mon, 2014-07-07 at 11:03 +0300, Andrey Utkin wrote:
2014-07-07 0:42 GMT+03:00 Eric Dumazet eric.duma...@gmail.com:
/* Queue packet (standard) */
+ sock_hold(sock);
+ skb-destructor = atalk_skb_destructor;
skb-sk = sock;
This part is not needed :
On Wed, Jun 25, 2014 at 08:44:35PM +0200, Jiri Olsa wrote:
From: Jiri Olsa jo...@redhat.com
While iterating siblings in perf_output_read_group we could
race with addition and removal of sibling in perf_group_attach
and perf_group_detach respective.
So why would anybody do this?
While in
The workqueue retry_unthrottle_workqueue is not scheduled anywhere
in the code. So, remove it.
Signed-off-by: Olivier Sobrie oliv...@sobrie.be
---
drivers/net/usb/hso.c | 12
1 file changed, 12 deletions(-)
diff --git a/drivers/net/usb/hso.c b/drivers/net/usb/hso.c
index
When the module sends bursts of data, sometimes a deadlock happens in
the hso driver when the tty buffer doesn't get the chance to be flushed
quickly enough.
To avoid this, first, we remove the endless while loop in
put_rx_bufdata() which is the root cause of the deadlock.
Secondly, when there is
1 - 100 of 2228 matches
Mail list logo
