v4l2_fh_init is already done.So call the v4l2_fh_exit in error condition
before returing from the function.
Signed-off-by: Shailendra Verma
---
drivers/media/platform/vsp1/vsp1_video.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/platform/vsp1/vsp1_video.c
b/drivers/medi
On 30 November 2016 at 22:09, Mathias Nyman
wrote:
> On 30.11.2016 11:02, Baolin Wang wrote:
>>
>> If the hardware never responds to the stop endpoint command, the
>> URBs will never be completed, and we might hang the USB subsystem.
>> The original watchdog timer is used to watch if one stop endp
Both functions initialize the file handle with v4l2_fh_init()
and thus need to call clean up with v4l2_fh_exit() as appropriate.
Signed-off-by: Shailendra Verma
---
drivers/staging/media/omap4iss/iss_video.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/media/omap4iss/
On Thu, Dec 01, 2016 at 04:41:40AM +, wangyunjian wrote:
> >-Original Message-
> >From: Jason Wang [mailto:jasow...@redhat.com]
> >Sent: Thursday, December 01, 2016 11:37 AM
> >To: Michael S. Tsirkin
> >Cc: wangyunjian; net...@vger.kernel.org; linux-kernel@vger.kernel.org; caihe
> >Sub
Hi Hari
Personally I like V1 more, but split the patch 2 is easier for ia64
people to reivew. I did basic x86 testing, it runs ok.
On 11/25/16 at 05:24pm, Hari Bathini wrote:
> Get rid of multiple definitions of append_elf_note() & final_note()
> functions. Reuse these functions compiled under C
The File handle is not yet added in the vdev list.So no need to call
v4l2_fh_del(&ctx->fh)if it fails to create control.
Signed-off-by: Shailendra Verma
---
drivers/media/platform/sti/bdisp/bdisp-v4l2.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platfor
On Wed, Nov 30, 2016 at 09:04:13PM -0700, Alex Williamson wrote:
> On Sun, 27 Nov 2016 19:34:17 +0800
> Cao jin wrote:
>
> > It is user space driver's or device-specific driver's(in guest)
> > responsbility
> > to do a serious recovery when error happened. Link-reset is one part of
> > recovery,
Hi Scott,
Thanks for your reminder!
I rephrased it as below:
-#define cputime64_to_clock_t(ct) cputime_to_clock_t((cputime_t)(ct))
+#define cputime64_to_clock_t(ct) \
+ (u64)(cputime_to_clock_t((cputime_t)(ct)))
and rebuilt the kernel, no warnings found.
New patch is attached, coul
On Wed, 30 Nov 2016 19:15:27 -0800
"Luis R. Rodriguez" wrote:
> On Wed, Nov 30, 2016 at 6:51 PM, Nicholas Piggin wrote:
> > On Wed, 30 Nov 2016 18:38:16 +0100
> > "Luis R. Rodriguez" wrote:
> >
> >> On Wed, Nov 30, 2016 at 02:09:47PM +1100, Nicholas Piggin wrote:
> >> What is wrong with that
Kalle Valo writes:
> "Valo, Kalle" writes:
>
>> Bjorn Andersson writes:
>>
>>> On Wed 16 Nov 10:49 PST 2016, Kalle Valo wrote:
>>>
Bjorn Andersson wrote:
> The correct include file for getting errno constants and ERR_PTR() is
> linux/err.h, rather than linux/errno.h, so fix the
On Thu, 1 Dec 2016 16:04:30 +1100
Nicholas Piggin wrote:
> On Wed, 30 Nov 2016 19:15:27 -0800
> "Luis R. Rodriguez" wrote:
>
> > On Wed, Nov 30, 2016 at 6:51 PM, Nicholas Piggin wrote:
> > > On Wed, 30 Nov 2016 18:38:16 +0100
> > > "Luis R. Rodriguez" wrote:
> > >
> > >> On Wed, Nov 30, 201
From: Andreas Pape
Setting pointer and afterwards check for wrap around leads
to the possibility of returning the inconsistent pointer position.
This patch accesses buffer pointer atomically to avoid this issue.
v2: use READ_ONCE and WRITE_ONCE to ensure read/write of buffer pointer in
only
David Miller writes:
> From: Kalle Valo
> Date: Tue, 29 Nov 2016 16:59:44 +0200
>
>> if there's still time here's one more patch to 3.9. I think this is good
>> to have in 3.9 as it fixes an issue where we were printing uninitialised
>> memory in mwifiex. I had this in wireless-drivers already f
Applied
Sorry, for some reason this patch was not present on linux-pm
patchwork, just on lkml patchwork, which I do not review.
thanks,
Len Brown, Intel Open Source Technology Center
On Wed, Nov 30, 2016 at 11:40:19AM -0800, Paul E. McKenney wrote:
> > See commit:
> >
> > 4a81e8328d37 ("rcu: Reduce overhead of cond_resched() checks for RCU")
> >
> > Someone actually wrote down what the problem was.
>
> Don't worry, it won't happen again. ;-)
>
> OK, so the regressions w
On (11/24/16 17:58), Petr Mladek wrote:
[..]
> > +/*
> > + * Lockless printk(), to avoid deadlocks should the printk() recurse
> > + * into itself. It uses a per-CPU buffer to store the message, just like
> > + * NMI.
> > + */
> > +static int vprintk_safe(const char *fmt, va_list args)
> > +{
> > +
On Wed, Nov 30, 2016 at 08:55:30PM -0800, Darren Hart wrote:
> On Thu, Nov 24, 2016 at 04:38:08PM +0100, Peter Zijlstra wrote:
> > > In this path the fixup can return -EFAIL as well, so it should drop
> > > rtmutex
> > > too if it owns it. We should move the rtmutex drop into the fixup
> > > fun
On Thu, Dec 01, 2016 at 11:34:42AM +0900, Sergey Senozhatsky wrote:
> On (11/25/16 16:17), Peter Zijlstra wrote:
> > On Fri, Nov 25, 2016 at 04:01:13PM +0100, Petr Mladek wrote:
> > > On Fri 2016-10-28 00:49:33, Sergey Senozhatsky wrote:
> > > > 2) Since commit cf9b1106c81c ("printk/nmi: flush NMI
Freezing process can abort when a client is waiting uninterruptibly
for a response. Add new macro wait_fatal_freezable to try to fix it.
Signed-off-by: cuilifei
---
fs/fuse/dev.c | 47 +++
1 file changed, 43 insertions(+), 4 deletions(-)
diff --git a/
Hi,
On 11/30/2016 05:02 PM, Baolin Wang wrote:
> If the hardware never responds to the stop endpoint command, the
> URBs will never be completed, and we might hang the USB subsystem.
> The original watchdog timer is used to watch if one stop endpoint
> command is timeout, if timeout, then the watc
Hello Aniroop Mathur
Thank you for your mail.
We have used the usleep_range() function in our new product's driver and the
verification result is working.
Your patch for bma150 is definitely working for sure.
Just one question need your answer.
To replace the msleep(2), is usleep_range(20
On Wed, Nov 30, 2016 at 01:13:03PM -0600, Josh Poimboeuf wrote:
> This question was probably intended for other folks, but I should point
> out that idle tasks *do* invoke the scheduler. cpu_idle_loop() calls
> schedule_preempt_disabled().
Right, but that doesn't matter I think. The below will si
Freezing process can abort when a client is waiting uninterruptibly
for a response. Add new macro wait_fatal_freezable to try to fix it.
Signed-off-by: cuilifei
---
fs/fuse/dev.c | 46 ++
1 file changed, 42 insertions(+), 4 deletions(-)
diff --git a/f
On Wed, Nov 30, 2016 at 12:34:53PM -0800, Andy Lutomirski wrote:
> This reverts commit ed68d7e9b9cfb64f3045ffbcb108df03c09a0f98.
>
> The patch wasn't quite correct -- there are non-Intel (and hence
> non-486) CPUs that we support that don't have CPUID. Since we no
> longer require CPUID for sync_
> [1/3] Add a bug tracking system location entry for cpufreq.
> [2/3] Add a bug tracking system location entry for cpuidle and intel_idle.
> [3/3] Add a new maintainer of intel_idle.
Acked-by: Len Brown
Hi Baolu,
On 1 December 2016 at 13:45, Lu Baolu wrote:
> Hi,
>
> On 11/30/2016 05:02 PM, Baolin Wang wrote:
>> If the hardware never responds to the stop endpoint command, the
>> URBs will never be completed, and we might hang the USB subsystem.
>> The original watchdog timer is used to watch if
On Thu, Nov 24, 2016 at 04:38:08PM +0100, Peter Zijlstra wrote:
> On Thu, Nov 24, 2016 at 04:19:41PM +0100, Thomas Gleixner wrote:
> > On Thu, 24 Nov 2016, Peter Zijlstra wrote:
> >
> > >
> > > While working on the futex code, I stumbled over this potential
> > > use-after-free scenario.
> > >
>
On 1 December 2016 at 14:04, Baolin Wang wrote:
> Hi Baolu,
>
> On 1 December 2016 at 13:45, Lu Baolu wrote:
>> Hi,
>>
>> On 11/30/2016 05:02 PM, Baolin Wang wrote:
>>> If the hardware never responds to the stop endpoint command, the
>>> URBs will never be completed, and we might hang the USB sub
Introduce some helpers for handling the signalling between VIA and
Cuda. This abstraction will be used to add support for Egret devices,
which utilize slightly different signalling.
Don't invert the sense of the Cuda's active-low signals when storing
them in the 'status' variable. Just assert, neg
Change the device probe test in the via-cuda.c driver so it will load on
Egret-based machines too. Remove the now redundant via-maciisi.c driver.
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
arch/m68k/include/asm/macintosh.h | 2 +-
arch/m68k/mac/config.c| 18 +-
arch/m6
If the Cuda driver does not enter the 'read_done' state for some
reason, it may continue in the 'reading' state until the buffer
overflows. Add a bounds check to prevent this.
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/macintosh/via-cuda.c | 8 +++-
1 file changed, 7 inse
The cuda_start() function uses spinlock_irq_save/restore for mutual
exclusion. Let's have cuda_poll() do the same when polling the VIA
interrupt.
The benefit to disabling local irqs when the interrupt is being polled
is that the interrupt handler now has the same timing properties
regardless of wh
There is no possibility that current_req can change during execution of
cuda_start(). This can be confirmed by inspection: cuda_lock is always
held whenever cuda_start() is called or current_req is modified.
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/macintosh/via-cuda.c | 8
This patch series has some improvements for the the Cuda driver: cleanup,
bug fixes and new functionality.
The broken via-maciisi driver is then replaced by via-cuda. This
eliminates over 600 LoC.
Thanks to Stan Johnson for testing these patches on a Mac LC III and
a PowerMac G3.
Finn Thain (10
The Egret system controller was the predecessor to the Cuda and the
differences are minor.
On Cuda, byte acknowledgement requires one transition of the TACK
signal; on Egret two are needed. On Cuda, TIP is active low; on Egret
it is active high. And Cuda raises certain interrupts that Egret omits.
Applied.
thanks!
Len Brown, Intel Open Source Technology Center
Add missing log message severity, remove old debug messages and
replace printk() loop with print_hex_dump() call.
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/macintosh/via-cuda.c | 26 ++
1 file changed, 6 insertions(+), 20 deletions(-)
diff --git a/dr
Initialize data_index where appropriate to improve readability and
assist debugging. This change doesn't affect driver behaviour.
I prefer to see
current_req->data[data_index++]
in place of
current_req->data[0]
or
current_req->data[1]
inasmuchas it becomes obvious what the
When a read transaction completes, one of several things will happen:
either a new transfer is started by the driver, a new transfer request
is raised by the Cuda (i.e. TREQ asserted), or both happen at once.
When both happen at once, there is a race condition between the TREQ test
in the read_don
When reading_reply is set, reply_ptr points into an adb_request struct.
Hence, when reply_ptr instead points into the global cuda_rbuf,
it must be the case that reading_reply is not set.
Unfortunately, this rule can be violated because re-initialization
of reply_ptr and reading_reply presently de
On Wed, Nov 30, 2016 at 10:24:59PM +0100, Vlastimil Babka wrote:
> [add more CC's]
>
> On 11/30/2016 09:19 PM, Robin H. Johnson wrote:
> > Somewhere in the Radeon/DRM codebase, CMA page allocation has either
> > regressed in the timeline of 4.5->4.9, and/or the drm/radeon code is
> > doing somethi
Fix bug https://bugzilla.kernel.org/show_bug.cgi?id=188551. A negative
return value means there are errors, while 0 indicates success. However,
in function bpa10x_send_frame(), it returns 0 no matter whether
usb_submit_urb() returns a negative value. As a result, the caller of
bpa10x_send_frame() m
Fix bug https://bugzilla.kernel.org/show_bug.cgi?id=188561. Function
wm831x_clkout_is_prepared() returns "true" when it fails to read
CLOCK_CONTROL_1. "true" means the device is already prepared. So
return "true" on the read failure seems improper.
Signed-off-by: Pan Bian
---
drivers/clk/clk-wm8
Commit fixed to handle the ifdef CONFIG_CIFS_SMB2 disabled problem you
noted, and repushed to my for-next branch. Thx for pointing this out.
On Tue, Nov 29, 2016 at 4:27 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the cifs tree, today's linux-next build (powerpc
> ppc64_defconfig) fai
On Thu, 2016-12-01 at 06:14 +, Rohit Thapliyal wrote:
> Hi,
>
Hi,
Do not top post on netdev, and do not use HTML format : it wont reach
netdev.
>
> Found at just one place in ping_v6_sendmsg, where np is checked for
> NULL.
>
> And I am not sure, if it is really required there also.
>
Hi,
On 12/01/2016 02:04 PM, Baolin Wang wrote:
> Hi Baolu,
>
> On 1 December 2016 at 13:45, Lu Baolu wrote:
>> Hi,
>>
>> On 11/30/2016 05:02 PM, Baolin Wang wrote:
>>> If the hardware never responds to the stop endpoint command, the
>>> URBs will never be completed, and we might hang the USB subs
Hi all,
Changes since 20161130:
New tree: openrisc
The cifs tree lost its build failure.
The net-next tree gained conflicts against the net and arm-soc trees.
The block tree gained a build failure for which I applied a merge
fix patch.
The tip tree gained a conflict against the net-next tree
Piotr,
Thanks for sending the patch, I've made this change to my turbostat
branch for 4.10.
I did not apply your patch directly because for some reason it didn't
appear in patchwork for linux-pm,
only for lkml, which I do not review.
Also, your patch depended on your style update patch to use the
results are here ... the culprit is, again, commit 2d66cccd73 ("mm:
Prevent __alloc_pages_nodemask() RCU CPU stall warnings"), and reverting that
patch fixes the problem. Good that you dropped it already :-).
Guenter
---
# bad: [59ab0083490c8a871b51e893bae5806e55901d7e
Hello Takashi
On 11/30/2016 05:54 PM, Takashi Iwai wrote:
On Wed, 30 Nov 2016 08:59:21 +0100,
Jiada Wang wrote:
From: Andreas Pape
since commit 57e6dae1087bbaa6b33d3dd8a8e90b63888939a3 the expected packetsize
is always limited to
Please use a form with 12 chars SHA ID plus the commit subj
Hi Takashi
On 11/30/2016 05:51 PM, Takashi Iwai wrote:
On Wed, 30 Nov 2016 08:59:22 +0100,
Jiada Wang wrote:
From: Daniel Girnus
ALSA usually calls the prepare function twice before starting the playback:
1. On hw_params call from userland and
2. internally when starting the stream.
Some dev
On Wed, Nov 30, 2016 at 11:49:56AM -0500, Martin K. Petersen wrote:
> > "Greg" == Greg Kroah-Hartman writes:
>
> Greg,
>
> Greg> From: Andrey Grodzovsky
>
> Greg> commit 18f6084a989ba1b38702f9af37a2e4049a924be6 upstream.
>
> Please also queue 7ff723ad0f87 ("scsi: mpt3sas: Unblock device a
Fix bug https://bugzilla.kernel.org/show_bug.cgi?id=188591. In function
ioat_dma_self_test(), when the calls to dma_mapping_error() fails, the
value of return variable err is 0 (indicates no error). As a result, the
return value may be inconsistent with the execution status. This patch
fixes the bu
On Wed, Nov 30, 2016 at 08:39:35AM -0800, Kevin Hilman wrote:
> kernelci.org bot writes:
>
> > stable-rc boot: 226 boots: 6 failed, 214 passed with 5 offline, 1 conflict
> > (v4.8.11-37-g70e9fe5f6b13)
> >
> > Full Boot Summary:
> > https://kernelci.org/boot/all/job/stable-rc/kernel/v4.8.11-37-g
On Wed, Nov 30, 2016 at 09:04:28AM -0700, Shuah Khan wrote:
> On 11/30/2016 02:29 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.8.12 release.
> > There are 37 patches in this series, all will be posted as a response
> > to this one. If anyone has any issu
On Wed 30-11-16 20:19:03, Robin H. Johnson wrote:
[...]
> alloc_contig_range: [83f2a3, 83f2a4) PFNs busy
Huh, do I get it right that the request was for a _single_ page? Why do
we need CMA for that?
--
Michal Hocko
SUSE Labs
On Wed, Nov 30, 2016 at 03:34:29PM -0800, Guenter Roeck wrote:
> On Wed, Nov 30, 2016 at 10:29:37AM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.8.12 release.
> > There are 37 patches in this series, all will be posted as a response
> > to this one. I
On Wed, Nov 30, 2016 at 11:59:49PM +, csmanjuvi...@gmail.com wrote:
> From: Manjunath Goudar
>
> The ohci_hcd_pxa27x_drv_probe function is not doing anything other
> than calling usb_hcd_pxa27x_probe function so ohci_hcd_pxa27x_drv_probe
> function is useless that is why removed ohci_hcd_pxa2
On Thu, 01 Dec 2016 03:29:23 +0100,
Dmitry Torokhov wrote:
>
> Hi Takashi,
>
> On Mon, Nov 28, 2016 at 02:56:36PM +0100, Takashi Iwai wrote:
> > Hi Dmitry,
> >
> > I've been testing a small machine with Intel Cherry Trail chipset, and
> > noticed that the kernel spews errors always like:
> >
>
Forgot to CC Joonsoo. The email thread starts more or less here
http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz
On Thu 01-12-16 08:15:07, Michal Hocko wrote:
> On Wed 30-11-16 20:19:03, Robin H. Johnson wrote:
> [...]
> > alloc_contig_range: [83f2a3, 83f2a4) PFNs busy
>
> Huh, do I
Hi Michal,
[auto build test ERROR on net/master]
url:
https://github.com/0day-ci/linux/commits/Michal-Kubecek/tipc-check-minimum-bearer-MTU/20161201-140555
config: i386-randconfig-s0-201648 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the att
On Wed, Nov 30, 2016 at 11:10:41PM +0530, Amitesh Singh wrote:
> On Nov 30, 2016 02:26, "Greg KH" wrote:
> >
> > On Mon, Nov 28, 2016 at 05:55:29PM +0530, Amitesh Singh wrote:
> > > Signed-off-by: Amitesh Singh
> > > ---
> >
> > I can't take patches without a changelog text :(
>
> did you mean t
Fix bug https://bugzilla.kernel.org/show_bug.cgi?id=188601. This patch
is based on "0001-dma-ioat-set-error-code-on-failures.patch". In this
patch, assign error code -ENOMEM to return variable err as long as the
call to dma_mapping_error() fails.
Signed-off-by: Pan Bian
---
drivers/dma/ioat/init
On 1 December 2016 at 14:35, Lu Baolu wrote:
> Hi,
>
> On 12/01/2016 02:04 PM, Baolin Wang wrote:
>> Hi Baolu,
>>
>> On 1 December 2016 at 13:45, Lu Baolu wrote:
>>> Hi,
>>>
>>> On 11/30/2016 05:02 PM, Baolin Wang wrote:
If the hardware never responds to the stop endpoint command, the
U
On 12/01/2016 07:21 AM, Robin H. Johnson wrote:
On Wed, Nov 30, 2016 at 10:24:59PM +0100, Vlastimil Babka wrote:
[add more CC's]
On 11/30/2016 09:19 PM, Robin H. Johnson wrote:
> Somewhere in the Radeon/DRM codebase, CMA page allocation has either
> regressed in the timeline of 4.5->4.9, and/or
On Wed, Nov 30, 2016 at 09:02:49AM -0800, Davidlohr Bueso wrote:
> On Wed, 30 Nov 2016, Greg KH wrote:
> > What changed from v1? Please always include it below the --- line to
> > keep maintainer's semi-sane.
>
> If anything changed I would have -- this is only the From != SoB thing
> you were co
Jiada Wang wrote:
> since commit 57e6dae1087bbaa6b33d3dd8a8e90b63888939a3 the expected packetsize
> is always limited to
> nominal + 25%. It was discovered, that some devices
Which devices?
> have a much higher jitter in used packetsizes than 25%
How high? (Please note that the USB specificati
From: MaJun
The return value 0 from acpi_register_gsi() means irq mapping failed.
So, we should process this case in else branch.
Signed-off-by: MaJun
---
drivers/acpi/resource.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource
On 12/01/2016 08:21 AM, Michal Hocko wrote:
Forgot to CC Joonsoo. The email thread starts more or less here
http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz
On Thu 01-12-16 08:15:07, Michal Hocko wrote:
On Wed 30-11-16 20:19:03, Robin H. Johnson wrote:
[...]
> alloc_contig_range:
sorry, ignore this one..
在 2016/12/1 15:41, Majun 写道:
> From: MaJun
>
> The return value 0 from acpi_register_gsi() means irq mapping failed.
> So, we should process this case in else branch.
>
> Signed-off-by: MaJun
> ---
> drivers/acpi/resource.c | 2 +-
> 1 file changed, 1 insertion(+), 1
Hi,
On 12/01/2016 03:35 PM, Baolin Wang wrote:
> On 1 December 2016 at 14:35, Lu Baolu wrote:
>> Hi,
>>
>> On 12/01/2016 02:04 PM, Baolin Wang wrote:
>>> Hi Baolu,
>>>
>>> On 1 December 2016 at 13:45, Lu Baolu wrote:
Hi,
On 11/30/2016 05:02 PM, Baolin Wang wrote:
> If the hard
From: MaJun
Add a new flag for ITS node in DT mode so we can disable/enable the
indirect route function.
Signed-off-by: MaJun
---
drivers/irqchip/irq-gic-v3-its.c | 16 +++-
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/ir
From: MaJun
For current ITS driver, two level table (indirect route) is enabled when the
memory used
for LPI route table over the limit(64KB * 2) size. But this function impact the
performance of LPI interrupt actually because need more time to look up the
table.
Although this function can sa
From: MaJun
Add the two-level-route property in ITS node.
When this property string defined, two-level route(indirect) function
will be enabled in ITS driver, otherwise disable it.
Signed-off-by: MaJun
---
Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 3 +++
1 file ch
From: MaJun
Add a new flag to control indirect route function for ACPI mode.
To carry the user defined flags information, we used the reserved byte
in ITS MADT table
Signed-off-by: MaJun
---
drivers/irqchip/irq-gic-v3-its.c | 5 -
include/acpi/actbl1.h| 3 ++-
2 files changed,
Hi, Rafael
> From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of Rafael J.
> Wysocki
> Subject: Re: [PATCH 02/11] ACPICA: Back port of "ACPICA: Dispatcher: Tune
> interpreter lock around
> AcpiEvInitializeRegion()"
>
> On Wed, Nov 30, 2016 at 8:20 AM, Lv Zheng wrote:
> > ACPICA
On Wed 30-11-16 12:04:31, Ross Zwisler wrote:
> On Tue, Nov 29, 2016 at 09:53:03AM +0100, Jan Kara wrote:
> > On Mon 28-11-16 12:15:04, Ross Zwisler wrote:
> > > On Thu, Nov 24, 2016 at 10:02:39AM +0100, Jan Kara wrote:
> > > > On Wed 23-11-16 11:44:17, Ross Zwisler wrote:
> > > > > With the curren
On 28/11/16 21:16, Zach Brown wrote:
> On NI 9037 boards the max SDIO frequency is limited by trace lengths
> and other layout choices. The max SDIO frequency is stored in an ACPI
> table.
>
> The driver reads the ACPI entry MXFQ during sdio_probe_slot and sets the
> f_max field of the host.
>
>
On 28/11/16 21:16, Zach Brown wrote:
> Add PCI ID for Intel byt sdio host controller sub-vended by NI.
>
> The controller has different behavior because of the board layout NI
> puts it on.
>
> Signed-off-by: Zach Brown
Acked-by: Adrian Hunter
> ---
> drivers/mmc/host/sdhci-pci-core.c | 24 +
On Thu, Dec 01, 2016 at 08:38:15AM +0100, Vlastimil Babka wrote:
> >> By default config this should not be used on x86.
> > What do you mean by that statement?
>
> I mean that the 16 mbytes for generic CMA area is not a default on x86:
>
> config CMA_SIZE_MBYTES
> int "Size in Mega Bytes
801 - 880 of 880 matches
Mail list logo
