The switch is typically used in conjunction with the MICDET clamp in
order to suppress pops and clicks associated with jack insertion.
Signed-off-by: Charles Keepax
Acked-by: Lee Jones
---
drivers/mfd/wm5110-tables.c |2
On 09/09/15 09:20, Li Jun wrote:
> On Mon, Sep 07, 2015 at 01:53:19PM +0300, Roger Quadros wrote:
>> On 07/09/15 10:40, Li Jun wrote:
>>> On Mon, Aug 24, 2015 at 04:21:18PM +0300, Roger Quadros wrote:
The OTG core instantiates the OTG Finite State Machine
per OTG controller and manages
On 09/09/2015 06:59 AM, Wang Long wrote:
> This patch add some out of bounds testcases to test_kasan
> module.
>
> Signed-off-by: Wang Long
Acked-by: Andrey Ryabinin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Tue, Sep 8, 2015 at 8:19 PM, Olliver Schinagl
wrote:
> The ssd1307fb driver supports a lot of chips from the ssd130xfb series.
> This patch adds the ssd1309 chip, a 128x64 OLED driver chip. It is very
> similar to the other chips and only has some definitions added to
Hi Lucasz,
Nit: Please add a version number to the patches you send - this is at
least the 4th revision of this series, and it is harder to keep track of
what I'm reviewing. git send-email --subject-prefix "PATCH v4" is your
friend.
On 09/09/15 10:30, Lukasz Anaczkowski wrote:
> ACPI subtable
Hi, Yu
On 2015-09-09 19:27, Chen Yu wrote:
> In current code, max_perf_pct might be smaller than min_perf_pct
> by improper user input:
>
> $ grep . /sys/devices/system/cpu/intel_pstate/m*_perf_pct
> /sys/devices/system/cpu/intel_pstate/max_perf_pct:100
>
Add virtio_gpu_queue_ctrl_buffer_nolock function, which does the same as
virtio_gpu_queue_ctrl_buffer but does not take the virtqueue lock. The
caller must hold the lock instead.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_vq.c | 17 +
1
From: Olliver Schinagl
The Olimex A20 OLinuXino Micro features an eeprom that is always on the
board. This patch adds it to the dts.
--Signed-off-by: Olliver Schinagl
---
arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts | 6 ++
1 file changed, 6
On 9 September 2015 at 11:58, Matt Fleming wrote:
> On Wed, 09 Sep, at 09:37:21AM, Ard Biesheuvel wrote:
>> On 8 September 2015 at 22:37, Matt Fleming wrote:
>> >
>> > diff --git a/arch/x86/platform/efi/efi.c b/arch/x86/platform/efi/efi.c
>> >
IEEE 1722 describes AVB (later renamed to TSN - Time Sensitive
Networking), a protocol, encapsualtion and synchronization to utilize
standard networks for audio/video (and later other time-sensitive)
streams.
This standard uses ethertype 0x22F0.
llist_del_first reads entry->next, but it did not acquire
visibility over the entry node. As the result it can get
a stale value of entry->next (e.g. NULL or whatever garbage
was there before the appending thread wrote correct value).
And then commit that value as llist head with cmpxchg.
That
On 9 September 2015 at 03:33, Rob Herring wrote:
> On 09/08/2015 02:30 AM, Tomeu Vizoso wrote:
>> On 7 September 2015 at 22:50, Rob Herring wrote:
>>> On Mon, Sep 7, 2015 at 7:23 AM, Tomeu Vizoso
>>> wrote:
Hello,
2015-09-09 6:59 GMT+03:00 Wang Long :
> The current KASAN code can find the following out-of-bounds
> bugs:
> char *ptr;
> ptr = kmalloc(8, GFP_KERNEL);
> memset(ptr+7, 0, 2);
>
> the cause of the problem is the type conversion error in
>
On Wed, 09 Sep, at 09:37:21AM, Ard Biesheuvel wrote:
> On 8 September 2015 at 22:37, Matt Fleming wrote:
> >
> > diff --git a/arch/x86/platform/efi/efi.c b/arch/x86/platform/efi/efi.c
> > index 691b333e0038..a2af35f6093a 100644
> > --- a/arch/x86/platform/efi/efi.c
> >
On 09/09/15 11:45, Peter Chen wrote:
> On Wed, Sep 09, 2015 at 12:33:20PM +0300, Roger Quadros wrote:
>> On 09/09/15 11:13, Peter Chen wrote:
>>> On Wed, Sep 09, 2015 at 12:08:10PM +0300, Roger Quadros wrote:
On 09/09/15 05:21, Peter Chen wrote:
> On Tue, Sep 08, 2015 at 03:25:25PM +0300,
On 2015/9/9 17:40, Andrey Ryabinin wrote:
> 2015-09-09 6:59 GMT+03:00 Wang Long :
>> The current KASAN code can find the following out-of-bounds
>> bugs:
>> char *ptr;
>> ptr = kmalloc(8, GFP_KERNEL);
>> memset(ptr+7, 0, 2);
>>
>> the cause of the
Hi,
On 09-09-15 11:16, yuantian.t...@freescale.com wrote:
From: Tang Yuantian
kbuild test robot reports the warnings:
drivers/ata/ahci_qoriq.c: In function 'ahci_qoriq_hardreset':
include/asm-generic/io.h:163:2: warning: 'px_is' may be used
uninitialized in this
(adding back folks in cc)
On 08/09/15 20:35, Alan Stern wrote:
> On Tue, 8 Sep 2015, Roger Quadros wrote:
>
What if there is another architecture like so?
C:
[Parent]
|
|
Greg,
any thoughts about the patch?
Regards,
Jan
- Original Message -
> From: "Dave Young"
> To: "Jan Stancek"
> Cc: gre...@linuxfoundation.org, linux-kernel@vger.kernel.org,
> linux...@kvack.org
> Sent: Tuesday, 1 September, 2015 9:15:53 AM
>
From: Paul Gortmaker
As of commit dae6e64d2bcfd4b06304ab864c7e3a4f6b5fedf4 ("rcu: Introduce
proper blocking to no-CBs kthreads GP waits") the RCU subsystem started
making use of wait queues.
Here we convert all additions of RCU wait queues to use simple wait
From: "Peter Zijlstra (Intel)"
The existing wait queue support has support for custom wake up call
backs, wake flags, wake key (passed to call back) and exclusive
flags that allow wakers to be tagged as exclusive, for limiting
the number of wakers.
In a lot of cases, none
Hi,
I post these patches without CC anyone. I will be on vacation soonish
and wont have time till LinuxCon EU. So this is basically the current
work and maybe someone is interested to look at them or do something
with them. In other words I archive the current series :)
These patches are against
> > > +#ifdef CONFIG_SERIAL_EARLYCON
> > > +static int use_earlycon __initdata;
> > > +static int __init setup_acpi_earlycon(char *buf)
> > > +{
> > > + if (!buf)
> > > + use_earlycon = 1;
> > > +
> > > + return 0;
> > > +}
> > > +early_param("earlycon", setup_acpi_earlycon);
> >
> > It
On Wed, Sep 09, 2015 at 11:43:05AM +0200, Peter Zijlstra wrote:
> Sadly that makes the code worse; I get 14 mul instructions where
> previously I had 11.
FWIW I count like:
objdump -d defconfig-build/kernel/sched/fair.o |
awk '/<[^>]*>:/ { p=0 }
/:/ { p=1 }
{ if (p) print $0 }' |
On Wed, Sep 09, 2015 at 12:33:20PM +0300, Roger Quadros wrote:
> On 09/09/15 11:13, Peter Chen wrote:
> > On Wed, Sep 09, 2015 at 12:08:10PM +0300, Roger Quadros wrote:
> >> On 09/09/15 05:21, Peter Chen wrote:
> >>> On Tue, Sep 08, 2015 at 03:25:25PM +0300, Roger Quadros wrote:
>
>
>
On Wed, Sep 09, 2015 at 11:43:05AM +0200, Peter Zijlstra wrote:
> On Tue, Sep 08, 2015 at 05:53:31PM +0100, Morten Rasmussen wrote:
> > On Tue, Sep 08, 2015 at 03:31:58PM +0100, Morten Rasmussen wrote:
>
> > > On Tue, Sep 08, 2015 at 02:52:05PM +0200, Peter Zijlstra wrote:
> > > But if we apply
On Wed, 09 Sep, at 08:33:07AM, joeyli wrote:
>
> Yes, the machine on my hand has EFI_PROPERTIES_TABLE enabled, and it doesn't
> boot without your patch.
Awesome. Could you test the following patch instead?
---
>From 24d324b781a3b688dcc265995949a9cf4e8af687 Mon Sep 17 00:00:00 2001
From: Matt
On 09/08/2015 06:15 PM, Christoph Lameter wrote:
> On Tue, 8 Sep 2015, Nikolay Borisov wrote:
>
>>> You have read https://www.kernel.org/doc/Documentation/vm/slub.txt?
>>
>> I've read that I'm also following the merge/nomerge thread on the DM
>> mailing list. I guess my understanding is wrong
Add the bits needed for opengl rendering support: query
capabilities, new virtio commands, drm ioctls.
Signed-off-by: Dave Airlie
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/Makefile| 3 +-
drivers/gpu/drm/virtio/virtgpu_drv.c |
On Tue, Sep 08, 2015 at 05:01:06PM +0900, Joonsoo Kim wrote:
> 2015-08-24 21:29 GMT+09:00 Mel Gorman :
> >
> >
> > +/*
> > + * Reserve a pageblock for exclusive use of high-order atomic allocations
> > if
> > + * there are no empty page blocks that contain a page
Some of the olimex series of boards feature a permanently connected eeprom on
i2c-1. This patch series adds them on all the boards that have them according
to the spec-sheets.
I explicitly added my personal --Tested-by to boards I actually tested. There
are two boards, that according to the
From: Olliver Schinagl
The OLinuXino A10S micro features an eeprom. According to the eeprom.txt
binding document, we should use the manufacturer and 'at' is not the
proper manufacturer id according to the vendor-prefixes.
This patch takes the proper vendor-prefix and uses it
On Wed, Sep 09, 2015 at 12:08:10PM +0300, Roger Quadros wrote:
> On 09/09/15 05:21, Peter Chen wrote:
> > On Tue, Sep 08, 2015 at 03:25:25PM +0300, Roger Quadros wrote:
> >>
> >>
> >> On 08/09/15 11:31, Peter Chen wrote:
> >>> On Mon, Sep 07, 2015 at 01:23:01PM +0300, Roger Quadros wrote:
>
From: Tang Yuantian
kbuild test robot reports the warnings:
drivers/ata/ahci_qoriq.c: In function 'ahci_qoriq_hardreset':
>> include/asm-generic/io.h:163:2: warning: 'px_is' may be used
>> uninitialized in this function [-Wuninitialized]
From: Dave Airlie
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.c
b/drivers/gpu/drm/virtio/virtgpu_drv.c
index 1245d09..e00298e
The renesas-intc-irqpin interrupt controller is cascaded to the GIC.
Hence when propagating wake-up settings to its parent interrupt
controller, the following lockdep warning is printed:
=
[ INFO: possible recursive locking detected ]
The renesas-irqc interrupt controller is cascaded to the GIC. Hence when
propagating wake-up settings to its parent interrupt controller, the
following lockdep warning is printed:
=
[ INFO: possible recursive locking detected ]
From: Dave Airlie
This is enough to enable DRI3.
Signed-off-by: Dave Airlie
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/Makefile| 2 +-
drivers/gpu/drm/virtio/virtgpu_drv.c | 13 +-
Hi Thomas, Jason,
The renesas-intc-irqpin and renesas-irqc interrupt controllers are
cascaded to GICs. Hence when propagating wake-up settings to their parent
interrupt controllers, a lockdep warning is printed.
Avoid these false positive by using separate lockdep classes for IRQC
and
Add helper function to handle the submission of fenced control requests.
Make sure we initialize the fence while holding the virtqueue lock, so
requests can't be reordered.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_fence.c | 2 +-
The completion code has been changed using swait (simple wait) instead
of the more complex wait implementation. ep_io() is using not using
the wait_for_completation_*() helper function we need to update this
function accordingly.
Signed-off-by: Daniel Wagner
Cc:
The completion code has been changed using swait (simple wait) instead
of the more complex wait implementation. ezusb_req_ctx_wait() is using
not using the wait_for_completation_*() helper function we need to
update this function accordingly.
Signed-off-by: Daniel Wagner
From: Marcelo Tosatti
The problem:
On -rt, an emulated LAPIC timer instances has the following path:
1) hard interrupt
2) ksoftirqd is scheduled
3) ksoftirqd wakes up vcpu thread
4) vcpu thread is scheduled
This extra context switch introduces unnecessary latency in the
The completion code has been changed using swait (simple wait) instead
of the more complex wait implementation. ffs_data_put() is checking
the internal state of the completion code. That is why the transition
from wait to swait is not completely transparent for this function and
we need to update
From: Paul Gortmaker
Completions have no long lasting callbacks and therefore do not need
the complex waitqueue variant. Use simple waitqueues which reduces
the contention on the waitqueue lock.
This was a carry forward from v3.10-rt, with some RT specific chunks,
By moving the rcu_nocb_gp_cleanup() call out of the rnp->lock
protected region we avoid a deadlock as lockdep reported.
swake_up_all() is toggling IRQ enable/disable. That means we might
start processing soft IRQs. __do_softirq() calls
rcu_process_callbacks() which wants to grab nrp->lock.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=104031
Fixes: 6e85d5ad36a26debc23a9a865c029cbe242b2dc8
Based on the discussion starting at
http://www.spinics.net/lists/netdev/msg342193.html
Tested locally on RTL8168evl/8111evl with various concurrent processes
accessing /proc/net/dev while
The sun4i_ss_opti_poll function cipher data until the output miter have
a length of 0.
If the crypto API client, give more SGs than necessary this could result
in an infinite loop.
Fix it by checking for remaining bytes, just like sun4i_ss_cipher_poll().
Signed-off-by: LABBE Corentin
On Wed, 9 Aug 2015 15:10:00 +0400
Ivan Mikhaylov wrote:
>On Wed, 2015-08-05 at 15:01 +0400, Ivan Mikhaylov wrote:
>> * do the redefinition of emac_regs struct from driver structure
>> perspective and passing size from actual struct size, not from memory
>> area variable which
On 09/09/15 11:13, Peter Chen wrote:
> On Wed, Sep 09, 2015 at 12:08:10PM +0300, Roger Quadros wrote:
>> On 09/09/15 05:21, Peter Chen wrote:
>>> On Tue, Sep 08, 2015 at 03:25:25PM +0300, Roger Quadros wrote:
On 08/09/15 11:31, Peter Chen wrote:
> On Mon, Sep 07, 2015 at
As per-irc request
*prod*
thanks!
-Henrik
On Thu, Aug 20, 2015 at 03:54:02PM +0200, Henrik Austad wrote:
> Most of the policy-tests are done via the _policy() helpers with
> the notable exception of idle. A new wrapper for valid_policy() has also
> been added to improve readability in
On Tue, Sep 08, 2015 at 05:53:31PM +0100, Morten Rasmussen wrote:
> On Tue, Sep 08, 2015 at 03:31:58PM +0100, Morten Rasmussen wrote:
> > On Tue, Sep 08, 2015 at 02:52:05PM +0200, Peter Zijlstra wrote:
> > But if we apply the scaling to the weight instead of time, we would only
> > have to apply
On 09/08/2015 03:12 PM, Xishi Qiu wrote:
> The shadow which correspond 16 bytes memory may span 2 or 3 bytes. If the
> memory is aligned on 8, then the shadow takes only 2 bytes. So we check
> "shadow_first_bytes" is enough, and need not to call
> "memory_is_poisoned_1(addr + 15);".
> But the
In current code, max_perf_pct might be smaller than min_perf_pct
by improper user input:
$ grep . /sys/devices/system/cpu/intel_pstate/m*_perf_pct
/sys/devices/system/cpu/intel_pstate/max_perf_pct:100
/sys/devices/system/cpu/intel_pstate/min_perf_pct:100
$ echo 80 >
From: Olliver Schinagl
The Olimex A20 OLinuXino Lime2 features an eeprom that is always on the
board. This patch adds it to the dts.
--Tested-by: Olliver Schinagl
--Signed-off-by: Olliver Schinagl
---
From: Olliver Schinagl
The Olimex A10 OLinuXino Lime features an eeprom that is always on the
board. This patch adds it to the dts.
--Tested-by: Olliver Schinagl
--Signed-off-by: Olliver Schinagl
---
From: Olliver Schinagl
The Olimex A20 OLinuXino Lime features an eeprom that is always on the
board. This patch adds it to the dts.
--Tested-by: Olliver Schinagl
--Signed-off-by: Olliver Schinagl
---
On 09/09/15 05:23, Peter Chen wrote:
> On Mon, Aug 24, 2015 at 04:21:21PM +0300, Roger Quadros wrote:
>> The existing usb_add/remove_hcd() functionality
>> remains unchanged for non-OTG devices. For OTG
>> devices they only register the HCD with the OTG core.
>>
>> Introduce
On Tue, 8 Sep 2015, Shaohua Li wrote:
> On Tue, Sep 08, 2015 at 05:08:03PM +0200, Thomas Gleixner wrote:
> > For non paravirt kernels which can read the TSC directly, we'd need a
> > way to transport that information. A simple mechanism would be to
> > query an emulated MSR from the watchdog which
On Wed, Sep 09, 2015 at 11:16:08AM +0800, Wu, Songjun wrote:
> On 9/8/2015 20:23, Mark Brown wrote:
> >If you want to have three controls you need to write code so that the
> >user can only change one of them from 0dB at once, returning an error
> >otherwise. That was why it looked like they
When printing a bitmap using the "%*pb[l]" printk format
a 16 bit variable (field_width) is used to store the size of the bitmap.
In some cases 16 bits are not sufficient, the variable overflows and
printk does not work as expected.
This patch fixes the problem by changing the type of field_width
On Wednesday 09 September 2015 05:19 AM, Rob Herring wrote:
On 09/07/2015 06:18 AM, Vaibhav Hiremath wrote:
With support for pxa1928 family of devices , this patch
updates the binding document with compatible property
of "marvell,pxav3-1928-sdhci".
Signed-off-by: Vaibhav Hiremath
The current KASAN code can not find the following out-of-bounds
bugs:
char *ptr;
ptr = kmalloc(8, GFP_KERNEL);
memset(ptr+7, 0, 2);
the cause of the problem is the type conversion error in
*memory_is_poisoned_n* function. So this patch fix that.
Signed-off-by: Wang Long
There is no point returning suspend_opp, if it is disabled by the core.
As we can't use it at all. Fix it.
Cc: Bartlomiej Zolnierkiewicz
Fixes: 4eafbd15b6c8 ("PM / OPP: add dev_pm_opp_get_suspend_opp() helper")
Signed-off-by: Viresh Kumar
---
On Tue, Sep 08, 2015 at 03:49:58PM +0900, Joonsoo Kim wrote:
> 2015-08-24 21:09 GMT+09:00 Mel Gorman :
> > __GFP_WAIT has been used to identify atomic context in callers that hold
> > spinlocks or are in interrupts. They are expected to be high priority and
> > have
Hi,
On Wed, Sep 9, 2015 at 1:13 PM, Octavian Purdila
wrote:
> On Wed, Sep 9, 2015 at 2:50 AM, Rafael J. Wysocki wrote:
>>
>> Hi,
>>
>> On Wed, Sep 9, 2015 at 12:25 AM, Ulf Hansson wrote:
>> > On 8 September 2015 at 22:56,
ACPI specifies the following rules when listing APIC IDs:
(1) Boot processor is listed first
(2) For multi-threaded processors, BIOS should list the first logical
processor of each of the individual multi-threaded processors in MADT
before listing any of the second logical processors.
(3)
On 2015/9/9 17:01, Vladimir Murzin wrote:
> On 09/09/15 04:59, Wang Long wrote:
>> The current KASAN code can find the following out-of-bounds
>
> Should it be "cannot"?
>
> Vladimir
>
sorry for that mistake, it should be "cannot".
>> bugs:
>> char *ptr;
>> ptr = kmalloc(8,
ACPI subtable parsing needs to be extended to allow two or more
handlers to be run in the same ACPI table walk, thus adding
acpi_subtable_proc structure which stores
() ACPI table id
() handler that processes table
() counter how many items has been processed
and passing it to
This series of patches attempts to fix how CPUs are enumerated by kernel when
there's more than 255 of them on single processor.
In such case, BIOS may interleave APIC/X2APIC MADT subtables, to obey
requirements
specified in ACPI spec. Without this patches, kernel then would first enumerate
BSP,
llist_del_first reads entry->next, but it did not acquire
visibility over the entry node. As the result it can get
a stale value of entry->next (e.g. NULL or whatever garbage
was there before the appending thread wrote correct value).
And then commit that value as llist head with cmpxchg.
That
; Cc: Thierry Reding <thierry.red...@gmail.com>
> > Cc: Alexandre Courbot <gnu...@gmail.com>
> > Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnier...@samsung.com>
>
> What tree does this apply to?
It applies fine to both next (next-20150909 branch) and curre
On Wed, Sep 9, 2015 at 2:50 AM, Rafael J. Wysocki wrote:
>
> Hi,
>
> On Wed, Sep 9, 2015 at 12:25 AM, Ulf Hansson wrote:
> > On 8 September 2015 at 22:56, Rafael J. Wysocki wrote:
> >> On Tue, Sep 8, 2015 at 9:35 AM, Oliver Neukum
On 08/31/2015 11:23 AM, Michal Hocko wrote:
On Fri 28-08-15 14:43:11, Eric B Munson wrote:
Update the mlock.2 man page with information on mlock2() and the new
mlockall() flag MCL_ONFAULT.
Signed-off-by: Eric B Munson
Cc: Michal Hocko
Acked-by: Michal
Hi All,
Are there any other concerns about this patch series?
Thanks,
Suravee
On 8/26/2015 8:54 PM, Suravee Suthikulpanit wrote:
This patch adds support to setup DMA coherency for PCI device using
the ACPI _CCA attribute. According to the ACPI spec, the _CCA attribute
is required for ARM64.
On Thu, 27 Aug, at 05:04:52PM, joeyli wrote:
>
> The purpose of checking attribute of hibernation key variable is
> in case someone created a key variable on runtime environment _before_
> this kernel create boot service variable. That causes EFI stub may load
> a key that from non-secure
On Thu, 27 Aug, at 06:21:44PM, joeyli wrote:
> On Fri, Aug 21, 2015 at 02:27:53PM +0100, Matt Fleming wrote:
> > On Tue, 11 Aug, at 02:16:29PM, Lee, Chun-Yi wrote:
> > > +static int __init init_hibernation_keys(void)
> > > +{
> > > + struct hibernation_keys *keys;
> > > + int ret = 0;
> > > +
> >
On Tue, Sep 08, 2015 at 05:26:13PM +0900, Joonsoo Kim wrote:
> 2015-08-24 21:30 GMT+09:00 Mel Gorman :
> > The primary purpose of watermarks is to ensure that reclaim can always
> > make forward progress in PF_MEMALLOC context (kswapd and direct reclaim).
> > These
Now that stmmac use dev_xxx, some __func__ are not necessary since their
use was to clearly identify which driver was logging.
This patch remove __func__ where such printing is useless.
Signed-off-by: LABBE Corentin
---
On 09/09/15 01:12, Guenter Roeck wrote:
On 09/08/2015 08:58 PM, Greg KH wrote:
On Tue, Sep 08, 2015 at 06:10:16PM -0700, Guenter Roeck wrote:
Hi Emilio,
On 09/08/2015 05:51 PM, Emilio López wrote:
Hi Greg & Guenter,
[ ... ]
Unless I am missing something, this is not explained anywhere,
Some printing have the function name hardcoded.
It is better to use __func__ instead.
Signed-off-by: LABBE Corentin
---
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
This patch adds the new AXP209 node on the OLinuXino Lime2.
The previously submitted otg enablement patch is needed to avoid merge
conflicts.
Signed-off-by: Olliver Schinagl
Olliver Schinagl (1):
ARM: dts: sun7i: Enable axp209 driver on olinuxino lime2
The number of dummy cycles used during Fast Read commands can be reduced
to improve transfer performances. Each manufacturer has a dedicated set of
registers to provide the memory with the exact number of dummy cycles it
should expect. Both the memory and the (Q)SPI controller must agree on
this
As the hardware description for this chip is the same as the sama5d4, we use
this SoC structures for layers and DC descriptions. Thus only 2 lines are added
to the atmel_hlcdc_of_match table.
The compatible string is already documented in the parent MFD driver's binding.
Signed-off-by: Nicolas
On Wed, 02 Sep, at 06:31:36AM, Kweh Hock Leong wrote:
>
> I have done an experiment on that by using the misc char device file note.
> I included the flush() callback function to the fops. In flush(), I put a
> printk()
> and return -EINVAL. When I perform "cat XXX > /dev/XXX" on Intel Quark
>
On 09/08/2015 01:17 AM, Chunfeng Yun wrote:
> add a DT binding documentation of usb3.0 phy for MT65xx
> SoCs from Mediatek.
>
> Signed-off-by: Chunfeng Yun
Acked-by: Rob Herring
> ---
> .../devicetree/bindings/phy/phy-mt65xx-usb.txt | 69
>
Bitte mein guter Freund
Ich bin mit diesem Medium, um Sie über die Transaktion zur Abgabe von
$ 2150 (einundzwanzig Millionen fünfhunderttausend US-Dollar) auf meinem
Bank in China, Sie als Empfänger zu informieren. Es ist 100% sicher, wobei der
Finanzvorstand des verstorbenen
On Wed, Sep 09, 2015 at 03:04:11PM +0200, Olliver Schinagl wrote:
> Hey all,
>
> After experimenting with a Micron eMMC chip, I made some interesting finds I
> wanted to share with you all.
>
> For a while now, some had hopes or guessed that the A20 could have support
> for 8 bit wide bused on
; > This patch series will move the functions as required and at the end of
>> > the series, allmodconfig builds.
>>
>> I believe it's fixed in the -mm tree and will be merged soon,
>> see the thread at https://lkml.org/lkml/2015/8/26/118
>
> I guess its alre
The stmmac driver use lots of pr_xxx functions to print information.
This is bad since we cannot know which device logs the information.
(moreover if two stmmac device are present)
Furthermore, it seems that it assumes wrongly that all logs will always
be subsequent by using a dev_xxx then some
The asm macros for setting up and restoring the frame pointer aren't
currently being used. However, they will be needed soon to help asm
functions to comply with stacktool.
Rename FRAME/ENDFRAME to FRAME_BEGIN/FRAME_END for more symmetry. Also
make the code more readable and improve the
Align the x86_energy_perf_policy line with the others and restore the
original alphabetical sorting.
Signed-off-by: Josh Poimboeuf
---
tools/Makefile | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/tools/Makefile
From: Marc Zyngier [mailto:marc.zyng...@arm.com]
Sent: Wednesday, September 9, 2015 12:48 PM
> Nit: Please add a version number to the patches you send - this is at
> least the 4th revision of this series, and it is harder to keep track of
> what I'm reviewing. git send-email --subject-prefix
On 26 August 2015 at 19:11, Taku Izumi wrote:
> This patch introduces new boot option named "efi_fake_mem_mirror".
> By specifying this parameter, you can mark specific memory as
> mirrored memory. This is useful for debugging of Address Range
> Mirroring feature.
>
>
On Tue, Sep 08, 2015 at 03:32:46PM -0400, kan.li...@intel.com wrote:
> From: Kan Liang
>
> To generate the frequency and performance output, perf must sample read
> special events like cycles, ref-cycles, msr/tsc/, msr/aperf/ or
> msr/mperf/.
> With the --freq-perf option,
If backing->stolen is true then we were freeing backing by calling
psb_gtt_free_range() but we called it again after unlocking the mutex.
Lets make it NULL after freeing in psb_gtt_free_range() and check for
NULL before calling the function for the second time.
Signed-off-by: Sudip Mukherjee
On Thu, 27 Aug, at 02:11:19AM, Taku Izumi wrote:
> UEFI spec 2.5 introduces new Memory Attribute Definition named
> EFI_MEMORY_MORE_RELIABLE. This patch adds this new attribute
> support to efi_md_typeattr_format().
>
> Signed-off-by: Taku Izumi
> ---
>
ACPI specifies the following rules when listing APIC IDs:
(1) Boot processor is listed first
(2) For multi-threaded processors, BIOS should list the first logical
processor of each of the individual multi-threaded processors in MADT
before listing any of the second logical processors.
(3)
ACPI subtable parsing needs to be extended to allow two or more
handlers to be run in the same ACPI table walk, thus adding
acpi_subtable_proc structure which stores
() ACPI table id
() handler that processes table
() counter how many items has been processed
and passing it to
This series of patches attempts to fix how CPUs are enumerated by kernel when
there's more than 255 of them on single processor.
In such case, BIOS may interleave APIC/X2APIC MADT subtables, to obey
requirements
specified in ACPI spec. Without this patches, kernel then would first enumerate
BSP,
801 - 900 of 1422 matches
Mail list logo