On Tue, Sep 23, 2014 at 07:21:50PM +0400, Vladimir Davydov wrote:
> On Tue, Sep 23, 2014 at 09:28:01AM -0400, Johannes Weiner wrote:
> > On Tue, Sep 23, 2014 at 03:06:34PM +0400, Vladimir Davydov wrote:
> > > On Mon, Sep 22, 2014 at 02:57:36PM -0400, Johannes Weiner wrote:
> > > > On Mon, Sep 22,
Reduce boilerplate code by using __seq_open_private() instead of seq_open()
in xt_match_open() and xt_target_open().
Signed-off-by: Rob Jones
---
This patch uses an existing variant of seq_open() to reduce the kernel code
size.
The only significant variation from the pre-existing code is the
Thomas,
Sorry again for the mistake on my part. Let me try to address some other
concerns you have below.
On 09/22/2014 04:08 PM, Thomas Gleixner wrote:
On Sat, 20 Sep 2014, suravee.suthikulpa...@amd.com wrote:
From: Suravee Suthikulpanit
This patch implelments the ARM64 version of
On Tuesday 23 September 2014 18:40:46 Sebastian Hesselbarth wrote:
> On 09/23/2014 06:29 PM, Arnd Bergmann wrote:
> > On Tuesday 23 September 2014 17:45:52 Sebastian Hesselbarth wrote:
> >> For reference, this is what we have for MVEBU SoCs with multiple ports
> >> per controller:
> >>
> >> eth:
This patch adds an option to sample raw monotonic clock
value with any perf event, with the the aim of allowing
time correlation between data coming from perf and
additional performance-related information generated in
userspace.
In order to correlate timestamps in perf data stream
with events
Greetings,
Another week, another series. Previous versions:
- RFC: http://www.spinics.net/lists/kernel/msg1824419.html
- v1: http://thread.gmane.org/gmane.linux.kernel/1790231
The first patch adds an additional timestamp field in the perf
sample data, which can be requested for any perf event
On Tue, Sep 23, 2014 at 6:26 PM, Seth Forshee
wrote:
> On Tue, Sep 23, 2014 at 06:07:35PM +0200, Miklos Szeredi wrote:
>> On Tue, Sep 2, 2014 at 5:44 PM, Seth Forshee
>> wrote:
>> > Here's an updated set of patches for allowing fuse mounts from pid and
>> > user namespaces. I discussed some of
This patch adds a new PERF_COUNT_SW_UEVENT software event
and a related PERF_SAMPLE_UEVENT sample. User can now
write to the the perf file descriptor, injecting such
event in the perf buffer.
The UEVENT sample begins with a 32 bit unsigned integer
value describing type of the generated event. The
On Thu, 2014-09-18 at 15:34 +0100, Pawel Moll wrote:
> This patch adds a PERF_COUNT_SW_USERSPACE_EVENT type,
> which can be generated by user with PERF_EVENT_IOC_ENTRY
> ioctl command, which injects an event of said type into
> the perf buffer.
It occurred to me last night that currently perf
On 09/18/2014 04:17 PM, Nicholas A. Bellinger wrote:
I'm currently reviewing #2, #4, #5 and #7 and will consider merging
these. These cleanups account for most of the LOC reduction, and avoid
most of the larger concerns.
Also for patches like this, they really need testing on your end before
On Tue, Sep 23, 2014 at 3:01 AM, Peter Zijlstra wrote:
> On Tue, Sep 23, 2014 at 03:44:59PM +0800, Zefan Li wrote:
>> This will simplify code when we add new flags.
>>
>> v3:
>> - Kees pointed out that no_new_privs should never be cleared, so we
>> shouldn't define task_clear_no_new_privs(). we
HI,
On Tue, Sep 23, 2014 at 06:44:40PM +0200, Arnd Bergmann wrote:
> On Tuesday 23 September 2014 15:36:45 Antoine Tenart wrote:
> > On Tue, Sep 23, 2014 at 12:39:04PM +0200, Arnd Bergmann wrote:
> > > On Tuesday 23 September 2014 12:28:03 Antoine Tenart wrote:
> > > > + if (dev->of_node) {
On Wed, 24 Sep 2014, Kukjin Kim wrote:
> On 09/16/14 21:52, Krzysztof Kozlowski wrote:
> > This fixes build breakage of platsmp.c if ARMv6 was chosen for compile
> > time options (e.g. by building allmodconfig):
> >
> > $ make allmodconfig
> > $ make
> >CC arch/arm/mach-exynos/platsmp.o
On 09/22/14 23:58, Valentin Rothberg wrote:
> The "_MODULE" suffix is reserved for tristates compiled as
> loadable kernel modules (LKM). The "TEST_MODULE" feature thereby
Is that documented anywhere?
Was this causing some kind of problem or error? Please tell us what that was
if so.
>
On Sep 22, 2014, at 5:36 PM, Stephen Boyd wrote:
> The secure environment only runs in little-endian mode, so any
> buffers shared with the secure environment should have their
> contents converted to little-endian. We also mark such elements
> with __le32 to allow sparse to catch such
Hi Valentin,
On Mon, 2014-09-22 at 16:58 +0200, Valentin Rothberg wrote:
> +FEATURE = r"\w*[A-Z]{1}\w*"
> +CONFIG_DEF = r"^\s*(?:menu){,1}config\s+(" + FEATURE + r")\s*"
If I read this correctly, this misidentifies these Kconfig symbols (all
found in powerpc, by the way):
8260
8272
On Tuesday 23 September 2014 15:36:45 Antoine Tenart wrote:
> On Tue, Sep 23, 2014 at 12:39:04PM +0200, Arnd Bergmann wrote:
> > On Tuesday 23 September 2014 12:28:03 Antoine Tenart wrote:
> > > + if (dev->of_node) {
> > > + ret = ci_hdrc_usb2_dt_probe(dev, ci_pdata);
> > > +
Hi Ohad,
On 09/23/2014 09:16 AM, Ohad Ben-Cohen wrote:
> Hi Suman,
>
> On Mon, Sep 15, 2014 at 10:39 PM, Suman Anna wrote:
>> These processors need to use their internal RAM for loading, which is
>> not for generic usage by the kernel, so defining a CMA block for this
>> memory doesn't make
On Sep 22, 2014 2:07 AM, "Peter Huewe" wrote:
>
> Hi,
>
> I would like to 'invite' all interested parties in a short TPM minisummit
> where we can discuss the following hot topics of the TPM subsystem over a
> beer or two:
> - State of the TPM Subsystem
> - De-/Initialization Mess
> -
On 09/23/2014 06:29 PM, Arnd Bergmann wrote:
On Tuesday 23 September 2014 17:45:52 Sebastian Hesselbarth wrote:
For reference, this is what we have for MVEBU SoCs with multiple ports
per controller:
eth: ethernet-ctrl@72000 {
compatible = "marvell,orion-eth";
...
reg =
Building with the attached random configuration file,
drivers/built-in.o: In function `smssdio_remove':
smssdio.c:(.text+0x14751c): undefined reference to `smscore_putbuffer'
smssdio.c:(.text+0x147526): undefined reference to `smscore_unregister_device'
drivers/built-in.o: In function
On Sep 23, 2014, at 7:49 AM, Josh Triplett wrote:
> On Tue, Sep 23, 2014 at 10:01:20AM +0200, Borislav Petkov wrote:
>> ./arch/x86/include/asm/io_apic.h: In function ‘io_apic_modify’:
>> ./arch/x86/include/asm/io_apic.h:223:48: warning: declaration of ‘apic’
>> shadows a global declaration
On Tuesday 23 September 2014 16:48:44 Boris BREZILLON wrote:
> Add RTT bindings documentation.
>
> Signed-off-by: Boris BREZILLON
> Acked-by: Nicolas Ferre
> Acked-by: Johan Hovold
>
Acked-by: Arnd Bergmann
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 08/26/14 23:10, Tomasz Figa wrote:
This patch extends the firmware_ops structure with two new callbacks:
.suspend() and .resume(). The former is intended to ask the firmware to
save all its volatile state and suspend the system, without returning
back to the kernel in between. The latter is
On Mon, 22 September 2014 Linus Torvalds wrote:
> Adding proper people and mailing lists..
>
> The PCI_CLASS_DISPLAY_VGA test goes back to the very beginning by
> BenH, and I have no idea if adding PCI_CLASS_DISPLAY_3D is
> appropriate, but hopefully somebody does. The fact that it makes
>
On Tuesday 23 September 2014 17:45:52 Sebastian Hesselbarth wrote:
> For reference, this is what we have for MVEBU SoCs with multiple ports
> per controller:
>
> eth: ethernet-ctrl@72000 {
> compatible = "marvell,orion-eth";
> #address-cells = <1>;
> #size-cells = <0>;
>
On 09/16/14 00:06, Krzysztof Kozlowski wrote:
The MAX77693 is a companion power management IC for smart phones and tablets.
The MAX77693 contains input over-voltage protection (OVP),
a fully-integrated 2.5A switching charger for Lithium Ion battery with
integrated battery disconnect,
Aaro Koskinen [aaro.koski...@iki.fi] wrote:
| Hi,
|
| On Wed, Jun 25, 2014 at 08:49:03AM -0700, Sukadev Bhattiprolu wrote:
| > powerpc/perf: Adjust callchain based on DWARF debug info
| >
| > When saving the callchain on Power, the kernel conservatively saves excess
| > entries in the callchain.
On Tue, Sep 23, 2014 at 06:07:35PM +0200, Miklos Szeredi wrote:
> On Tue, Sep 2, 2014 at 5:44 PM, Seth Forshee
> wrote:
> > Here's an updated set of patches for allowing fuse mounts from pid and
> > user namespaces. I discussed some of the issues we debated with the last
> > patch set (and a few
On Tuesday 23 September 2014 18:25:01 Rafael J. Wysocki wrote:
> The problem is iteration over child nodes of a given one where there
> may not be struct device objects.
>
> For example (from patch [2/16]):
>
> +int acpi_for_each_child_node(struct acpi_device *adev,
> +
On Tue, Sep 23, 2014 at 8:00 AM, Scott Branden wrote:
> On 14-09-23 05:54 AM, Matt Porter wrote:
>>
>> On Mon, Sep 22, 2014 at 10:03:39PM -0700, Olof Johansson wrote:
>>>
>>> On Fri, Sep 19, 2014 at 11:17:11AM -0700, Florian Fainelli wrote:
Hi all,
As some of you may have seen
On Tue, 23 Sep 2014 13:28:48 +0200, Michal Hocko said:
> And there is another one hitting during randconfig. The patch makes my
> eyes bleed
Amen. But I'm not seeing a better fix either.
> #if defined(CONFIG_NUMA_BALANCING) || defined(CONFIG_COMPACTION)
> - "tlb_flush_pending
On Fri, Sep 19, 2014 at 4:22 PM, Mikhail Efremov wrote:
> On Thu, 18 Sep 2014 13:22:07 +0200 Mateusz Guzik wrote:
>> On Thu, Sep 18, 2014 at 02:55:00PM +0400, Mikhail Efremov wrote:
>> > Only exchange source and destination filenames
>> > if flags contain RENAME_EXCHANGE.
Acked-by: Miklos
On Tue, Sep 23, 2014 at 05:11:17PM +0100, Matt Fleming wrote:
> On Tue, 23 Sep, at 09:05:41AM, Linus Torvalds wrote:
> >
> > Well, it boots on my Vaio, fwiw. I'm assume that isn't all that
> > interesting, since presumably it's the macbooks that you expected to
> > still have problems.
>
> Yeah,
Hello Kukjin,
On 09/23/2014 06:00 PM, Kukjin Kim wrote:
> On 09/23/14 15:17, Kukjin Kim wrote:
>
> I've applied above and this series and please double-check the commits
> in my tree. If no problems, I will send the branch out for v3.18 soon...
>
> Thanks,
> Kukjin
>
I've looked the RTC
On Tue, Sep 23, 2014 at 06:52:02PM +0300, Mika Westerberg wrote:
> On Tue, Sep 23, 2014 at 05:45:57PM +0200, Arnd Bergmann wrote:
> > On Tuesday 23 September 2014 17:25:50 Linus Walleij wrote:
> > > On Tue, Sep 16, 2014 at 1:52 PM, Mika Westerberg
> > > wrote:
> > >
> > > > Some drivers need to
This allows to have the input devices ready in while parsing the reports
descriptor.
Signed-off-by: Benjamin Tissoires
---
drivers/hid/wacom_sys.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/hid/wacom_sys.c b/drivers/hid/wacom_sys.c
index
When we have to deal with new elements in probe, having the exit labels
named sequencially is a pain to maintain. Put a meaningful name instead
so that we do not have to renumber them on inserts.
Signed-off-by: Benjamin Tissoires
---
drivers/hid/wacom_sys.c | 49
On Tue, Sep 23, 2014 at 12:44:47PM +0200, Rostislav Lisovy wrote:
> On Čt, 2014-09-18 at 21:12 -0700, Guenter Roeck wrote:
> > How about reading the OMAP_WATCHDOG_SPR register ?
>
> Unfortunately this would be not only extremely fragile (someone writes
> correct start sequence followed by some
Hi guys,
So, this patch series aims at supporting natively any future HID compliant wacom
tablet. Those found on the various laptops (ISDv4/5) already are HID compliant
and they should work in the future without any modification of the kernel.
Few things to note here:
- I used the PID 0x00E6
On Tue, Sep 23, 2014 at 06:20:46PM +0530, Kiran Padwal wrote:
> This change uses managed resource APIs to allocate resources such as,
> mem, irq in order to simplify the driver unload or failure cases.
>
> Signed-off-by: Kiran Padwal
> ---
> drivers/dma/cppi41.c | 15 ---
> 1 file
Ping? I haven't heard anything on this.
Thanks,
-corey
On 09/18/2014 07:58 AM, Corey Minyard wrote:
> On 09/18/2014 04:58 AM, Ralf Baechle wrote:
>> On Tue, Sep 16, 2014 at 04:45:25PM -0500, miny...@acm.org wrote:
>>
>>> From: Corey Minyard
>>>
>>> The MIPS frame save code was just saving a
Hi Guennadi,
On Tue, 23 Sep 2014 14:33:20 +0200 (CEST)
Guennadi Liakhovetski wrote:
> Hi Boris,
>
> On Tue, 22 Jul 2014, Boris BREZILLON wrote:
>
> > Rename mediabus formats and move the enum into a separate header file so
> > that it can be used by DRM/KMS subsystem without any reference to
Signed-off-by: Benjamin Tissoires
---
drivers/hid/wacom_sys.c | 39 ++--
drivers/hid/wacom_wac.c | 120
drivers/hid/wacom_wac.h | 8
3 files changed, 164 insertions(+), 3 deletions(-)
diff --git a/drivers/hid/wacom_sys.c
This new field cpu_capacity_orig reflects the original capacity of a CPU
before being altered by frequency scaling, rt tasks and/or IRQ
The cpu_capacity_orig will be used in several places to detect when the
capapcity of a CPU has been noticeably reduced so we can trig load balance
to look for a
Monitor the usage level of each group of each sched_domain level. The usage is
the amount of cpu_capacity that is currently used on a CPU or group of CPUs.
We use the utilization_load_avg to evaluate the usage level of each group.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 13
On Tue, 23 Sep, at 09:05:41AM, Linus Torvalds wrote:
>
> Well, it boots on my Vaio, fwiw. I'm assume that isn't all that
> interesting, since presumably it's the macbooks that you expected to
> still have problems.
Yeah, though I'm still interested in hearing success stories since it
indicates I
If the CPU is used for handling lot of IRQs, trig a load balance to check if
it's worth moving its tasks on another CPU that has more capacity.
As a sidenote, this will note generate more spurious ilb because we already
trig an ilb if there is more than 1 busy cpu. If this cpu is the only one
On Tue, Sep 23, 2014 at 04:07:35PM +0200, Boris BREZILLON wrote:
> Several MTD users (either in user or kernel space) expect a valid raw
> access support to NAND chip devices.
> This is particularly true for testing tools which are often touching the
> data stored in a NAND chip in raw mode to
add the SD_PREFER_SIBLING flag for SMT level in order to ensure that
the scheduler will put at least 1 task per core.
Signed-off-by: Vincent Guittot
---
kernel/sched/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index c7c8ac4..f72663e
On 09/16/14 21:52, Krzysztof Kozlowski wrote:
This fixes build breakage of platsmp.c if ARMv6 was chosen for compile
time options (e.g. by building allmodconfig):
$ make allmodconfig
$ make
CC arch/arm/mach-exynos/platsmp.o
/tmp/ccdQM0Eg.s: Assembler messages:
/tmp/ccdQM0Eg.s:432:
On Tue, Sep 23, 2014 at 07:49:36AM -0700, Josh Triplett wrote:
> Here, I think the right fix involves picking a more descriptive name
> than "apic" for the global varible.
Sure, this one is simple enough and could be fixed. Something for a
newbie to tackle I'd say.
--
Regards/Gruss,
Boris.
On Tue, Sep 23, 2014 at 08:31:53PM +0800, Xiubo Li wrote:
> Add power management operations(suspend and resume) as part of
> dev_pm_ops for IMX2 watchdog driver.
>
> If PM will be supported, please make sure that the wdev->clk
> could disable the watchdog's counter input clock source or can
>
Heiko,
On Tue, Sep 23, 2014 at 4:59 AM, Heiko Stuebner wrote:
> From: Heiko Stuebner
>
> Add the ability to parse gpio-charger data from a devicetree node.
>
> Signed-off-by: Heiko Stuebner
> ---
> drivers/power/gpio-charger.c | 72
> ++--
> 1 file
The scheduler tries to compute how many tasks a group of CPUs can handle by
assuming that a task's load is SCHED_LOAD_SCALE and a CPU capacity is
SCHED_CAPACITY_SCALE but the capacity_factor is hardly working for SMT system,
it sometimes works for big cores but fails to do the right thing for
Add new statistics which reflect the average time a task is running on the CPU
and the sum of these running time of the tasks on a runqueue. The latter is
named utilization_avg_contrib.
This patch is based on the usage metric that was proposed in the 1st
versions of the per-entity load tracking
During load balance, the scheduler evaluates the number of tasks that a group
of CPUs can handle. The current method assumes that tasks have a fix load of
SCHED_LOAD_SCALE and CPUs have a default capacity of SCHED_CAPACITY_SCALE.
This assumption generates wrong decision by creating ghost cores or
ISDv4 and v5 are plain HID devices. We can directly implement a generic
HID parsing/handling and remove the need to manually add those PID in
the list of supported devices.
This patch implements the pen support only. The finger part will come in
a later patch.
To be properly notified of an
If the input can be created earlier during probe, we can already populate
them while reading the report descriptor. This way, we can rely on the
hid subsystem directly for tablets which already provide a meaningful
report descriptor (like ISDv4-5).
This patch only splits the allocation and
On Tue, Sep 2, 2014 at 5:44 PM, Seth Forshee wrote:
> Here's an updated set of patches for allowing fuse mounts from pid and
> user namespaces. I discussed some of the issues we debated with the last
> patch set (and a few others) with Eric at LinuxCon, and the updates here
> mainly reflect the
Heiko,
On Tue, Sep 23, 2014 at 4:59 AM, Heiko Stuebner wrote:
> From: Heiko Stuebner
>
> Some gpio implementations return interesting values for gpio_get_value when
> the value is not 0 - as seen on a imx6sl board. Therefore do not use the
> value returned from gpio_get_value directly but
On 2014-09-23 18:02, David Miller wrote:
> From: Michal Marek
> Date: Tue, 23 Sep 2014 17:44:00 +0200
>
>> Commit 5d6be6a5 ("scsi_netlink : Make SCSI_NETLINK dependent on NET
>> instead of selecting NET") removed what happened to be the only instance
>> of 'select NET'. Defconfigs that were
On Tue, Sep 23, 2014 at 6:18 AM, Matt Fleming wrote:
>
> OK, below is what I've got on top of commit f3670394c29f in Linus' tree.
> Please don't anyone pick this up yet, I'm still testing it on my
> machines and it desperately needs some Tested-by tags.
Well, it boots on my Vaio, fwiw. I'm
On Tue, Sep 23, 2014 at 3:32 AM, Michael S. Tsirkin wrote:
> On restore, virtio pci does the following:
> + set features
> + init vqs etc - device can be used at this point!
> + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits
>
> This is in violation of the virtio spec, which
> requires the
On Tuesday, September 23, 2014 05:45:57 PM Arnd Bergmann wrote:
> On Tuesday 23 September 2014 17:25:50 Linus Walleij wrote:
> > On Tue, Sep 16, 2014 at 1:52 PM, Mika Westerberg
> > wrote:
> >
> > > Some drivers need to deal with only firmware representation of its
> > > GPIOs. An example would
From: Michal Marek
Date: Tue, 23 Sep 2014 17:44:00 +0200
> Commit 5d6be6a5 ("scsi_netlink : Make SCSI_NETLINK dependent on NET
> instead of selecting NET") removed what happened to be the only instance
> of 'select NET'. Defconfigs that were relying on the select now lack
> networking support.
>
On Tue, Sep 23, 2014 at 7:37 AM, Matt Fleming wrote:
>
> I know Josh was in favour of getting this message dropped and treating
> this as a regression fix, but I was erring on the side of caution
> because it's not critical.
I'd certainly prefer this too, because UI also see the annoying
On 09/23/14 15:17, Kukjin Kim wrote:
Kukjin Kim wrote:
Andreas Färber wrote:
[...]
Kukjin: Andreas's patch series was Reviewed long ago I think and by
now I'd imagine it's got some conflicts due to it not having been
applied in a timely fashion. Perhaps you could fix it up for Andreas
Heiko,
On Tue, Sep 23, 2014 at 5:03 AM, Heiko Stübner wrote:
> Am Montag, 22. September 2014, 09:48:33 schrieb Doug Anderson:
>> > @@ -196,6 +255,7 @@ static struct platform_driver gpio_charger_driver = {
>> >
>> > .name = "gpio-charger",
>> > .owner =
On Tue, Sep 23, 2014 at 9:04 AM, Thierry Reding
wrote:
> On Tue, Sep 23, 2014 at 03:06:35PM +0100, Russell King - ARM Linux wrote:
>> On Tue, Sep 23, 2014 at 07:56:01AM -0600, Bjorn Helgaas wrote:
>> > This doesn't require any coordination with the PCI core, so I was just
>> > leaving this up to
On Mon, Sep 22, 2014 at 06:44:37PM +0200, Oleg Nesterov wrote:
> __lock_task_sighand() does local_irq_save() to prevent the potential
> deadlock, we can use preempt_disable() with the same effect. And in
> this case we can do preempt_disable/enable + rcu_read_lock/unlock only
> once outside of the
get voltage & duty table from device tree might be better, other platforms can
also use this
driver without any modify.
Tested on a rk3288 sdk board as logic voltage regulator.
Changes in v6:
Adviced by Mark Rutland
- fix a spelling error
Changes in v4:
Adviced by Doug Anderson
- improve
Document the st-pwm regulator
Signed-off-by: Chris Zhong
Reviewed-by: Doug Anderson
---
Changes in v6:
Adviced by Mark Rutland
- fix a spelling error
Changes in v4:
Adviced by Doug Anderson
- remove regulator-always-on and regulator-boot-on from the Example
Changes in v3:
Adviced by Doug
Get voltage & duty table from device tree might be better, other platforms can
also use this
driver without any modify.
Signed-off-by: Chris Zhong
Reviewed-by: Doug Anderson
---
Changes in v6: None
Changes in v4:
Adviced by Doug Anderson
- improve kconfig
- add const for desc structure
On Tue, Sep 23, 2014 at 05:45:57PM +0200, Arnd Bergmann wrote:
> On Tuesday 23 September 2014 17:25:50 Linus Walleij wrote:
> > On Tue, Sep 16, 2014 at 1:52 PM, Mika Westerberg
> > wrote:
> >
> > > Some drivers need to deal with only firmware representation of its
> > > GPIOs. An example would
On 09/23/2014 12:11 AM, Tejun Heo wrote:
> On Tue, Sep 23, 2014 at 08:09:06AM +0200, Christoph Hellwig wrote:
>> On Tue, Sep 23, 2014 at 02:01:41AM -0400, Tejun Heo wrote:
>>> On Tue, Sep 23, 2014 at 07:59:24AM +0200, Christoph Hellwig wrote:
"[PATCHSET percpu/for-3.18] percpu_ref: implement
On Fri, Sep 5, 2014 at 9:52 PM, Nishanth Menon wrote:
> When viewing the /proc/interrupts, there is no information about which
> GPIO bank a specific gpio interrupt is hooked on to. This is more than a
> bit irritating as such information can esily be provided back to the
> user and at times,
On Tuesday, September 23, 2014 10:29:45 AM Felipe Balbi wrote:
> On Tue, Sep 23, 2014 at 05:17:03PM +0200, Rafael J. Wysocki wrote:
> > On Tuesday, September 23, 2014 09:52:21 AM Felipe Balbi wrote:
> > > On Tue, Sep 23, 2014 at 04:52:01PM +0200, Rafael J. Wysocki wrote:
> > > > On Tuesday,
On Tuesday 23 September 2014 17:25:50 Linus Walleij wrote:
> On Tue, Sep 16, 2014 at 1:52 PM, Mika Westerberg
> wrote:
>
> > Some drivers need to deal with only firmware representation of its
> > GPIOs. An example would be a GPIO button array driver where each button
> > is described as a
Commit 5d6be6a5 ("scsi_netlink : Make SCSI_NETLINK dependent on NET
instead of selecting NET") removed what happened to be the only instance
of 'select NET'. Defconfigs that were relying on the select now lack
networking support.
Reported-by: Stephen Rothwell
Cc: sparcli...@vger.kernel.org
On Wed, Sep 17, 2014 at 3:47 PM, Loic Poulain wrote:
> Direct Irq En bit can be initialized to a bad value.
> This bit has to be cleared for io access mode.
>
> Signed-off-by: Loic Poulain
> ---
> v2: Apply over ff998356b644ebe723127bd9eec6040b59a4a4f6 + add Warning
I can't figure out if the
Commit 5d6be6a5 ("scsi_netlink : Make SCSI_NETLINK dependent on NET
instead of selecting NET") removed what happened to be the only instance
of 'select NET'. Defconfigs that were relying on the select now lack
networking support.
Reported-by: Stephen Rothwell
Cc: linuxppc-...@lists.ozlabs.org
On 09/23/2014 04:37 PM, Arnd Bergmann wrote:
On Tuesday 23 September 2014 16:29:22 Antoine Tenart wrote:
So I had a look on other Ethernet bindings. Would you agree with
something like the following?
eth0: ethernet@f7b9 {
...
#address-cells =
Commit 5d6be6a5 ("scsi_netlink : Make SCSI_NETLINK dependent on NET
instead of selecting NET") removed what happened to be the only instance
of 'select NET'. Defconfigs that were relying on the select now lack
networking support.
Reported-by: Stephen Rothwell
Cc: linux...@vger.kernel.org
Commit 5d6be6a5 ("scsi_netlink : Make SCSI_NETLINK dependent on NET
instead of selecting NET") removed what happened to be the only instance
of 'select NET'. Defconfigs that were relying on the select now lack
networking support.
Reported-by: Stephen Rothwell
Cc: linux-m...@linux-mips.org
Commit 5d6be6a5 ("scsi_netlink : Make SCSI_NETLINK dependent on NET
instead of selecting NET") removed what happened to be the only instance
of 'select NET'. Defconfigs that were relying on the select now lack
networking support.
Reported-by: Stephen Rothwell
Cc: linux-par...@vger.kernel.org
On 22 September 2014 22:34, Bjorn Helgaas wrote:
> [+cc x86 folks]
>
> On Mon, Sep 22, 2014 at 02:27:48PM -0600, Bjorn Helgaas wrote:
>> On Mon, Aug 25, 2014 at 11:26:34PM +0200, Mathias Krause wrote:
>> > Hi Bjorn,
>> >
>> > [...]
>> >
>> > Mathias Krause (5):
>> > x86/PCI: Mark DMI tables as
On Thu, Sep 18, 2014 at 10:57 AM, Paul Bolle wrote:
> From: Paul Bolle
>
> Commit d78c16ccde96 ("ARM: SAMSUNG: Remove remaining legacy code")
> removed the Kconfig symbol S5P_GPIO_DRVSTR. It didn't remove one check
> for the related macro. Remove that check and the dead code it hides.
>
>
On 18 September 2014 12:09, Krzysztof Kozlowski wrote:
> On śro, 2014-09-17 at 20:42 +0200, Ulf Hansson wrote:
>> On 16 September 2014 10:51, Krzysztof Kozlowski
>> wrote:
>
> [...]
>
>> >
>> > @@ -2585,6 +2620,34 @@ static int pl330_dma_device_slave_caps(struct
>> > dma_chan *dchan,
>> >
On Thu, Sep 18, 2014 at 11:03 AM, Gernot Vormayr wrote:
> If one adds 'gpio-controller;' to the chip in the devicetree, then
> initialization fails with 'gpiochip_find_base: cannot find free range',
> because ngpio is 0. This patch fixes the bug.
>
> Tested on ml507 board.
>
> Signed-off-by:
On Wed, Sep 10, 2014 at 03:06:27PM -0400, Peter Hurley wrote:
> The tty core does not test tty->hw_stopped; remove from drivers
> which don't test it themselves.
>
> cc: Johan Hovold
> Signed-off-by: Peter Hurley
Acked-by: Johan Hovold
--
To unsubscribe from this list: send the line
On Tue, 23 Sep 2014 23:17:41 +0800
Huang Shijie wrote:
> On Tue, Sep 23, 2014 at 04:07:35PM +0200, Boris BREZILLON wrote:
> > Several MTD users (either in user or kernel space) expect a valid raw
> > access support to NAND chip devices.
> > This is particularly true for testing tools which are
On Wed, Sep 17, 2014 at 10:49 AM, Chang Rebecca Swee Fun
wrote:
> This patch series is about enabling legacy GPIO support for Quark X1000.
> The patches were developed on top of Mika Westerberg's commit on
> consolidating core and resume banks. Please refer to the link below for
> more
On Tue, Sep 23, 2014 at 05:17:03PM +0200, Rafael J. Wysocki wrote:
> On Tuesday, September 23, 2014 09:52:21 AM Felipe Balbi wrote:
> > On Tue, Sep 23, 2014 at 04:52:01PM +0200, Rafael J. Wysocki wrote:
> > > On Tuesday, September 23, 2014 03:17:12 PM Heikki Krogerus wrote:
> > > > On Wed, Aug 20,
On Wed, Sep 17, 2014 at 8:46 AM, Anders Berg wrote:
> Add support for a extended PL022 which has an extra register for controlling
> up
> to five chip select signals. This controller is found on the AXM5516 SoC.
> Unfortunately the PrimeCell identification registers are identical to a
>
I don't have any hardware to test this over, however I can emulate a
arm system over qemu if needed.
I was just trying to help out if we need hardware I can't test and
again I am sorry for the terrible patches.
It was never my goal to be a nuisance.
Nick
On Tue, Sep 23, 2014 at 9:46 AM, Krzysztof
On 09/23/2014 09:22 AM, Chris J Arges wrote:
> When using a virtual SCSI disk in a VMWare VM if blkdev_issue_zeroout is used
> data can be improperly zeroed out using the mptfusion driver. This patch
> disables write_same for this driver and the vmware subsystem_vendor which
> ensures that manual
On Tue, Sep 16, 2014 at 1:52 PM, Mika Westerberg
wrote:
> With release of ACPI 5.1 and _DSD method we can finally name GPIOs (and
> other things as well) returned by _CRS. Previously we were only able to
> use integer index to find the corresponding GPIO, which is pretty error
> prone if the
On Tue, Sep 23, 2014 at 08:00:41AM -0700, Scott Branden wrote:
> On 14-09-23 05:54 AM, Matt Porter wrote:
> >On Mon, Sep 22, 2014 at 10:03:39PM -0700, Olof Johansson wrote:
> >>On Fri, Sep 19, 2014 at 11:17:11AM -0700, Florian Fainelli wrote:
> >>>Hi all,
> >>>
> >>>As some of you may have seen in
On Tue, Sep 16, 2014 at 1:52 PM, Mika Westerberg
wrote:
> Some drivers need to deal with only firmware representation of its
> GPIOs. An example would be a GPIO button array driver where each button
> is described as a separate firmware node in device tree. Typically these
> child nodes do not
401 - 500 of 2070 matches
Mail list logo
