[PATCH 15/15] arm64: remove ununsed set_irq_flags

Now that all users of set_irq_flags and custom flags are converted to genirq functions, the ARM specific set_irq_flags can be removed. Signed-off-by: Rob Herring Cc: Catalin Marinas Cc: Will Deacon Cc: linux-arm-ker...@lists.infradead.org --- arch/arm64/include/asm/hardirq.h | 5 - 1 file

[git pull] Input updates for 4.1-rc7

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive a small tweak for Synaptics PS/2 touchpad driver. Changelog: - Peter Hutterer (1): Input: synaptics - add min/max quirk for Lenovo S540 Diffstat: dri

Re: [PATCH V2] regulator: core: fix constraints debug output

> Mark Brown hat am 9. Juni 2015 um 20:00 geschrieben: > > > On Wed, Jun 03, 2015 at 09:56:29PM +, Stefan Wahren wrote: > > The line buffer for constraints debug isn't big enough to hold the output > > in all cases. So fix the possible buffer overflow by the usage of the > > scnprintf(). > >

[PATCH 01/15] ARM: kill off set_irq_flags usage

set_irq_flags is ARM specific with custom flags which have genirq equivalents. Convert drivers to use the genirq interfaces directly, so we can kill off set_irq_flags. The translation of flags is as follows: IRQF_VALID -> !IRQ_NOREQUEST IRQF_PROBE -> !IRQ_NOPROBE IRQF_NOAUTOEN -> IRQ_NOAUTOEN For

[PATCH 02/15] regmap: kill off set_irq_flags usage

set_irq_flags is ARM specific with custom flags which have genirq equivalents. Convert drivers to use the genirq interfaces directly, so we can kill off set_irq_flags. The translation of flags is as follows: IRQF_VALID -> !IRQ_NOREQUEST IRQF_PROBE -> !IRQ_NOPROBE IRQF_NOAUTOEN -> IRQ_NOAUTOEN For

Re: [RFC PATCH] sched: Fix sched_wakeup tracepoint

- On Jun 9, 2015, at 11:13 AM, Peter Zijlstra pet...@infradead.org wrote: > So how about we introduce the 'waking' tracepoint and leave the existing > wakeup one in place and preserve its woken semantics. That would work for me, but leaves me wondering how you would move to the new 'woken' na

Re: [PATCH 03/15] clk: kill off set_irq_flags usage

On Tue, 9 Jun 2015 13:26:29 -0500 Rob Herring wrote: > set_irq_flags is ARM specific with custom flags which have genirq > equivalents. Convert drivers to use the genirq interfaces directly, so we > can kill off set_irq_flags. The translation of flags is as follows: > > IRQF_VALID -> !IRQ_NOREQ

Re: [PATCH v6 1/3] ARM: rockchip: fix the CPU soft reset

Caesar, On Tue, Jun 9, 2015 at 2:49 AM, Caesar Wang wrote: > We need different orderings when turning a core on and turning a core > off. In one case we need to assert reset before turning power off. > In ther other case we need to turn power on and the deassert reset. > > In general, the correc

Re: [PATCH v2 3/4] x86, mwaitt: introduce mwaix delay with a configurable timer

On Tue, Jun 09, 2015 at 10:55:15AM -0700, Andy Lutomirski wrote: > When I looked at the rdtsc ordering a couple years ago, I thought > about what it meant for rdtsc to be properly ordered. I decided that > proper rdtsc ordering meant that no one should ever be able to tell if > rdtsc ends up reord

Re: [PATCH v6] procfs: Always expose /proc//map_files/ and make it readable

On Tue, Jun 09, 2015 at 10:47:31AM -0700, Andy Lutomirski wrote: ... > > > > Cool, I think this looks good. Thanks! > > > > Reviewed-by: Kees Cook > > > > Looks good to me, too. Wow! Great job, Calvin, thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body

Re: [PATCH v5 18/21] nd_btt: atomic sector updates

