On Tue, Mar 14, 2017 at 06:57:02PM +0200, Daniel Baluta wrote:
> bclk is derived from sysclk with the help of bclk_divs. Anyhow, for
> S20_3LE format there is no bclk_divs that could be used to derive
> an exact bclk.
>
> We can fix this by using storage size instead the exact
> number of bits of
On Mon, Mar 6, 2017 at 5:46 PM, Charles Keepax
wrote:
> Now the wm831x-core has basic DT support we can update this driver to
> allow use of the GPIOs within a device tree system.
>
> Signed-off-by: Charles Keepax
> Acked-by: Linus Walleij
Patch applied.
Yours,
Linus Walleij
On Tue, Mar 14, 2017 at 02:52:34PM +, Suzuki K Poulose wrote:
> In kvm_free_stage2_pgd() we don't hold the kvm->mmu_lock while calling
> unmap_stage2_range() on the entire memory range for the guest. This could
> cause problems with other callers (e.g, munmap on a memslot) trying to
> unmap a
On Tue 14-03-17 08:47:29, Ingo Molnar wrote:
>
> * Kirill A. Shutemov wrote:
>
> > Here's the first bunch of patches of 5-level patchset. Let's see if I'm on
> > right track addressing Ingo's feedback. :)
> >
> > These patches prepare x86 code to be switched from
> >
> > to . It's a stepping
From: Gabriel Fernandez
This patch enables clocks for STM32H743 boards.
Signed-off-by: Gabriel Fernandez
---
.../devicetree/bindings/clock/st,stm32h7-rcc.txt | 152 ++
drivers/clk/Makefile |1 +
drivers/clk/clk-stm32h7.c | 1586
Am Dienstag, den 14.03.2017, 21:14 +0100 schrieb Tobias Herzog:
> USB devices may have very limitited endpoint packet sizes, so that
> notifications can not be transferred within one single usb packet.
> Reassembling of multiple packages may be necessary.
Hi,
thank you for the patch.
Am Dienstag, den 14.03.2017, 21:14 +0100 schrieb Tobias Herzog:
> Notifications may only be 8 bytes so long. Accessing the 9th and
> 10th byte of unimplemented/unknown notifications may be insecure.
> Also check the length of known notifications before accessing anything
> behind the 8th byte.
>
Yes, exactly that.
Christian.
Am 15.03.2017 um 09:25 schrieb Zhou, David(ChunMing):
Does that means we don't need invisible vram later?
David
-Original Message-
From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
Christian K?nig
Sent: Wednesday, March 15,
Geert Uytterhoeven writes:
> On Wed, Mar 15, 2017 at 1:19 AM, Michael Ellerman wrote:
>> Geert Uytterhoeven writes:
>>> Submitters of device tree binding documentation may forget to CC
>>> the subsystem maintainer if this is missing.
>>>
>>> Signed-off-by: Geert Uytterhoeven
>>> Cc: Benjamin
Before this patch, clust1 has little core0~3, clust0 has big core0~3
cpu_l | cpu0 |
cpu_l | cpu1 | clust1
cpu_l | cpu2 |
cpu_l | cpu3 |
--
cpu_b | cpu4 |
cpu_b | cpu5 | clust0
cpu_b | cpu6 |
cpu_b | cpu7 |
With this patch, clust0 will have little core0~3, clust1 will have big
On Mon, Mar 6, 2017 at 9:06 PM, Nathan Sullivan wrote:
> The GPIO-based NAND controller on National Instruments 169445 hardware
> exposes a set of simple lines for the control signals.
>
> Signed-off-by: Nathan Sullivan
Totally standard ans simple patch, applied.
Hint: it's probably nice to
On Wed, 15 Mar 2017, Arushi Singhal wrote:
> HiThis Patch series is not yet added to the kernel tree.
The normal process is to send it again, with RESEND inside the [PATCH]
box.
julia
> Thanks
> Arushi
>
> On Saturday, 11 March 2017 02:12:02 UTC+5:30, Arushi Singhal wrote:
> Improve
On 15/03/17 09:17, Christoffer Dall wrote:
> On Tue, Mar 14, 2017 at 02:52:32PM +, Suzuki K Poulose wrote:
>> From: Marc Zyngier
>>
>> We don't hold the mmap_sem while searching for the VMAs when
>> we try to unmap each memslot for a VM. Fix this properly to
>> avoid unexpected results.
>>
>>
On Mon, Mar 6, 2017 at 9:06 PM, Nathan Sullivan wrote:
> Support the National Instruments 169445 board.
>
> Signed-off-by: Nathan Sullivan
(...)
> + gpio1:gpio-controller@1f300010 {
> + compatible = "ni,169445-nand-gpio";
> + reg =
Hi Michael,
On Wed, Mar 15, 2017 at 10:30 AM, Michael Ellerman wrote:
> Geert Uytterhoeven writes:
>> On Wed, Mar 15, 2017 at 1:19 AM, Michael Ellerman
>> wrote:
>>> Geert Uytterhoeven writes:
Submitters of device tree binding documentation may forget to CC
the subsystem maintainer
On 15/03/17 09:21, Christoffer Dall wrote:
> On Tue, Mar 14, 2017 at 02:52:34PM +, Suzuki K Poulose wrote:
>> In kvm_free_stage2_pgd() we don't hold the kvm->mmu_lock while calling
>> unmap_stage2_range() on the entire memory range for the guest. This could
>> cause problems with other callers
On 14/03/17 18:35, Vitaly Kuznetsov wrote:
> All code to support Xen PV will get under this new option. For the
> beginning, check for it in the common code.
>
> Signed-off-by: Vitaly Kuznetsov
> ---
> Changes since v2:
>select XEN_HAVE_PVMMU moved to config XEN_PV [Juergen Gross]
> ---
On 14/03/17 18:35, Vitaly Kuznetsov wrote:
> As a preparation to splitting the code we need to untangle it:
>
> x86_hyper_xen -> x86_hyper_xen_hvm and x86_hyper_xen_pv
> xen_platform() -> xen_platform_hvm() and xen_platform_pv()
> xen_cpu_up_prepare() -> xen_cpu_up_prepare_pv() and
On Wed, Mar 15, 2017 at 10:18:31AM +0100, Linus Walleij wrote:
> On Mon, Mar 6, 2017 at 5:46 PM, Charles Keepax
> wrote:
>
> > Now the wm831x-core has basic DT support we can update this driver to
> > allow use of the GPIOs within a device tree system.
> >
> > Signed-off-by: Charles Keepax
> >
On Tue, Mar 7, 2017 at 2:31 PM, Neil Armstrong wrote:
> Signed-off-by: Neil Armstrong
Patch applied for fixes.
Yours,
Linus Walleij
Hello Akshay,
Am 15.03.2017 um 05:44 schrieb Akshay Bhat:
Hi Wolfgang,
On Tue, Mar 14, 2017 at 2:08 PM, Wolfgang Grandegger
wrote:
...snip
/disconnect cable
can0 2088 [8] 00 00 00 19 00 00 28 00 ERRORFRAME
protocol-violation{{}{acknowledge-slot}}
On 14/03/17 18:35, Vitaly Kuznetsov wrote:
> Changes since v2:
> - Rebase to 4.11.0-rc1+
> - XEN_HAVE_PVMMU moved to config XEN_PV [Juergen Gross]
> - .pin_vcpu kept for x86_hyper_xen_hvm to support PVH Dom0 in future
>[Juergen Gross]
> - 'extern' qualifiers dropped from newly introduced
On March 15, 2017 5:00 PM Aaron Lu wrote:
> void tlb_finish_mmu(struct mmu_gather *tlb, unsigned long start, unsigned
> long end)
> {
> + struct batch_free_struct *batch_free, *n;
> +
s/*n/*next/
> tlb_flush_mmu(tlb);
>
> /* keep the page table cache within bounds */
>
On Tue, Mar 7, 2017 at 2:31 PM, Neil Armstrong wrote:
> Fix some inverted bit numbers in some pinctrl groups and add missing pins
> and groups to be in pair with the GXBB pinctrl pins definition.
>
> Signed-off-by: Neil Armstrong
This does not apply on my fixes branch and possibly no other
On Tue, Mar 7, 2017 at 2:31 PM, Neil Armstrong wrote:
> Add pinctrl pins nodes following the additions of missing pins in the pinctrl
> driver.
>
> Signed-off-by: Neil Armstrong
Acked-by: Linus Walleij
Please funnel this through ARM SoC or wherever meson dts files
go.
Yours,
Linus Walleij
On Tue, Mar 7, 2017 at 6:54 PM, Tony Lindgren wrote:
> * Fabio Estevam [170307 09:39]:
>> Hi Gary,
>>
>> On Tue, Mar 7, 2017 at 2:26 PM, Gary Bisson
>> wrote:
>>
>> > No it isn't because of the use of radix but instead of:
>> >
On Thu, Mar 9, 2017 at 3:52 PM, Neil Armstrong wrote:
> This patch describes the GPIO lines usage on the Odroid-C2 board.
>
> This is useful in the debugfs gpio file and using the cdev gpio API.
>
> Signed-off-by: Neil Armstrong
Very helpful.
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
On Mon, Mar 13, 2017 at 02:12:54PM +0200, Andy Shevchenko wrote:
> On Mon, Mar 13, 2017 at 1:11 PM, Eva Rachel Retuya
> wrote:
>
Hello Andy,
Thanks for the review.
> Missed commit message is no-no!
>
> > Signed-off-by: Eva Rachel Retuya
>
> > -int adxl345_core_probe(struct device *dev,
On 03/15/2017 10:43 AM, Linus Walleij wrote:
> On Tue, Mar 7, 2017 at 2:31 PM, Neil Armstrong
> wrote:
>
>> Fix some inverted bit numbers in some pinctrl groups and add missing pins
>> and groups to be in pair with the GXBB pinctrl pins definition.
>>
>> Signed-off-by: Neil Armstrong
>
> This
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The following patchset introduces a new coccinelle patch,
> irq_chip_raw_spinlock.cocci, which is used to identify irq_chip implementors
> which acquire/release non-raw spinlocks, and in addition, a set of generated
> patches for most
From: Suniel Mahesh
Fixed the following checkpatch.pl warning:
line over 80 characters
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for easy review
as suggested by Greg K-H
- New patch addition to the series
- Rebased on top of next-20170310
From: Suniel Mahesh
Fixed unbalanced braces around else statement
Add braces on all arms of the if-else statements to comply with
kernel coding style.
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for easy review
as suggested by Greg K-H
-
From: Suniel Mahesh
Fixed the following checkpatch.pl warning:
Possible unnecessary 'out of memory' message
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for easy review
as suggested by Greg K-H
- Modified subject and description for better
From: Suniel Mahesh
Fixed the following checkpatch.pl checks:
spaces preferred around that 'operator', spacing provided
Logical continuations should be on the previous line, modified accordingly
Unnecessary parentheses around variables, removed
Please use a blank line after
From: Suniel Mahesh
Fixed the following checkpatch.pl checks:
Blank lines aren't necessary after an open brace '{'
and before a close brace '}', removed
No space is necessary after a cast, removed
Please don't use multiple blank lines, removed
Signed-off-by: Suniel Mahesh
---
Changes for v3:
From: Suniel Mahesh
This patch simplifies code by replacing explicit NULL comparison
with ! or unmark operator
Reported by checkpatch.pl for comparison to NULL could be
written '!foo' or 'foo'
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for
From: Suniel Mahesh
Fixed the following checkpatch.pl warnings:
Block comments should align the * on each line
Block comments use * on subsequent lines
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for easy review
as suggested by Greg K-H
-
From: Suniel Mahesh
Split earlier patches into multiple commits for easy review as
suggested by Dan Carpenter.
Modified subject, description and in few patches both for
better readability as suggested by Greg KH.
Fixed the following issues reported by checkpatch.pl:
Block comments should align
From: Suniel Mahesh
Replaced sizeof(struct foo) into sizeof(*ptr), found by checkpatch.pl
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for easy review
as suggested by Greg K-H
- Modified description for better readability
- Rebased on top of
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The altera gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a real-time
> kernel.
On Mon, Mar 13, 2017 at 09:47:57AM +, James Hogan wrote:
> >
> > Note that the corruption is different across reboots, both in the size
> > of the corruption and the location. I saw 1900~ and 1400~ byte
> > sequences corrupted on separate occasions, which don't correspond to
> > the system's
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The 104-dio-48e gpio driver currently implements an irq_chip for
> handling interrupts; due to how irq_chip handling is done, it's
> necessary for the irq_chip methods to be invoked from hardirq context,
> even on a a real-time kernel.
Hi Heiko
On 03/15/2017 05:03 PM, Heiko Stübner wrote:
Am Mittwoch, 15. März 2017, 16:42:30 CET schrieb Chris Zhong:
For RK3399, the grf clock should be controlled by dw-mipi-dsi driver,
add the description for this clock.
Signed-off-by: Chris Zhong
---
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The bcm-kona gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel.
On Fri, Mar 10, 2017 at 6:28 PM, Ray Jui wrote:
> Is such API use change well accepted by the open source community already?
The raw_*spinlock APIs are in the kernel header files and used at several
sites in the kernel, so yes.
Yours,
Linus Walleij
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The ath79 gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The etraxfs gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel.
On Tue, 14 Mar 2017, Bjorn Helgaas wrote:
> On Tue, Mar 14, 2017 at 07:24:14PM -0700, Andi Kleen wrote:
> > > I agree that it should be fairly safe to do ECAM/MMCONFIG without
> > > locking. Can we handle the decision part by adding a "lockless" bit
> > > to struct pci_ops? Old ops don't mention
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The pl061 gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because
On 2017-03-14 19:16, Dan Carpenter wrote:
> Looks good!
Thanks, now pushed out to the for-next branch of
https://gitlab.com/peda-linux/mux.git
Cheers,
peda
From: Chen Liang
The rk3328 soc need more pin function index for pinctrl.
Signed-off-by: Chen Liang
---
include/dt-bindings/pinctrl/rockchip.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/dt-bindings/pinctrl/rockchip.h
b/include/dt-bindings/pinctrl/rockchip.h
index
From: Chen Liang
The rk3328 saradc is the same as rk3399.
Signed-off-by: Chen Liang
---
Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt
From: Chen Liang
The rk3328 i2c is the same as rk3399
Signed-off-by: Chen Liang
---
Documentation/devicetree/bindings/i2c/i2c-rk3x.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-rk3x.txt
b/Documentation/devicetree/bindings/i2c/i2c-rk3x.txt
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The ws16c48 gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel.
From: Liang Chen
These patchs depend on pinctrl patchs as below:
https://patchwork.kernel.org/patch/9566427/
https://patchwork.kernel.org/patch/9566425/
https://patchwork.kernel.org/patch/9566431/
Chen Liang (7):
include: dt-bindings: Add pin function index definition for rockchip
From: Chen Liang
Signed-off-by: Chen Liang
---
Documentation/devicetree/bindings/soc/rockchip/grf.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/soc/rockchip/grf.txt
b/Documentation/devicetree/bindings/soc/rockchip/grf.txt
index a0685c2..db4da0b
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The zx gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because
On Tue, 7 Mar 2017, Hans de Goede wrote:
> On 07-03-17 10:18, Thomas Gleixner wrote:
> > I'm a bit worried about this being hardcoded for that particular use
> > case. That also means that you cannot use the generic regmap irq handling
> > stuff and need to have your own irq magic there.
>
>
Hello!
On 3/15/2017 12:23 AM, Philippe Reynes wrote:
The function gem_begin_auto_negotiation dereference
the pointer ep before testing if it's null. This
patch add a check on ep before dereferencing it.
This issue was added by the patch 92552fdd557:
"net: sun: sungem: use new api
On Wed, Mar 15, 2017 at 8:21 AM, Gerd Hoffmann wrote:
> Hi,
>
>> First the flipping of the mmc host driver for the SD card slot will
>> cause issues for users that build it as a module. When I tested this
>> on Fedora the first update I ended up with a system that didn't boot.
>
> Yep,
On Tue, Mar 14, 2017 at 01:30:30PM -0700, Laura Abbott wrote:
> On 03/14/2017 01:13 PM, Daniel Vetter wrote:
> > On Tue, Mar 14, 2017 at 01:04:19PM -0700, Laura Abbott wrote:
> >>
> >> dma-buf is designed to share buffers. Sharing means that there needs to
> >> be another subsystem to accept those
On Tue, 14 Mar 2017, Krzysztof Kozlowski wrote:
> The MFD-specific header will go away because it duplicates defines from
> exynos-regs-pmu.h.
>
> Reported-by: kbuild test robot
> Signed-off-by: Krzysztof Kozlowski
> Reviewed-by: Bartlomiej Zolnierkiewicz
> ---
> drivers/mfd/exynos-lpass.c |
Am Mittwoch, 15. März 2017, 17:55:23 CET schrieb Chris Zhong:
> Hi Heiko
>
> On 03/15/2017 05:03 PM, Heiko Stübner wrote:
> > Am Mittwoch, 15. März 2017, 16:42:30 CET schrieb Chris Zhong:
> >> For RK3399, the grf clock should be controlled by dw-mipi-dsi driver,
> >> add the description for this
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote:
> The bcm pinctrl drivers currently implement an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel.
On Tue, 14 Mar 2017, Andy Shevchenko wrote:
> On Tue, 2017-03-14 at 15:02 +, Lee Jones wrote:
> > On Mon, 13 Mar 2017, Andy Shevchenko wrote:
> >
> > > Crystal Cove and Whiskey Cove are two different PMICs which are
> > > installed on Intel Atom SoC based platforms.
> > >
> > > Moreover
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote:
> The amd pinctrl drivers currently implement an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel.
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote:
> The sirf atlas7 pinctrl drivers currently implement an irq_chip for
> handling interrupts; due to how irq_chip handling is done, it's
> necessary for the irq_chip methods to be invoked from hardirq context,
> even on a a real-time kernel.
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote:
> The sunxi pinctrl driver currently implement an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel.
On Wed, Mar 15, 2017 at 03:21:51PM +0530, suni...@techveda.org wrote:
> @@ -1796,7 +1796,7 @@ static short _rtl92e_alloc_rx_ring(struct net_device
> *dev)
>
> for (rx_queue_idx = 0; rx_queue_idx < MAX_RX_QUEUE; rx_queue_idx++) {
> priv->rx_ring[rx_queue_idx] =
On Wed, Mar 15, 2017 at 5:52 AM, Cong Wang wrote:
> On Fri, Mar 10, 2017 at 12:04 PM, Dmitry Vyukov wrote:
>> On Fri, Mar 10, 2017 at 8:46 PM, Marcelo Ricardo Leitner
>> wrote:
>>> On Fri, Mar 10, 2017 at 4:11 PM, Dmitry Vyukov wrote:
Hello,
I've got the following recursive
Also the subject is too vague.
regards,
dan carpenter
On Wed, Mar 8, 2017 at 8:35 PM, Nathan Sullivan wrote:
> The GPIO-based NAND controller on National Instruments 169445 hardware
> exposes a set of simple lines for the control signals.
>
> Signed-off-by: Nathan Sullivan
Oh a newer patch with comments exist. I take out the other patch then
and
On Wed, Mar 15, 2017 at 03:21:52PM +0530, suni...@techveda.org wrote:
> From: Suniel Mahesh
>
> Fixed the following checkpatch.pl warning:
> Possible unnecessary 'out of memory' message
>
> Signed-off-by: Suniel Mahesh
> ---
> Changes for v3:
>
> - Split earlier patches into multiple commits
On Friday, March 3, 2017 11:43:00 AM CET Jin Yao wrote:
> v4: Remove the options "--inline-line" and "--inline-name". Just use
> a new option "--inline" to print the inline function information.
> The policy is if the inline function name can be resolved then
> print the name in
Currently we are adding all components from the dts, if one of their
drivers been disabled, we would not be able to bring up others.
Refactor component match logic, follow exynos drm.
Signed-off-by: Jeffy Chen
Reviewed-by: Andrzej Hajda
---
Changes in v3:
Address Andrzej Hajda 's comments.
On Tue, 14 Mar 2017, Enric Balletbo i Serra wrote:
> On 14/03/17 14:59, Lee Jones wrote:
> > On Tue, 14 Feb 2017, Enric Balletbo i Serra wrote:
> >
> >> From: Stephen Barber
> >>
> >> If the EC supports RTC host commands, expose an RTC device.
> >>
> >> Signed-off-by: Stephen Barber
> >>
On Wed, Mar 15, 2017 at 03:21:54PM +0530, suni...@techveda.org wrote:
> @@ -2294,17 +2294,20 @@ static int _rtl92e_ioctl(struct net_device *dev,
> struct ifreq *rq, int cmd)
>
> if (ipw->cmd == IEEE_CMD_SET_ENCRYPTION) {
> if (ipw->u.crypt.set_tx) {
> -
Hi Andrzej,
On 03/14/2017 08:05 PM, Andrzej Hajda wrote:
Hi Jeffy,
On 14.03.2017 11:45, Jeffy Chen wrote:
Currently we are adding all components from the dts, if one of their
drivers been disabled, we would not be able to bring up others.
Refactor component match logic, follow exynos drm.
Linus Lüssing wrote:
> When trying to redirect bridged frames to the bridge device itself
> via the ebtables nat-prerouting chain and the dnat target then this
> currently fails:
>
> The ethernet destination of the frame is dnat'ed to the MAC address of
> the bridge itself just fine and the
On Tue, 14 Mar 2017, Arnd Bergmann wrote:
> On Tue, Mar 14, 2017 at 12:14 PM, Lee Jones wrote:
> > On Tue, 28 Feb 2017, Arnd Bergmann wrote:
> >
> >> When the db8500 watchdog is enabled without the PRCMU, we get a lot of
> >> warnings about duplicate or missing helper functions:
> >>
> >> In
On Tue, Mar 7, 2017 at 7:52 PM, Florian Fainelli wrote:
> In case a platform only defaults a "default" set of pins, but not a
> "sleep" set of pins, and this particular platform suspends and resumes
> in a way that the pin states are not preserved by the hardware, when we
> resume, we would call
On Mon, Mar 13, 2017 at 8:06 PM, Andy Shevchenko
wrote:
> On Mon, Mar 13, 2017 at 8:59 PM, Florian Fainelli
> wrote:
>> On 03/07/2017 10:52 AM, Florian Fainelli wrote:
>
>> Linus am I hitting some of your spam folder, or you are really having
>> way too much fun with Gemini ;) ?
>
> A bit
Hi,
Any Update?
Thanks,
Sreekanth
On Mon, Mar 13, 2017 at 12:13 PM, Sreekanth Reddy
wrote:
> Hi,
>
> Our LSI(Broadcom) SAS3.5 HBA device's support virtual SES device.
>
> Whenever we load the mpt3sas driver then we are observing below error message,
>
> "Wrong diagnostic page; asked for 7 got
On Tue, 14 Feb 2017, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Add the Altera Arria10 DevKit sysfs attributes to the
> MFD device. Update copyright and email.
>
> Signed-off-by: Thor Thayer
> ---
> drivers/mfd/altera-a10sr.c | 98
>
If a console was specified by ACPI SPCR table _and_ command line parameters like
"console=ttyAMA0" _and_ "earlycon" were specified, then log messages
appear twice.
This issue was addressed in the patch [1] but the approach was wrong and
a revert [2] was suggested.
First two patches "printk: fix
The variable preferred_console is used only inside register_console()
and its semantics is boolean. It is negative when no console has been
made preferred.
Make it static bool and rename to has_preferred.
Renaming was suggested by Peter Hurley
Acked-by: Petr Mladek
Reviewed-by: Steven Rostedt
If a console was specified by ACPI SPCR table _and_ command line
parameters like "console=ttyAMA0" _and_ "earlycon" were specified,
then log messages appear twice.
The root cause is that the code traverses the list of specified
consoles (the `console_cmdline` array) and stops at the first match.
The variable selected_console is set in __add_preferred_console()
to point to the last console parameter that was added to the
console_cmdline array.
Rename it to preferred_console so that the name reflects the usage.
Petr Mladek:
"[..] the selected_console/preferred_console
value is used to
On Tue, 21 Feb 2017, Javier Martinez Canillas wrote:
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the assumption that a
> I2C device registered via OF will always match a legacy I2C device ID and
> that the
On Tue, 21 Feb 2017, Javier Martinez Canillas wrote:
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the assumption that a
> I2C device registered via OF will always match a legacy I2C device ID and
> that the
On Wed, Mar 15, 2017 at 04:18:11AM +0100, Linus Lüssing wrote:
> When trying to redirect bridged frames to the bridge device itself
> via the ebtables nat-prerouting chain and the dnat target then this
> currently fails:
>
> The ethernet destination of the frame is dnat'ed to the MAC address of
>
On Mon, 13 Mar 2017, Andy Shevchenko wrote:
> After commit 028af5941dd8 ("mfd: intel-lpss: Pass SDA hold time to I2C host
> controller driver")
> the driver still has a non-used variable.
>
> Remove it here.
>
> Cc: Mika Westerberg
> Cc: Rafael J. Wysocki
> Signed-off-by: Andy Shevchenko
>
Currently net/sunrpc/xprtmultipath.c is the only file outside of arch/
headers and asm-generic/ headers to include , apparently
for the use of cmpxchg_relaxed().
However, many architectures do not provide cmpxchg_relaxed() in their
, and it is necessary to include to get
this definition, as
On Fri, 10 Mar 2017, Quentin Schulz wrote:
> This adds support for the Allwinner A33 thermal sensor.
>
> Unlike the A10, A13 and A31, the Allwinner A33 only has one channel
> which is dedicated to the thermal sensor. Moreover, its thermal sensor
> does not generate interruptions, thus we only
Hi Vivek,
On Fri, 2017-03-10 at 20:10 +0530, Vivek Gautam wrote:
> Hi Philipp,
>
>
> On Wed, Feb 22, 2017 at 10:54 AM, Vivek Gautam
> wrote:
> > Count number of reset phandles available with the device node
> > to know the resets a given device has.
> >
> > Cc: Philipp Zabel
> >
On Wed, Mar 15, 2017 at 11:26:08AM +0100, Florian Westphal wrote:
> Linus Lüssing wrote:
> > When trying to redirect bridged frames to the bridge device itself
> > via the ebtables nat-prerouting chain and the dnat target then this
> > currently fails:
> >
> > The ethernet destination of the
It also needs any support from VBIOS side ? I mean PCIe large bar support?
Thanks,
Ayyappa.
On Wed, Mar 15, 2017 at 1:07 PM, Christian König
wrote:
> Carizzo is an APU and resizing BARs isn't needed nor supported there. The
> CPU can access the full stolen VRAM directly on that hardware.
>
> As
On 03/15/2017 08:53 AM, Wanpeng Li wrote:
> Ping, :)
> 2017-03-07 13:51 GMT+08:00 Wanpeng Li :
>> From: Wanpeng Li
>>
>> The following warning can be triggered by hot-unplugging the CPU
>> on which an active SCHED_DEADLINE task is running on:
>>
>> [ cut here ]
>>
On Wed, 2017-02-22 at 10:54 +0530, Vivek Gautam wrote:
> Add support to get a list of resets available for the device.
> These resets must be kept de-asserted until the device is
> in use.
>
> Cc: Felipe Balbi
> Signed-off-by: Vivek Gautam
> ---
>
> Based on torvald's master branch.
>
>
Hi,
Thanks for the patch. If the assumption will not be there than this
fix is needed. I tested it on BeagleBoneBlack and it does not effect
anything.
Tested-by: Crt Mori
Acked-by: Crt Mori
Best regards,
Crt
On 15 March 2017 at 05:44, Javier Martinez Canillas
wrote:
> The driver doesn't
1001 - 1100 of 1820 matches
Mail list logo
