Tejun Heo tj at kernel.org writes:
On Mon, Sep 08, 2014 at 06:46:47PM -0500, Christoph Lameter wrote:
I already acked a patch like this today.
It isn't in my inbox.
It was [PATCH] x86, apic: Fix unmasked CPU initialization
http://www.spinics.net/lists/kernel/msg1820725.html
Sorry you
On Mon, Sep 8, 2014 at 10:27 PM, Feng Kan f...@apm.com wrote:
On Mon, Sep 8, 2014 at 1:52 AM, Arun Chandran achand...@mvista.com wrote:
Hi Feng,
Is this patch still needed to fix perf calltrace?
Yes, if the someone decide to run the secure mode of the GIC, which is
what is present in
the
On 09/08/2014 03:47 PM, Felipe Balbi wrote:
Hi,
On Mon, Sep 08, 2014 at 09:57:00AM +0200, Robert Baldyga wrote:
This patch introduces virtual endpoint address mapping. It separates
function logic form physical endpoint addresses making it more hardware
independent.
Following modifications
A few build issues have popped up with more extensive testing of the
patches to split the clock framework into a proper provider/consumer
relationship. [0]
The first patch adapts Intel's LPSS driver to use the clock provider
APIs. If no one objects to this patch then I will fold it into Tomeu's
Looks like this driver was missed during the original mass driver
rework[0]. This patch converts the LPSS driver to the new clock provider
data type (struct clk_core).
If there are no objections I propose to roll this patch into a rebase of
that patch[0] in my tree.
[0]
If CONFIG_COMMON_CLK is selected then __clk_get and __clk_put are
defined in drivers/clk/clk.c and declared in include/linux/clkdev.h.
Sylwester's series[0] to properly support clk_{get,put} in the common
clock framework made changes to the asm-specific clkdev.h headers, but
not the asm-generic
On 09/01/2014 01:35 PM, Marc Zyngier wrote:
On 01/09/14 15:57, Hanjun Guo wrote:
From: Tomasz Nowicki tomasz.nowi...@linaro.org
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver
Hi,
Yes, efifb has the same semantics. We just need some ID with clear
documentation saying sth like implies framebuffer without
anything else so that noone will get an idea to plug e.g. vga
hooks into it.
Want to make a patch?
Attached. Can someone test with the patched
Hi Juri,
On 09/08/2014 05:13 PM, Juri Lelli wrote:
thanks a lot for your patch. I'd actually have a slightly different fix
for the same problem. I'm actually baking a small patchset that I should
be able to release in the next few days. I'd say we could wait for that
to happen and then
On 09/03/2014 06:30 AM, Marc Zyngier wrote:
On 02/09/14 16:45, Hanjun Guo wrote:
This value is for max processors entries in MADT, and we will use it to scan
MADT
for SMP/GIC Init, I just make it big enough for GICv3/4. since ACPI core
will stop
scan MADT if the real numbers of processors
This patch introduces virtual endpoint address mapping. It separates
function logic form physical endpoint addresses making it more hardware
independent.
Following modifications changes user space API, so to enable them user
have to switch on the FUNCTIONFS_VIRTUAL_ADDR flag in descriptors.
Up to now, when endpoint addresses in descriptors were non-consecutive,
there were created redundant files, which could cause problems in kernel,
when user tried to read/write to them. It was result of fact that maximum
endpoint address was taken as total number of endpoints in funciton.
This
Hi Felipe,
I have finally prepated patchset that should apply and build with your
testing/next tree.
Best regards
Robert Baldyga
Changelog:
v8:
- add patch usb: gadget: f_fs: fix the redundant ep files problem to
make it possible to apply to Felipe tree
v7:
- return proper value from
This patch introduces ioctl named FUNCTIONFS_ENDPOINT_DESC, which
returns endpoint descriptor to userspace. It works only if function
is active.
Signed-off-by: Robert Baldyga r.bald...@samsung.com
Acked-by: Michal Nazarewicz min...@mina86.com
---
drivers/usb/gadget/function/f_fs.c | 23
On 09/05/14 at 10:11am, Kees Cook wrote:
I don't think this is correct. If you look at a02150610776 (x86,
relocs: Move ELF relocation handling to C), we always did relocations
on 32-bit when CONFIG_RELOCATABLE was set, so I think this will fail
badly on 32-bit. 64-bit only needs relocation
On Tue, Sep 9, 2014 at 11:02 AM, Anup Chenthamarakshan
an...@chromium.org wrote:
I had initially tried reusing cpufreq_stats.c to export stats.
Calling cpufreq_stats_update() via the cpufreq notifier added
some amount of overhead while switching frequencies. Specifically,
looking up the index
On 09/03/2014 10:57 AM, Arnd Bergmann wrote:
On Wednesday 03 September 2014 11:26:14 Tomasz Nowicki wrote:
In particular, the ACPI tables describing the irqchip have no way to
identify the GIC at all, if I read the spec correctly, you have to
parse the tables, ioremap the registers and then
On 09/03/2014 02:42 PM, Arnd Bergmann wrote:
On Monday 01 September 2014 22:57:51 Hanjun Guo wrote:
+ /* Collect CPU base addresses */
+ count = acpi_parse_entries(sizeof(struct acpi_table_madt),
+ gic_acpi_parse_madt_cpu, table,
+
Hello Kukjin,
On 09/09/2014 05:47 AM, kg...@kernel.org wrote:
Javier Martinez Canillas wrote:
Any comments on this series?
Looks good to me but I just wanted to get ack from chrome guy, Doug? But since
Naveen tested, it should be fine I think. I'll take the series.
Great, thanks!
Signed-off-by: Eli Billauer eli.billa...@gmail.com
---
MAINTAINERS | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index f040e7f..95bcdee 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8789,12 +8789,6 @@ M: Arnaud Patard
Hi to all,
I've installed new 3.16.2 kernel, and now:
- if I use an USB 3.0 cable I've same crash as said using 3.16.1 version;
- if I use an USB 2.0 cable works, I've made a complete backup without
any problem.
As told, tell me if I can help your works to determine how to resolve this bug.
On Mon, Sep 08, 2014 at 12:09:12PM -0700, H. Peter Anvin wrote:
Are you genuinely saying we shouldn't document this command line
parameter? Sorry, it really doesn't work that way.
My intent is to keep this one from getting abused for the wrong reasons.
Not documenting it is probably not going
On 29 August 2014 12:24, Alim Akhtar alim.akh...@samsung.com wrote:
There are upcoming ARM64 SoCs with dw_mmc host controller.
Signed-off-by: Alim Akhtar alim.akh...@samsung.com
---
drivers/mmc/host/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi Arnd,
On 09/03/2014 11:09 AM, Arnd Bergmann wrote:
On Wednesday 03 September 2014 01:00:23 Rafael J. Wysocki wrote:
Our intention is specifically not to use random incompatible bindings
in that. We'd rather have a common venue and process for establishing
new bindings for both DT and
At Mon, 8 Sep 2014 22:48:03 +0530,
Sudip Mukherjee wrote:
as pr_* macros are more preffered over printk, so printk replaced
with corresponding pr_* macros.
this patch will generate warning from checkpatch as it only did printk
replacement and didnot fixed other style issues.
Hm, this patchlet seems to be having trouble taking wing.
(tosses it up in the air.. flap yer little wings patchlet)
I thought you had changed the title to..
x86,cpu-hotplug: clear llc_shared_mask at CPU hotplug
..due to Peter saying sched is only a consumer, but v4 somehow reverted
back to
On Tue, 09 Sep, at 07:07:49AM, Ingo Molnar wrote:
So please only put the 3 regression fixes into efi-urgent, the
rest can go into the v3.18 pile.
OK, I'll sort that out.
--
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe
Hi,
On Tue, Sep 09, 2014 at 01:39:30PM +0800, Huang Ying wrote:
On Mon, 2014-09-08 at 22:23 -0700, Jaegeuk Kim wrote:
Hi Huang,
On Mon, Sep 08, 2014 at 07:38:26PM +0800, Huang Ying wrote:
For fsync, if the nid of a non-inode dnode nid of inode and the
inode is not checkpointed.
Hi Gleb,
On 09/03/2014 11:04 PM, Gleb Natapov wrote:
On Wed, Sep 03, 2014 at 09:42:30AM +0800, tangchen wrote:
Hi Gleb,
On 09/03/2014 12:00 AM, Gleb Natapov wrote:
..
+static void vcpu_reload_apic_access_page(struct kvm_vcpu *vcpu)
+{
+ /*
+* apic access page could be
On Mon, Sep 08, 2014 at 09:09:14PM +0200, Nitin Kuppelur wrote:
Hi Aaro,
Thanks for review. I will correct the commit log length and resend the patch.
About the __cvmx_usb_perform_complete():
Here return statement has associated label. Due to which it will add
compilation warning. So I am
On 09/09/2014 07:59 AM, Ingo Molnar wrote:
* Arnaldo Carvalho de Melo a...@kernel.org wrote:
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 39b5a56ec0be5effe9b7d0f18cb27724bf2e5d47:
Merge branch 'rfc/perf' into perf/core, because it's ready for
Hi Khiem-san,
On Tue, Sep 9, 2014 at 12:44 AM, Khiem Nguyen
khiem.nguyen...@renesas.com wrote:
+ - #address-cells: Must be 1,
+ - #address-cells: Must be 0.
Should it be #size-cells: Must be 0. ?
Yes, obviously. Thanks, will fix.
Gr{oetje,eeting}s,
Geert
On Tue 2014-09-09 00:52:55, Rafael J. Wysocki wrote:
On Monday, August 11, 2014 06:50:52 PM Lee, Chun-Yi wrote:
In arch/x86/kernel/setup.c::trim_bios_range(), the codes introduced
by 1b5576e6 (base on d8a9e6a5), it updates the first 4Kb of memory
to be E820_RESERVED region. That's because
Hi Mike,
On Tue, Sep 09, 2014 at 09:06:32AM +0200, Mike Galbraith wrote:
Hm, this patchlet seems to be having trouble taking wing.
(tosses it up in the air.. flap yer little wings patchlet)
I thought you had changed the title to..
x86,cpu-hotplug: clear llc_shared_mask at CPU hotplug
..due to
Hi all,
Changes since 20140908:
New trees: kselftest-fixes and kselftest
The v4l-dvb tree gained a build failure so I used the version from
next-20140908.
The wireless-next tree still had its build failure for which I applied
a suggested fix patch.
The drm tree still had its build failure for
On 2014-09-08 at 21:02:49 +0200, Adrian Nicoara anico...@uwaterloo.ca wrote:
Cleanup checkpatch.pl warnings.
Please state which warning this is fixing. Same goes for patches 1-3.
Signed-off-by: Adrian Nicoara anico...@uwaterloo.ca
---
Somehow I missed the comment Tobias made on the line
build is giving :
warning: passing argument 1 of 'strlen' makes pointer from integer
without a cast [enabled by default]
the snprintf after the strlen is trying to put the Unsupported string
at the end of exising string. so len should give the string length here
Signed-off-by: Sudip Mukherjee
On Mon, Sep 8, 2014 at 1:47 PM, Mika Westerberg
mika.westerb...@linux.intel.com wrote:
Some newer Intel SoCs like Braswell already have more than 256 GPIOs
available so the default limit is exceeded. In order to support these add
back the custom GPIO header with limit of 512 GPIOs for x86.
On Mon, Sep 08, 2014 at 07:26:57AM -0400, ext Jason Cooper wrote:
Matti,
On Mon, Sep 08, 2014 at 10:32:24AM +0300, Matti Vaittinen wrote:
---
Here. Otherwise, it'll get included in the commit message, which I
don't think was your intention.
Ok, thanks.
On Mon, Sep 08, 2014 at 03:02:49PM -0400, Adrian Nicoara wrote:
Cleanup checkpatch.pl warnings.
Signed-off-by: Adrian Nicoara anico...@uwaterloo.ca
---
Somehow I missed the comment Tobias made on the line indentation. I fixed the
patch, and added here as a reply - the previous patch
tasklet_kill clears TASKLET_STATE_SCHED bit. tasklet_action reconstructs
the tasklet_vec with TASKLET_STATE_SCHED bit cleared. But it does not
remove any tasklet_struct from tasklet_vec. tasklet_kill_immediate can
remove a tasklet_struct form tasklet_vec. But it can only run when CPU
state is
has been corrected in next-20140909.
thanks
sudip
--
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 09/08/2014 07:55 PM, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [140908 10:41]:
* Sebastian Andrzej Siewior bige...@linutronix.de [140905 12:03]:
This is my complete queue fo the omap serial driver based on the 8250 core
code. I played with it on beagle bone, am335x-evm and
Hi Kishon,
Thanks for reviewing :-)
+On STiH410, we have to use the DWC3 port#2 with a picoPHY to manage USB2
+devices. The USB2 Controller will use the ports #0 and #1.
+
+This is to document the DT parameters to be passed from the blob in that
case.
+
+Required properties:
+-
On Fri, Sep 05, 2014 at 05:15:43PM -0600, Bjorn Helgaas wrote:
Date: Fri, 5 Sep 2014 17:15:43 -0600
From: Bjorn Helgaas bhelg...@google.com
To: Chen, Gong gong.c...@linux.intel.com
Cc: rdun...@infradead.org, b...@alien8.de, tony.l...@intel.com,
linux-...@vger.kernel.org,
Hi Jacob,
I think it would have been nice to have CC'd Carlo Caione, the
original writer of the driver on this.
On Mon, Sep 08, 2014 at 03:24:04PM -0700, Jacob Pan wrote:
XPower AXP288 is a customized PMIC for Intel Baytrail-CR platforms. Similar
to AXP202/209, AXP288 comes with USB charger,
When trying to use the LED GPIO trigger with e.g. the PCA953x GPIO
driver, request_irq() fails with -EINVAL, because the GPIO driver
requires a nested interrupt handler.
Use request_any_context_irq() to be able to use any GPIO driver as LED
trigger.
Signed-off-by: Lothar Waßmann
These patches make it possible to use the ledtrig-gpio driver with
GPIO drivers that require threaded IRQs (like the PCA953x I2C driver).
It has been tested with a PCA9554 chip on an i.MX28 module.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Tue, Sep 09, 2014 at 01:43:46PM +0800, Huang Ying wrote:
On Mon, 2014-09-08 at 22:13 -0700, Jaegeuk Kim wrote:
Hi Huang,
On Mon, Sep 08, 2014 at 03:36:35PM +0800, huang ying wrote:
Hi, Jaegeuk,
On Mon, Sep 8, 2014 at 11:50 AM, Jaegeuk Kim jaeg...@kernel.org wrote:
Hi,
When using a GPIO driver whose accessor functions may sleep (e.g. an
I2C GPIO extender like PCA9554) the following warning is issued:
WARNING: CPU: 0 PID: 665 at drivers/gpio/gpiolib.c:2274
gpiod_get_raw_value+0x3c/0x48()
Modules linked in:
CPU: 0 PID: 665 Comm: kworker/0:2 Not tainted
Isn't this exactly what ida is for?
Sent from my tablet, pardon any formatting problems.
On Sep 9, 2014, at 0:24, Linus Walleij linus.wall...@linaro.org wrote:
On Mon, Sep 8, 2014 at 1:47 PM, Mika Westerberg
mika.westerb...@linux.intel.com wrote:
Some newer Intel SoCs like Braswell
I didn't look at it that hard since it claimed to be a sched patch. I
prioritize things in my inbox which say x86 for obvious reasons. Since I have
over 12,000 unread messages in my inbox alone...
Sent from my tablet, pardon any formatting problems.
On Sep 9, 2014, at 0:24, Wanpeng Li
Hi,
On 09/08/2014 06:55 PM, Dmitry Torokhov wrote:
ForcePads are found on HP EliteBook 1040 laptops. They lack any kind of
physical buttons, instead they generate primary button click when user
presses somewhat hard on the surface of the touchpad. Unfortunately they
also report primary button
On Tue, Sep 9, 2014 at 9:14 AM, Adrian Hunter adrian.hun...@intel.com wrote:
On 09/09/2014 07:59 AM, Ingo Molnar wrote:
* Arnaldo Carvalho de Melo a...@kernel.org wrote:
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit
On Fri, Sep 05, 2014 at 05:34:21PM -0600, Bjorn Helgaas wrote:
Date: Fri, 5 Sep 2014 17:34:21 -0600
From: Bjorn Helgaas bhelg...@google.com
To: Chen, Gong gong.c...@linux.intel.com
Cc: rdun...@infradead.org, b...@alien8.de, tony.l...@intel.com,
linux-...@vger.kernel.org,
This patch releases gpiochip related resources by calling
gpiochip_remove when gpiochip_irqchip_add fails.
CC: Srinivas Kandagatla srinivas.kandaga...@gmail.com
CC: Srinivas Kandagatla srinivas.kandaga...@linaro.com
CC: Maxime Coquelin maxime.coque...@st.com
CC: Patrice Chotard
For i2c devices in OF the modalias exposed to userspace is i2c:node
type, for the Maxtouch driver this is i2c:maxtouch.
Add maxtouch to the i2c id table such that userspace can correctly
load the module for the device and drop the OF table as it's not
needed for i2c devices.
Signed-off-by:
On 09/09/2014 10:45 AM, Stephane Eranian wrote:
On Tue, Sep 9, 2014 at 9:14 AM, Adrian Hunter adrian.hun...@intel.com wrote:
On 09/09/2014 07:59 AM, Ingo Molnar wrote:
* Arnaldo Carvalho de Melo a...@kernel.org wrote:
Hi Ingo,
Please consider pulling,
- Arnaldo
The following
Hi,
On 09/08/2014 06:39 PM, Kumar Gala wrote:
Add support for the Qualcomm AHCI SATA controller that exists on several
SoC and specifically the IPQ806x family of chips. The IPQ806x SATA support
requires the associated IPQ806x SATA PHY Driver to be enabled as well.
If I'm reading this driver
This patch releases gpiochip resources with of_gpiochip_remove
and gpiochip_remove in failure cases.
CC: John Crispin blo...@openwrt.org
CC: Linus Walleij linus.wall...@linaro.org
Signed-off-by: Pramod Gurav pramod.gu...@smartplayin.com
---
Changes since v1:
Dropped call to of_gpiochip_remove()
Hello Robert,
On Mon, Sep 08, 2014 at 04:11:19PM +0200, Robert Richter wrote:
From: Robert Richter rrich...@cavium.com
Fixing 32 bit compatibility by using ULL for u64 constants.
Signed-off-by: Robert Richter rrich...@cavium.com
---
drivers/irqchip/irq-gic-v3.c | 4 ++--
1 file
Subhransu S. Prusty wrote:
This is needed because the hardware
Which hardware? Every x86-64 CPU ever built by AMD, Intel, and VIA?
does not support 64-bit moveq insructions while writing to PCI MMIO.
+#ifndef CONFIG_X86_64
+#define MEMCPY_TOIO memcpy_toio
+#else
+#define MEMCPY_TOIO
This patch releases gpiochip resources with of_gpiochip_remove
and gpiochip_remove in failure cases.
CC: John Crispin blo...@openwrt.org
CC: Linus Walleij linus.wall...@linaro.org
Signed-off-by: Pramod Gurav pramod.gu...@smartplayin.com
---
Changes since v1:
Dropped call to of_gpiochip_remove()
Folks, this is a resend of the EFI urgent pull request from yesterday
with the non-regression-fixing patches dropped as Ingo requested. The
patches fix two regressions introduced during the merge window, and one
introduced in -rc2.
The following changes since commit
On Tue, 2014-09-09 at 00:41 -0700, Jaegeuk Kim wrote:
On Tue, Sep 09, 2014 at 01:43:46PM +0800, Huang Ying wrote:
On Mon, 2014-09-08 at 22:13 -0700, Jaegeuk Kim wrote:
Hi Huang,
On Mon, Sep 08, 2014 at 03:36:35PM +0800, huang ying wrote:
Hi, Jaegeuk,
On Mon, Sep 8, 2014
Am Freitag, 8. August 2014, 17:53:45 schrieb Heiko Stübner:
Am Freitag, 8. August 2014, 08:45:16 schrieb Doug Anderson:
Kever,
On Thu, Aug 7, 2014 at 8:55 PM, Kever Yang kever.y...@rock-chips.com
wrote:
rk3288 has two kind of usb controller, this add the dwc2 controller
for otg
Hi! Kent Overstreet, I tested bcache branch for jens:
http://evilpiepirate.org/git/linux-bcache.git/log/?h=for-jens
I have a question about buckets utilization, can you help me to resolve it?
This is the test fio cmd:
fio -name iops -rw=randwrite -iodepth=32 -numjobs=1 -filename=/dev/bcache0
On Mon, Sep 08, 2014 at 01:44:48PM +0200, Robert Richter wrote:
From: Robert Richter rrich...@cavium.com
Raising the current maximum limit to 64. This is needed for Cavium's
Thunder systems that will have at least 48 cores per die.
The change keeps the current memory footprint in cpu mask
Hi Jaegeuk,
Looks good to me!
One nitpick, how about judging this condition before we lock -i_mutex to
avoid unneeded lock contention and invoking of i_size_read()?
Thanks,
Yu
-Original Message-
From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
Sent: Tuesday, September 09, 2014 12:42 PM
On Monday 08 September 2014 19:27:14 H. Peter Anvin wrote:
On 09/08/2014 03:43 PM, James Bottomley wrote:
This was years ago (possibly decades). We had to implement in-kernel
unaligned traps for the networking layer because it could access short
and int fields that weren't of the
On Mon, 08 Sep 2014, Jacob Pan wrote:
More XPowers PMIC devices can be supported by extending this driver, so
rename it to axp2xx to cover axp288 variant.
Signed-off-by: Jacob Pan jacob.jun@linux.intel.com
---
drivers/mfd/Kconfig| 7 +-
drivers/mfd/Makefile | 2 +-
On Fri, 05 Sep 2014, Jaewon Kim wrote:
This patch add haptic of_compatible in order to use the haptic
device driver using Devicetree.
Signed-off-by: Jaewon Kim jaewon02@samsung.com
Acked-by: Chanwoo Choi cw00.c...@samsung.com
---
drivers/mfd/max77693.c |5 -
1 file changed,
On Wed, Aug 20, 2014 at 03:36:05PM +0300, Alexander Shishkin wrote:
When there's new data in the AUX space, output a record indicating its
offset and size and weather it was truncated to fix in the ring buffer.
This patch is too late; it should have been before the patch adding
On Mon, 08 Sep 2014, Octavian Purdila wrote:
On Mon, Sep 8, 2014 at 7:30 PM, Johan Hovold jo...@kernel.org wrote:
On Mon, Sep 08, 2014 at 06:57:29PM +0300, Octavian Purdila wrote:
On Mon, Sep 8, 2014 at 5:44 PM, Johan Hovold jo...@kernel.org wrote:
snip
Hi Johan,
Again, thanks
On 8 September 2014 18:22, Andrew Bresticker abres...@chromium.org wrote:
On Mon, Sep 8, 2014 at 8:34 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
On 2 September 2014 23:34, Andrew Bresticker abres...@chromium.org wrote:
Tested on Venice2, Jetson TK1, and Big with a variety of USB2.0 and
Am Freitag, 5. September 2014, 09:53:11 schrieb Doug Anderson:
From: huang lin h...@rock-chips.com
This adds basic SPI nodes to the base rk3288 device tree file.
A few notes:
* It's assumed that most users of the SPI ports are using chip select
0. Thus the default pinctrl for the ports
On 08/09/14 17:23, Russell King - ARM Linux wrote:
On Mon, Sep 08, 2014 at 04:28:35PM +0100, Daniel Thompson wrote:
@@ -604,8 +731,19 @@ static void gic_raise_softirq(const struct cpumask
*mask, unsigned int irq)
{
int cpu;
unsigned long flags, map = 0;
+unsigned long
On 08/09/14 17:24, Russell King - ARM Linux wrote:
On Mon, Sep 08, 2014 at 04:28:30PM +0100, Daniel Thompson wrote:
* Restructured to sit nicely on a similar FYI patchset from Russell
King. It now effectively replaces the work in progress final patch
with something much more complete.
Am Mittwoch, 3. September 2014, 16:05:23 schrieb Doug Anderson:
It's convenient (and less confusing to people reading logs) if the
eMMC port on rk3288 is consistenly marked with mmc0 and the sdmmc port
on rk3288 is consistently marked with mmc1. Add the appropriate
aliases.
Added to my
When using e.g. the matrix_keymap driver with the gpio-pca953x driver,
the following warning may be issued when a keypress is detected:
WARNING: CPU: 0 PID: 3 at kernel/irq/manage.c:677
irq_nested_primary_handler+0x18/0x2c()
Primary handler called for nested irq 245
Modules linked in: evbug
When trying to use the matrix-keypad driver with GPIO drivers that
require nested irq handlers (e.g. I2C GPIO adapters like PCA9554),
request_irq() fails because the GPIO driver requires a threaded
interrupt handler.
Use request_any_context_irq() to be able to use any GPIO driver as
keypad
On Wed, Aug 20, 2014 at 03:36:06PM +0300, Alexander Shishkin wrote:
This adds support for overwrite mode in the AUX area, which means keep
collecting data till you're stopped. It does not depend on data buffer's
overwrite mode, so that it doesn't lose sideband data that is instrumental
for
This patch fixes a typo which resulted in 'is never less
than zero warning' reported by static checker.
drivers/mmc/host/mmci_qcom_dml.c:131 dml_hw_init()
warn: unsigned 'producer_id' is never less than zero.
drivers/mmc/host/mmci_qcom_dml.c
121 /* Initialize the dml hardware
On 08/09/2014 21:37, Boris BREZILLON :
On Mon, 8 Sep 2014 21:22:18 +0200
Boris BREZILLON boris.brezil...@free-electrons.com wrote:
On Mon, 8 Sep 2014 19:33:38 +0200
Alexandre Belloni alexandre.bell...@free-electrons.com wrote:
On 03/09/2014 at 10:45:33 +0200, Boris Brezillon wrote :
The
Hi,
I have splitted my patchset usb: dwc2/gadget: fix series into two series.
This patch series contains fixes for dwc2/gadget driver. It's intended
for 3.17-final. I will also send this patches backported for stable.
Best regard
Robert Baldyga
Kamil Debski (2):
usb: dwc2/gadget: fix phy
Endpoint 0 should not be disabled, so we start loop counter from number 1.
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
index
From: Kamil Debski k.deb...@samsung.com
In the Generic PHY Framework a NULL phy is considered to be a valid phy
thus the if (hsotg-phy) check does not give us the information whether
the Generic PHY Framework is used.
In addition to the above this patch also removes phy_init from probe and
Because we have not enough memory to have each TX FIFO of size at least
3072 bytes (the maximum single packet size with 3 transactions per
microframe), we create four FIFOs of lenght 1024, and four of length
3072 bytes, and assing them to endpoints dynamically according to
maxpacket size value of
Hi,
I have splitted my patchset usb: dwc2/gadget: fix series into two series.
This patch series contains improvements for dwc2/gadget driver. It's intended
for 3.18.
Andrzej Pietrasiewicz (1):
usb: dwc2/gadget: Fix comment text
Kamil Debski (1):
usb: dwc2/gadget: move phy bus legth
Hi, Joerg,
The problem you describe here should also be fixed by this (simpler)
patch. Can you test this please?
The running result of this patch is correct.
My opinion is we should avoid modifying the original data
early_ioapic_map[i].devid and devid from IVHD since they are original data
From: Andrzej Pietrasiewicz andrze...@samsung.com
Adjust the debug text to the name of the printed variable.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1
When device is stopped or suspended clock is not needed so we
can disable it for this time.
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
index
On Tue, Sep 09, 2014 at 06:54:21AM +0100, Yijing Wang wrote:
on new requests. This function gets called quite a lot and I'm trying not
to
make it too heavy weight.
Generally, nothing should be accessing the same DT value frequently.
It should get cached somewhere.
The problem
From: Kamil Debski k.deb...@samsung.com
This patch moves the part of code that initializes the PHY bus width.
This results in simpler code and removes the need to check whether
the Generic PHY Framework is used.
Signed-off-by: Kamil Debski k.deb...@samsung.com
Signed-off-by: Marek Szyprowski
From: Marek Szyprowski m.szyprow...@samsung.com
Print warning if FIFOs are configured in such a way that they don't fit
into the SPRAM available on the s3c hsotg module.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
From: Marek Szyprowski m.szyprow...@samsung.com
Some DWC2/s3c-hsotg debug messages are really useless for typical user,
so hide them behind dev_dbg().
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
drivers/usb/dwc2/gadget.c | 4
On Wed, Aug 20, 2014 at 03:36:06PM +0300, Alexander Shishkin wrote:
diff --git a/kernel/events/ring_buffer.c b/kernel/events/ring_buffer.c
index 925f369947..5006caba63 100644
--- a/kernel/events/ring_buffer.c
+++ b/kernel/events/ring_buffer.c
@@ -294,9 +295,22 @@ void
On 09/09/2014 12:17 AM, Arnaldo Carvalho de Melo wrote:
Hi Ingo,
Please consider pulling,
- Arnaldo
I am very sorry Arnaldo but 2 patches are older versions, namely:
perf tools: Build programs to copy 32-bit compatibility VDSOs
perf tools: Add support for 32-bit
Hi Darren,
On Sat, 2014-09-06 at 23:17 +0200, Rafael J. Wysocki wrote:
On Friday, September 05, 2014 07:17:57 PM Darren Hart wrote:
On Thu, Sep 04, 2014 at 09:08:08AM +0200, Paul Bolle wrote:
[...]
static ssize_t store_sys_acpi(struct device *dev, int cm,
@@ -278,12 +276,13 @@ static
From: Marek Szyprowski m.szyprow...@samsung.com
This patch fixes kernel panic/interrupt storm/etc issues if bootloader
left s3c-hsotg module in enabled state. Now interrupt handler is enabled
only after proper configuration of hardware registers.
Signed-off-by: Marek Szyprowski
1 - 100 of 2114 matches
Mail list logo