On Tue, 2015-06-09 at 08:44 +0200, Christoph Hellwig wrote: > I really want to see a good explanation why this is not a blk-mq driver > given that it does fairly substantial work and has synchronization > in its make_request function. The biggest reason, I think, is that the BTT (just like pmem, b

Re: [PATCH] i2c: designware: use enable on resume instead initialization

Hi Mika, On Tue, Jun 9, 2015 at 5:51 AM, Mika Westerberg wrote: > On Mon, Jun 08, 2015 at 02:50:28PM -0300, lucas.de.mar...@gmail.com wrote: >> From: Fabio Mello >> >> According to documentation and tests, initialization is not >> necessary on module resume, since the controller keeps its state

[PATCH 09/15] mfd: kill off set_irq_flags usage

set_irq_flags is ARM specific with custom flags which have genirq equivalents. Convert drivers to use the genirq interfaces directly, so we can kill off set_irq_flags. The translation of flags is as follows: IRQF_VALID -> !IRQ_NOREQUEST IRQF_PROBE -> !IRQ_NOPROBE IRQF_NOAUTOEN -> IRQ_NOAUTOEN For

[PATCH 07/15] irqchip: kill off set_irq_flags usage

set_irq_flags is ARM specific with custom flags which have genirq equivalents. Convert drivers to use the genirq interfaces directly, so we can kill off set_irq_flags. The translation of flags is as follows: IRQF_VALID -> !IRQ_NOREQUEST IRQF_PROBE -> !IRQ_NOPROBE IRQF_NOAUTOEN -> IRQ_NOAUTOEN For

Re: [PATCH v2 1/2] ARM: Add cpu_resume_arm() for firmwares that resume in ARM state

On 06/09/2015 08:29 AM, Russell King - ARM Linux wrote: > > Stephen, if you can arrange for the patch to end up in the patch system > please... > Sure no problem. The patch is 8389/1 in the tracker. I also fixed the commit text. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Foru

Re: [PATCH v5 2/2] ASoC: qcom: add apq8016 sound card support

On 09/06/15 19:04, Mark Brown wrote: On Tue, Jun 09, 2015 at 06:51:59PM +0100, Srinivas Kandagatla wrote: On 09/06/15 18:07, Mark Brown wrote: Why not just do these one time at probe, we don't undo them when we shut the DAI down? If I do that Am afraid that the driver would loose the fle

[PATCH 10/15] PCI: kill off set_irq_flags usage

set_irq_flags is ARM specific with custom flags which have genirq equivalents. Convert drivers to use the genirq interfaces directly, so we can kill off set_irq_flags. The translation of flags is as follows: IRQF_VALID -> !IRQ_NOREQUEST IRQF_PROBE -> !IRQ_NOPROBE IRQF_NOAUTOEN -> IRQ_NOAUTOEN For

Re: [Question] ksm: rmap_item pointing to some stale vmas

On 4/30/2015 11:37 AM, Susheel Khiani wrote: But if I've misunderstood, and you think that what you're seeing fits with the transient forking bugs I've (not quite) described, and you can explain why even the transient case is important for you to have fixed, then I really ought to redouble my eff

[PATCH 12/15] SH: kill off set_irq_flags usage

set_irq_flags is ARM specific with custom flags which have genirq equivalents. Convert drivers to use the genirq interfaces directly, so we can kill off set_irq_flags. The translation of flags is as follows: IRQF_VALID -> !IRQ_NOREQUEST IRQF_PROBE -> !IRQ_NOPROBE IRQF_NOAUTOEN -> IRQ_NOAUTOEN For

Re: [PATCH v2 3/4] x86, mwaitt: introduce mwaix delay with a configurable timer

On Tue, Jun 9, 2015 at 10:13 AM, Peter Zijlstra wrote: > On Tue, 2015-06-09 at 09:46 -0700, Andy Lutomirski wrote: >> On Jun 9, 2015 2:30 AM, "Peter Zijlstra" wrote: > >> > How about you think instead and do something like: >> > >> > rdtsc(start); >> > rdtsc_barrier(); >> >> Other

[PATCH 04/15] dma: kill off set_irq_flags usage

set_irq_flags is ARM specific with custom flags which have genirq equivalents. Convert drivers to use the genirq interfaces directly, so we can kill off set_irq_flags. The translation of flags is as follows: IRQF_VALID -> !IRQ_NOREQUEST IRQF_PROBE -> !IRQ_NOPROBE IRQF_NOAUTOEN -> IRQ_NOAUTOEN For

[PATCH 11/15] pinctrl: kill off set_irq_flags usage

set_irq_flags is ARM specific with custom flags which have genirq equivalents. Convert drivers to use the genirq interfaces directly, so we can kill off set_irq_flags. The translation of flags is as follows: IRQF_VALID -> !IRQ_NOREQUEST IRQF_PROBE -> !IRQ_NOPROBE IRQF_NOAUTOEN -> IRQ_NOAUTOEN For

[PATCH 00/15] Kill off set_irq_flags

This series converts all users of ARM specific set_irq_flags to use common genirq functions. In many cases where irqdomains are used, the set_irq_flags calls were redundant, so I've removed them. This is not intended for 4.2, but if any subsystem maintainers want to pick up their subsystem's chang

[PATCH 06/15] gpu/drm: kill off set_irq_flags usage

set_irq_flags is ARM specific with custom flags which have genirq equivalents. Convert drivers to use the genirq interfaces directly, so we can kill off set_irq_flags. The translation of flags is as follows: IRQF_VALID -> !IRQ_NOREQUEST IRQF_PROBE -> !IRQ_NOPROBE IRQF_NOAUTOEN -> IRQ_NOAUTOEN For

Re: [PATCH v2 3/4] VFIO: platform: populate the reset function on probe

On Fri, 2015-06-05 at 17:06 +0200, Eric Auger wrote: > The reset function lookup happens on vfio-platform probe. The reset > module load is requested and a reference to the function symbol is > hold. The reference is released on vfio-platform remove. > > Signed-off-by: Eric Auger > > --- > > v

Re: [PATCH v2 1/4] VFIO: platform: add reset struct and lookup table

On Fri, 2015-06-05 at 17:06 +0200, Eric Auger wrote: > This patch introduces the vfio_platform_reset_combo struct that > stores all the information useful to handle the reset modality: > compat string, name of the reset function, name of the module that > implements the reset function. A lookup tab

Re: [PATCH v6 3/3] ARM: rockchip: fix the SMP code style

Caesar, On Tue, Jun 9, 2015 at 2:49 AM, Caesar Wang wrote: > Use the below scripts to check: > scripts/checkpatch.pl -f --subject arch/arm/mach-rockchip/platsmp.c > > Signed-off-by: Caesar Wang > > --- > > Changes in v6: > - fix the commnet Unified format. > Series-changes: 5 > - Add the changel

clustered MD

I've just noticed the existence of clustered MD for the first time. It is a major new user of the dlm, and I have some doubts about it. When did this appear on the mailing list for review? Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to m

Re: [PATCH v6 2/3] ARM: rockchip: ensure CPU to enter WFI/WFE state

Caesar, On Tue, Jun 9, 2015 at 2:49 AM, Caesar Wang wrote: > The patch can ensure that v7_exit_coherency_flush() in rockchip_cpu_die() > executed in time. > The mdelay(1) has enough time to fix the problem of CPU offlining. > That's a workaround way in rockchip hotplug code, > At least, we haven'

Re: [PATCH v2 0/8] Goodix touchscreen enhancements

On Mon, Jun 08, 2015 at 05:37:45PM +0300, Irina Tirdea wrote: > Add several enhancements to the Goodix touchscreen driver: > - write configuration data to the device > - power management support > - cleanup and refactoring > > I have kept the original patch for ESD ("input: goodix: add support

Re: [PATCH v2 6/8] input: goodix: add power management support

On Mon, Jun 08, 2015 at 05:37:51PM +0300, Irina Tirdea wrote: > Implement suspend/resume for goodix driver. > > This is based on Goodix datasheets for GT911 and GT9271 > and on Goodix driver gt9xx.c for Android (publicly available > in Android kernel trees for various devices). > > Signed-off-by:

randconfig build error with next-20150609, in drivers/misc/mic/scif/scif_rb.c

Building with the attached random configuration file, drivers/misc/mic/scif/scif_rb.c: In function ‘scif_rb_write’: drivers/misc/mic/scif/scif_rb.c:115:11: error: ‘ENOMEM’ undeclared (first use in this function) return -ENOMEM; ^ drivers/misc/mic/scif/scif_rb.c:115:11: note: each un

Re: [PATCH v2 5/8] input: goodix: write configuration data to device

Hi Irina, On Mon, Jun 08, 2015 at 05:37:50PM +0300, Irina Tirdea wrote: > Goodix devices can be configured by writing custom data to the device at > init. The configuration data is read with request_firmware from > "goodix__cfg.bin", where is the product id read from the device > (e.g.: goodix_91

Re: [PATCH v6] procfs: Always expose /proc//map_files/ and make it readable

On Tue, Jun 9, 2015 at 10:27 AM, Kees Cook wrote: > On Mon, Jun 8, 2015 at 8:39 PM, Calvin Owens wrote: >> Currently, /proc//map_files/ is restricted to CAP_SYS_ADMIN, and >> is only exposed if CONFIG_CHECKPOINT_RESTORE is set. >> >> This interface very useful because it allows userspace to stat(

Re: [PATCH v11 4/5] x86/earlyprintk: setup earlyprintk as early as possible

2015-06-09 23:00 GMT+06:00 Andy Shevchenko : > > I'm still not convincing by this code to be in that form and here. What > about to refactor setup_early_printk() to helper which will do parse > parameters to a let say structure where one of the flag will be > struct early_printk_param { > … > const

Re: [PATCH] block: Make CFQ default to IOPS mode on SSDs

On 06/09/2015 04:18 AM, Romain Francoise wrote: Hi, On Tue, May 19, 2015 at 01:55:21PM -0700, Tahsin Erdogan wrote: --- a/block/cfq-iosched.c +++ b/block/cfq-iosched.c @@ -4460,7 +4460,7 @@ static int cfq_init_queue(struct request_queue *q, struct elevator_type *e) cfqd->cfq_slice[1] =

Re: [PATCH v11 3/5] x86/earlyprintk: Allocate early log_buf as early as possible

On Tue, Jun 09, 2015 at 06:58:52PM +0300, Andy Shevchenko wrote: >> On Tue, 2015-06-09 at 17:11 +0600, Alexander Kuleshov wrote: >> > This patch moves call of the early setup_log_buf from the >> > arch/x86/kernel/setup.c to the arch/x86/kernel/head{32,64}.c >> > and updates log_buf with the earlypr

Re: [PATCH v5 2/2] ASoC: qcom: add apq8016 sound card support

On Tue, Jun 09, 2015 at 06:51:59PM +0100, Srinivas Kandagatla wrote: > On 09/06/15 18:07, Mark Brown wrote: > >Why not just do these one time at probe, we don't undo them when we shut > >the DAI down? > If I do that Am afraid that the driver would loose the flexibility of > selecting different MI

Re: [PATCH V2] regulator: core: fix constraints debug output

On Wed, Jun 03, 2015 at 09:56:29PM +, Stefan Wahren wrote: > The line buffer for constraints debug isn't big enough to hold the output > in all cases. So fix the possible buffer overflow by the usage of the > scnprintf(). If we know how much output we might produce then why not extend the buff

Re: [PATCH v5 1/2] arm64: kvm: allows kvm cpu hotplug

Hi Takahiro, On 29/05/15 06:38, AKASHI Takahiro wrote: > The current kvm implementation on arm64 does cpu-specific initialization > at system boot, and has no way to gracefully shutdown a core in terms of > kvm. This prevents, especially, kexec from rebooting the system on a boot > core in EL2. >

Re: [PATCH v2 4/8] input: goodix: reset device at init

Hi Irina, On Mon, Jun 08, 2015 at 05:37:49PM +0300, Irina Tirdea wrote: > +static int goodix_get_gpio_config(struct goodix_ts_data *ts) > +{ > + struct device *dev; > + struct gpio_desc *gpiod; > + int ret; > + > + if (!ts->client) > + return -EINVAL; > + dev = &ts-

Re: [PATCH v5 2/2] ASoC: qcom: add apq8016 sound card support

On 09/06/15 18:07, Mark Brown wrote: On Tue, Jun 09, 2015 at 01:59:36PM +0100, Srinivas Kandagatla wrote: + if (cpu_dai->id == MI2S_QUATERNARY) { + /* Configure the Quat MI2S to TLMM */ + writel(readl(pdata->mic_iomux) | + MIC_CTRL_QUA_W

[PATCH RESEND] Documentation/scsi: Documentation about scsi_cmnd lifecycle

Add documentation to describe the various scenarios that the scsi_cmnd may go through in its life time in the mid level driver - aborts, failures, retries, error handling etc. The documentation has lots of details including examples. Signed-off-by: Rajat Jain --- Hello James / linux-scsi, Resend

[PATCH v2 1/3] Input: export LEDs as class devices in sysfs

From: Samuel Thibault This change creates a new input handler called "leds" that exports LEDs on input devices as standard LED class devices in sysfs and allows controlling their ptate via sysfs or via any of the standard LED triggers. This allows to re-purpose and reassign LDEs on the keyboards

Re: [PATCH v4 2/2] staging: wilc1000: Align enum members in coreconfigurator

On Mon, Jun 08, 2015 at 11:54:29PM +0300, Stanislav Kholmanskikh wrote: > Aligned enum members to follow a common style per enum. You also reformatted defines, which you didn't mention here :( -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to ma

Re: [PATCH v4 1/2] staging: wilc1000: Cleanup to coreconfigurator

On Mon, Jun 08, 2015 at 11:54:28PM +0300, Stanislav Kholmanskikh wrote: > Fixed the following issues found with checkpatch.pl: > > * Multiple debug strings contained " \n". Changed > it to "\n". > > * Changed 'return(X)' to 'return X'. > > * Aligned TAG_PARAM_OFFSET to fit 80 columns That is

RE: [PATCH v3 02/18] NTB: Add NTB hardware abstraction layer

From: Bjorn Helgaas [mailto:bhelg...@google.com] > > It was pointed out in v1 that this one patch is over 200KB. Please > > accept my appologies for not breaking this down further. The affected > > components in this patch had interdependencies, which makes it > difficult > > to contain the chang

Re: [PATCH] ARM: Re-enable TRACE_IRQFLAGS_SUPPORT on ARMv7-M

On 09/06/15 16:01, Russell King - ARM Linux wrote: On Tue, Jun 09, 2015 at 12:41:50PM +0100, Daniel Thompson wrote: Does the following patch, which makes the arch_irqs_disabled() implementation from asm-generic available on arm, fix the build for you? Yes, this is exactly the kind of fix for t

PLEASE ANSWER

HI, I HAVE A PROJECT WE BOTH CAN BENEFIT FROM. IF INTERESTED ANSWERS THOSE QUESTIONS BELOW AND SEND THE ANSWER TO MY EMAIL ( lin.li...@aim.com ) REGARDS, LIN -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majo

[PATCH] time.c::timespec_trunc: fix nanosecond file time rounding

From: Karsten Blees Date: Tue, 9 Jun 2015 10:50:28 +0200 The rounding optimization in timespec_trunc() is based on the incorrect assumptions that current_kernel_time() is rounded to jiffies resolution, and that jiffies resolution is a multiple of all potential file time granularities. Thus, sub-

Re: [PATCH 1/3] Input: export LEDs as class devices in sysfs

On Tue, Jun 09, 2015 at 07:22:31PM +0200, Samuel Thibault wrote: > Dmitry Torokhov, le Tue 09 Jun 2015 09:49:35 -0700, a écrit : > > > > + [LED_NUML] = { "num-lock", VT_TRIGGER("kbd-numlock") }, > > > > + [LED_CAPSL] = { "caps-lock", VT_TRIGGER("kbd-capslock") }, > > > > +

[PATCH 2/4] mm: Send one IPI per CPU to TLB flush all entries after unmapping pages

An IPI is sent to flush remote TLBs when a page is unmapped that was potentially accesssed by other CPUs. There are many circumstances where this happens but the obvious one is kswapd reclaiming pages belonging to a running process as kswapd and the task are likely running on separate CPUs. On sma

[PATCH 3/4] mm: Defer flush of writable TLB entries

If a PTE is unmapped and it's dirty then it was writable recently. Due to deferred TLB flushing, it's best to assume a writable TLB cache entry exists. With that assumption, the TLB must be flushed before any IO can start or the page is freed to avoid lost writes or data corruption. This patch defe

[PATCH 4/4] mm: Send one IPI per CPU to TLB flush pages that were recently unmapped

When unmapping pages, an IPI is sent to flush all TLB entries on CPUs that potentially have a valid TLB entry. There are many circumstances where this happens but the obvious one is kswapd reclaiming pages belonging to a running process as kswapd and the task are likely running on separate CPUs. Th

[PATCH 1/4] x86, mm: Trace when an IPI is about to be sent

It is easy to trace when an IPI is received to flush a TLB but harder to detect what event sent it. This patch makes it easy to identify the source of IPIs being transmitted for TLB flushes on x86. Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel Reviewed-by: Dave Hansen --- arch/x86/mm/tlb

[PATCH 0/3] TLB flush multiple pages per IPI v6

Changelog since V5 o Split series to first do a full TLB flush and then targetting flushing Changelog since V4 o Rebase to 4.1-rc6 Changelog since V3 o Drop batching of TLB flush from migration o Redo how larger batching is managed o Batch TLB flushes when writable entries exist When unmapping p

Re: [PATCH v5 1/2] ASoC: qcom: document apq8016 sbc machine driver bindings

On 09/06/15 18:13, Mark Brown wrote: On Tue, Jun 09, 2015 at 06:08:24PM +0100, Srinivas Kandagatla wrote: +- external : flag to indicate if the I2S is connected to external codec not sure I understand why we need a boolean property indicating if an external CODEC is in use - what is th

Re: [PATCH v3 3/3] spi: atmel: add support to FIFOs

On Tue, Jun 09, 2015 at 01:53:54PM +0200, Cyrille Pitchen wrote: > To enable the FIFO feature a "atmel,fifo-size" attribute with a strictly > positive value must be added into the node of the device-tree describing > the spi controller. I'd expect the driver to use FIFOs any time they make sense,

Re: [PATCH v6] procfs: Always expose /proc//map_files/ and make it readable

On Mon, Jun 8, 2015 at 8:39 PM, Calvin Owens wrote: > Currently, /proc//map_files/ is restricted to CAP_SYS_ADMIN, and > is only exposed if CONFIG_CHECKPOINT_RESTORE is set. > > This interface very useful because it allows userspace to stat() > deleted files that are still mapped by some process,

Re: [PATCH v3 2/3] spi: atmel: update DT bindings documentation

On Tue, Jun 09, 2015 at 01:53:53PM +0200, Cyrille Pitchen wrote: > - add new property "atmel,fifo-size" Why is this a property and not something we know from the IP version? signature.asc Description: Digital signature

Re: [PATCH v3 1/3] spi: atmel: add support for the internal chip-select of the spi controller

On Tue, Jun 09, 2015 at 01:53:52PM +0200, Cyrille Pitchen wrote: > This patch relies on the CSAAT (Chip Select Active After Transfer) feature > introduced by the version 2 of the spi controller. This new mode allows to > use properly the internal chip-select output pin of the spi controller > inste

[PATCH] x86/asm/entry/32: Fix fallout from r9 trick removal in SYSCALL code

I put %ebp restoration code too late. Under strace, it is not reached and %ebp is not restored upon return to userspace. This is the fix. Run-tested. Signed-off-by: Denys Vlasenko CC: Linus Torvalds CC: Steven Rostedt CC: Ingo Molnar CC: Borislav Petkov CC: "H. Peter Anvin" CC: Andy Lutomir

Re: [RFC PATCH] usb: dwc3: ep0: Fix mem corruption on OUT transfers of more than 512 bytes

On Tue, 9 Jun 2015, Kishon Vijay Abraham I wrote: > > But with a bounce buffer that's only 512 bytes long, you can never send > > an entire packet's worth of data. If the bounce buffer is 1024 bytes > > for control endpoint, 512 bytes should be sufficient to send entire packet > right? Yes, yo

Re: [PATCH 1/3] Input: export LEDs as class devices in sysfs

Dmitry Torokhov, le Tue 09 Jun 2015 09:49:35 -0700, a écrit : > > > + [LED_NUML] = { "num-lock", VT_TRIGGER("kbd-numlock") }, > > > + [LED_CAPSL] = { "caps-lock", VT_TRIGGER("kbd-capslock") }, > > > + [LED_SCROLLL] = { "scroll-lock", VT_TRIGGER("kbd-scrollock") }, > > > > I'd tend to th

Re: [RFC PATCH] usb: dwc3: ep0: Fix mem corruption on OUT transfers of more than 512 bytes

On Tue, Jun 09, 2015 at 10:59:50AM -0400, Alan Stern wrote: > On Tue, 9 Jun 2015, Kishon Vijay Abraham I wrote: > > > Hi, > > > > On Tuesday 09 June 2015 08:09 PM, Michael Trimarchi wrote: > > > Hi > > > > > > On Jun 9, 2015 4:36 PM, "Kishon Vijay Abraham I" > > > wrote: >

Re: [PATCH 3.18 000/178] 3.18.15-review

Hi Sasha, On Mon, Jun 8, 2015 at 6:39 AM, Sasha Levin wrote: > This is the start of the stable review cycle for the 3.18.15 release. > There are 178 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. W

Re: [PATCH 1/3] Input: export LEDs as class devices in sysfs

Dmitry Torokhov, le Tue 09 Jun 2015 09:50:52 -0700, a écrit : > On Tue, Jun 09, 2015 at 03:27:34PM +0200, Samuel Thibault wrote: > > Samuel Thibault, le Tue 09 Jun 2015 15:19:55 +0200, a écrit : > > > > + [LED_NUML] = { "num-lock", VT_TRIGGER("kbd-numlock") }, > > > > + [LED_CAPSL]

Re: [PATCH 6/8] regulator: pwm-regulator: Separate voltage-table initialisation

On Fri, Jun 05, 2015 at 07:42:49PM +0100, Lee Jones wrote: > Take this out of the main .probe() routine in order to facilitate the > introduction of different ways to obtain 'duty cycle' information. This and the rest of the patches are fine but seem to depend on patch 4 - can you please rebase an

Re: [PATCH v2 3/4] x86, mwaitt: introduce mwaix delay with a configurable timer

On Tue, 2015-06-09 at 09:46 -0700, Andy Lutomirski wrote: > On Jun 9, 2015 2:30 AM, "Peter Zijlstra" wrote: > > How about you think instead and do something like: > > > > rdtsc(start); > > rdtsc_barrier(); > > Other way around. We really need a function static inline u64 > rdtsc

Re: [PATCH v5 1/2] ASoC: qcom: document apq8016 sbc machine driver bindings

On Tue, Jun 09, 2015 at 06:08:24PM +0100, Srinivas Kandagatla wrote: > >>>+- external: flag to indicate if the I2S is connected to external > >>>codec > >not sure I understand why we need a boolean property indicating if an > >external CODEC is in use - what is the consequence of setting

Re: [PATCH 1/2] regulator: max8973: configure ramp delay through callback

On Tue, Jun 09, 2015 at 07:17:52PM +0530, Laxman Dewangan wrote: > Regulator core framework support the configuration of ramp > delay reading from platform specific regulator data via the > regulator callback ops. Applied both, thanks. signature.asc Description: Digital signature

Re: [PATCH] KVM: arm/arm64: Enable the KVM-VFIO device

On 05/06/15 16:21, Eric Auger wrote: > From: Kim Phillips > > The KVM-VFIO device is used by the QEMU VFIO device. It is used to > record the list of in-use VFIO groups so that KVM can manipulate > them. > > Signed-off-by: Kim Phillips > Signed-off-by: Eric Auger > > --- > > - previously inc

Re: [PATCH v5 1/2] ASoC: qcom: document apq8016 sbc machine driver bindings

On 09/06/15 17:57, Mark Brown wrote: On Tue, Jun 09, 2015 at 01:59:29PM +0100, Srinivas Kandagatla wrote: >+Optional CPU/CODEC subnodes properties: >+- external : flag to indicate if the I2S is connected to external codec >+Example: Missing blank line between the property and the "Example:".

Re: [PATCH v5 2/2] ASoC: qcom: add apq8016 sound card support

On Tue, Jun 09, 2015 at 01:59:36PM +0100, Srinivas Kandagatla wrote: > + if (cpu_dai->id == MI2S_QUATERNARY) { > + /* Configure the Quat MI2S to TLMM */ > + writel(readl(pdata->mic_iomux) | > + MIC_CTRL_QUA_WS_SLAVE_SEL_10 | > + M

Re: [PATCH v2 1/4] x86, mwaitt: add monitorx and mwaitx instruction

On Tue, Jun 09, 2015 at 09:44:59AM -0700, Andy Lutomirski wrote: > [1] For those who weren't bitten by this repeatedly, modern Intel CPUs > (at least Sandy Bridge, anyway) will, by default, detect when all > cores are in C1 or deeper, think to themselves "wow, the OS selected > C1 -- it must want a

[RFC] panic_on_oom_timeout

Hi, during the last iteration of the timeout based oom killer discussion (http://marc.info/?l=linux-mm&m=143351457601723) I've proposed to introduce panic_on_oom_timeout as an extension to panic_on_oom rather than oom timeout which would allow OOM killer to select another oom victim and do that unt

Re: [PATCH v11 4/5] x86/earlyprintk: setup earlyprintk as early as possible

On Tue, 2015-06-09 at 17:11 +0600, Alexander Kuleshov wrote: > The early_printk function is usable only after the setup_early_printk will > be executed. We pass 'earlyprintk' through the kernel command line, so it > will be usable only after the 'parse_early_param' will be executed. This means > th

RE: [PATCH v3 09/18] NTB: Add parameters for Intel SNB B2B addresses

From: Bjorn Helgaas [mailto:bhelg...@google.com] > On Tue, Jun 09, 2015 at 05:44:36AM -0400, Allen Hubbe wrote: > > Add module parameters for the addresses to be used in b2b topology. > > What does "b2b" mean? In this case it means back-to-back, referring to the topology connecting the ntb devic

Re: [PATCH RFC v2 1/2] hwspinlock: Introduce raw capability for hwspinlocks

Two minor nits I noticed. On 6/9/2015 10:23 AM, Lina Iyer wrote: The hwspinlock framework, uses a s/w spin lock around the hw spinlock to ensure that only process acquires the lock at any time. This is the most Should this be "ensure that only one process"? Introduce hwcaps member for hwsp

Re: [Patch v5 4/6] PCI/ACPI: Consolidate common PCI host bridge code into ACPI core

On 2015/6/10 0:12, Lorenzo Pieralisi wrote: > On Mon, Jun 08, 2015 at 05:20:46PM +0100, Jiang Liu wrote: > > [...] > >> +static int acpi_pci_probe_root_resources(struct acpi_pci_root_info *info) >> +{ >> +int ret; >> +struct list_head *list = &info->resources; >> +struct acpi_device *

Re: [PATCH v5 1/2] ASoC: qcom: document apq8016 sbc machine driver bindings

On Tue, Jun 09, 2015 at 01:59:29PM +0100, Srinivas Kandagatla wrote: > +Optional CPU/CODEC subnodes properties: > +- external : flag to indicate if the I2S is connected to external codec > +Example: Missing blank line between the property and the "Example:". I'm still not sure I understand why

Re: [PATCH v2 1/2] ASoC: wm_adsp: Add code_probe and codec_remove stubs

On Tue, Jun 09, 2015 at 05:43:29PM +0100, Richard Fitzgerald wrote: > We can certainly look at factoring out that control creation once we have > a probe function in wm_adsp to put them in. Which is what this patch creates. Well, please do that then! signature.asc Description: Digital signature

[PATCH v5 2/2] gpio_wdt: Add option for early registration

In some situation, mainly when it's not possible to disable a watchdog, you may want the watchdog driver to be started as soon as possible. Adding GPIO_WATCHDOG_ARCH_INITCALL to raise initcall from module_init to arch_initcall. This patch require watchdog registration deferral mechanism Signed-o

[PATCH v5 1/2] watchdog_core: Add watchdog registration deferral mechanism

Currently, watchdog subsystem require the misc subsystem to register a watchdog. This may not be the case in case of an early registration of a watchdog, which can be required when the watchdog cannot be disabled. This patch introduces a deferral mechanism to remove this requirement. Signed-off-b

Re: [PATCH v4 5/7] Watchdog: introduce ARM SBSA watchdog driver

On 06/09/2015 11:45 AM, Guenter Roeck wrote: I tend to agree that we should just forget about pretimeout and use your original approach, where the timeout value is used to program WOR. Everything else is really just asking for trouble. The driver that I submitted is effectively the same as Fu'

Re: [PATCH v3 02/18] NTB: Add NTB hardware abstraction layer

On Tue, Jun 09, 2015 at 05:44:29AM -0400, Allen Hubbe wrote: > Abstract the ntb device behind a programming interface, so that it can > support different hardware. Change the intel hardware driver to fit the > abstraction. > > Expose the ntb hardware api to client drivers instead of tying it to >

Re: [PATCH 1/3] Input: export LEDs as class devices in sysfs

On Tue, Jun 09, 2015 at 03:19:55PM +0200, Samuel Thibault wrote: > Hello, > > Dmitry Torokhov, le Mon 08 Jun 2015 14:43:08 -0700, a écrit : > > 1. Instead of making LED class devices part of the input device they are > > implemented as an input handler (and thus are completely separate from > > in

Re: [PATCH] TESTCASE: of: OOPS when disabling node via OF_DYNAMIC

Hi Grant, On Sunday 07 June 2015 12:16:32 Grant Likely wrote: > On Wed, 22 Apr 2015 15:30:28 +0300, Pantelis Antoniou wrote: > > > On Apr 14, 2015, at 16:27 , Wolfram Sang wrote: > > > > > > Hi Pantelis, > > > > > > thanks for your prompt reply. Unfortunately, I had to wait until I could > > >

Re: [PATCH 0/3] TLB flush multiple pages per IPI v5

On 06/09/2015 08:34 AM, Dave Hansen wrote: > 2. We should measure flushing of ascending, adjacent virtual addresses >mapped with 4k pages since that is the normal case. Perhaps >vmalloc(16MB) or something. Now that I think about this a bit more, we really have two different patterns here:

Re: [PATCH 1/3] Input: export LEDs as class devices in sysfs

On Tue, Jun 09, 2015 at 03:27:34PM +0200, Samuel Thibault wrote: > Samuel Thibault, le Tue 09 Jun 2015 15:19:55 +0200, a écrit : > > > + [LED_NUML] = { "num-lock", VT_TRIGGER("kbd-numlock") }, > > > + [LED_CAPSL] = { "caps-lock", VT_TRIGGER("kbd-capslock") }, > > > + [LED_SCROLLL] = { "s

RE: [PATCH v3 01/18] NTB: Move files in preparation for NTB abstraction

From: Bjorn Helgaas [mailto:bhelg...@google.com] > On Tue, Jun 09, 2015 at 05:44:28AM -0400, Allen Hubbe wrote: > > This patch only serves the purpose to move files to their new > locations, > > s/only serves the purpose to move/moves/ > > > before applying the next patch adding the NTB Abstracti

Re: [PATCH] Documentation/scsi: Documentation about scsi_cmnd lifecycle

Hello James, On Tue, May 26, 2015 at 11:15 AM, Rajat Jain wrote: > Hello James / linux-scsi folks, > > On Wed, May 13, 2015 at 12:36 PM, Jonathan Corbet wrote: >> On Tue, 12 May 2015 14:33:46 -0700 >> Rajat Jain wrote: >> >>> Add documentation to describe the various scenarios that the scsi_cmn

Re: [PATCH 2/2 RESEND] power: reset: Add syscon poweroff device node for APM X-Gene platform

Hi Dann, On Tue, Jun 9, 2015 at 8:31 AM, Dann Frazier wrote: > On Mon, Jun 8, 2015 at 10:34 PM, Tai Tri Nguyen wrote: >> Hi Dann, >> >> On Mon, Jun 8, 2015 at 8:44 PM, Dann Frazier >> wrote: >>> On Tue, Jun 2, 2015 at 1:19 PM, Tai Nguyen wrote: This patch adds syscon poweroff device node

Re: [PATCH v2 3/4] x86, mwaitt: introduce mwaix delay with a configurable timer

On Jun 9, 2015 2:30 AM, "Peter Zijlstra" wrote: > > On Tue, Jun 09, 2015 at 11:13:40AM +0800, Huang Rui wrote: > > +static void delay_mwaitx(unsigned long __loops) > > +{ > > + u32 end, now, delay, addr; > > + > > + delay = __loops; > > + rdtsc_barrier(); > > + rdtscl(end); > > +

Re: [PATCH v3 15/18] NTB: Improve performance with write combining

On Tue, Jun 09, 2015 at 05:44:42AM -0400, Allen Hubbe wrote: > From: Dave Jiang > > Changing the memory window BAR mappings to write combining significantly > boosts the performance. We will also use memcpy that utilizies s/utilizies/uses/ > non-temporal store which showed performance improeme

[PATCH 0/2] scatterlist cleanups

Hi Jens, While working through a conversion of the scattlerlist data structure I noticed that some users were open coding scatterlist manipulations. Christoph recommended sending these for 4.1-rc inclusion. These are based on 4.1-rc7. --- Dan Williams (2): scatterlist: use sg_phys()

Re: [ANNOUNCE] 4.0.4-rt1

On 05/28/2015 06:56 PM, Fernando Lopez-Lezcano wrote: Oh well. Second time the machine hangs in two days in the same way (otherwise very stable running 3.18.x-rty) (this is a bumblebee + bbswitch graphics laptop - argh, if I had known better...) May 28 18:49:21 localhost kernel: --

Re: [PATCH v3 18/18] NTB: Increase transport MTU to 64k from 16k

On Tue, 2015-06-09 at 11:04 -0500, 'Bjorn Helgaas' via linux-ntb wrote: > On Tue, Jun 9, 2015 at 4:44 AM, Allen Hubbe > wrote: > > From: Dave Jiang > > > > Benchmarking showed significant performance increase going from MTU > > size > > of 64k from 16k. Changing the default. > > This changel

Re: [PATCH v4 5/7] Watchdog: introduce ARM SBSA watchdog driver

On 06/09/2015 09:29 AM, Timur Tabi wrote: On 06/09/2015 11:22 AM, Guenter Roeck wrote: but I see your point. Essentially, the specification is broken for all practical purposes, since, as you point out, enabling the watchdog overwrites and explicitly sets WCV. Effectively this means that just

Re: [PATCH v2 1/4] x86, mwaitt: add monitorx and mwaitx instruction

On Jun 9, 2015 3:05 AM, "Borislav Petkov" wrote: > > On Tue, Jun 09, 2015 at 05:48:56PM +0800, Huang Rui wrote: > > Any better suggestion? EBX * (TSC cycle) ? :) > > No, he means to put the description of MWAITX, what registers it > uses/takes and so on over __mwaitx() and not only in the commit m

<    1   2   3   4   5   6   7   8   9   10   >