On Mon, Nov 21, 2016 at 10:53:52AM -0600, Bjorn Helgaas wrote:
> On Wed, Nov 16, 2016 at 12:11:58PM -0600, Bjorn Helgaas wrote:
> > Hi Johannes,
> >
> > On Wed, Nov 02, 2016 at 04:35:52PM -0600, Johannes Thumshirn wrote:
> > > The Read Completion Boundary (RCB) bit must only be set on a device or
Hi Greg,
On Mon, Nov 21, 2016 at 03:46:08PM +0100, Greg KH wrote:
> > > > +
> > > > +config TYPEC
> > > > + tristate
> > >
> > > Hah, that says NOTHING about what this code is at all.
> >
> > Alone the class driver does nothing. Why would the user need to be
> > aware of if it when selecti
On 22.11.2016 03:29, atull wrote:
> On Mon, 21 Nov 2016, Moritz Fischer wrote:
>
>> Add myself as co-maintainer to fpga mgr framework.
>>
>> Signed-off-by: Moritz Fischer
>> Cc: Alan Tull
>> Cc: Greg Kroah-Hartman
>> Cc: linux-kernel@vger.kernel.org
>> Cc: linux-f...@vger.kernel.org
>> ---
>> H
On Tue, Nov 22, 2016 at 08:48:57AM +0100, Michal Simek wrote:
> On 22.11.2016 03:29, atull wrote:
> > On Mon, 21 Nov 2016, Moritz Fischer wrote:
> >
> >> Add myself as co-maintainer to fpga mgr framework.
> >>
> >> Signed-off-by: Moritz Fischer
> >> Cc: Alan Tull
> >> Cc: Greg Kroah-Hartman
> >
Virtio modern devices are always little edian, let's introduce
the LE functions for read/write configuration space for
virtio modern devices, which avoid complaint by Sparse when
we use the virtio_creaed/virtio_cwrite in VIRTIO_1 devices.
Signed-off-by: Gonglei
---
include/linux/virtio_config.h
This patch introduces virtio-crypto driver for Linux Kernel.
The virtio crypto device is a virtual cryptography device
as well as a kind of virtual hardware accelerator for
virtual machines. The encryption anddecryption requests
are placed in the data queue and are ultimately handled by
thebackend
The virtio crypto device is a virtual cryptography device
as well as a kind of virtual hardware accelerator for
virtual machines. The encryption anddecryption requests
are placed in the data queue and are ultimately handled by
thebackend crypto accelerators. The second queue is the
control queue us
Hi John,
Thank you for the patch.
On Monday 21 Nov 2016 16:37:30 John Stultz wrote:
> In chasing down issues with EDID probing, I found some
> duplicated but incomplete logic used to power the chip on and
> off.
>
> This patch refactors the adv7511_power_on/off functions, so
> they can be used f
On Wed, Nov 09, 2016 at 03:32:15PM +0900, Byungchul Park wrote:
> Currently rcu code forces CPU into scheduler when jiffies >=
> rcu_state.gp_start + jiffies_till_sched_qs, via resched_cpu().
>
> It would be better to force CPU into scheduler when jiffies >=
> rcu_state.jiffies_resched, too.
Hell
On Tue, Nov 22, 2016 at 12:14 AM, Laurent Pinchart
wrote:
> Hi John,
>
> Thank you for the patch.
>
> On Monday 21 Nov 2016 16:37:30 John Stultz wrote:
>> In chasing down issues with EDID probing, I found some
>> duplicated but incomplete logic used to power the chip on and
>> off.
>>
>> This patc
Hi Eric,
Today's linux-next merge of the userns tree got conflicts in:
arch/alpha/kernel/ptrace.c
arch/blackfin/kernel/ptrace.c
arch/cris/arch-v32/kernel/ptrace.c
arch/ia64/kernel/ptrace.c
arch/mips/kernel/ptrace32.c
arch/powerpc/kernel/ptrace32.c
include/linux/mm.h
kernel/ptrace.
On 11/22/2016 04:51 PM, Andrzej Hajda wrote:
> On 22.11.2016 02:24, Jaehoon Chung wrote:
>> On 11/22/2016 02:06 AM, Krzysztof Kozlowski wrote:
>>> On Mon, Nov 21, 2016 at 04:10:32PM +0900, Jaehoon Chung wrote:
Odroid-xu3/4 didn't need to use the cd-gpios for detecting card.
Because Host c
On Mon, Nov 21, 2016 at 12:44:45PM -0800, Andi Kleen wrote:
> > > http://halobates.de/tracepoint-trace
> >
> > There's a lot of push and pop regs due to function calling. There's
> > places that inlines can still improve things, and perhaps even some
> > likely unlikelys well placed.
>
> Assuming
On Tue, Nov 22, 2016 at 09:58:13AM +0200, Heikki Krogerus wrote:
> Hi Greg,
>
> On Mon, Nov 21, 2016 at 03:46:08PM +0100, Greg KH wrote:
> > > > > +
> > > > > +config TYPEC
> > > > > + tristate
> > > >
> > > > Hah, that says NOTHING about what this code is at all.
> > >
> > > Alone the class
Am 21.11.2016 22:53, schrieb Christophe JAILLET:
> In fs/cifs/smb2pdu.h, we have:
> #define SMB2_SHARE_TYPE_DISK0x01
> #define SMB2_SHARE_TYPE_PIPE0x02
> #define SMB2_SHARE_TYPE_PRINT 0x03
>
> Knowing that, with the current code, the SMB2_SHARE_TYPE_PRINT case can
> never trigger and p
Hello,
On Mon, 21 Nov 2016 17:28:39 -0800, Florian Fainelli wrote:
> +Thomas, Gregory,
>
> On 11/21/2016 05:22 PM, Stephen Rothwell wrote:
> [snip]
> >
> > Introduced by commit
> >
> > a0627f776a45 ("net: marvell: Allow drivers to be built with COMPILE_TEST")
> >
> > "a few warnings" is a ma
On 22 November 2016 at 00:04, 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
Hi John,
Thank you for the patch.
On Monday 21 Nov 2016 16:37:31 John Stultz wrote:
> Secton 4.1 of the adv7511 programming guide advises one waits
> 200ms after powering on the chip before trying to communicate
> with it via i2c. Not doing so can cause reliability issues when
> probing the EDID.
Hi John,
On Tuesday 22 Nov 2016 00:16:55 John Stultz wrote:
> On Tue, Nov 22, 2016 at 12:14 AM, Laurent Pinchart wrote:
> > On Monday 21 Nov 2016 16:37:30 John Stultz wrote:
> >> In chasing down issues with EDID probing, I found some
> >> duplicated but incomplete logic used to power the chip on a
On 22.11.2016 09:07, Greg Kroah-Hartman wrote:
> On Tue, Nov 22, 2016 at 08:48:57AM +0100, Michal Simek wrote:
>> On 22.11.2016 03:29, atull wrote:
>>> On Mon, 21 Nov 2016, Moritz Fischer wrote:
>>>
Add myself as co-maintainer to fpga mgr framework.
Signed-off-by: Moritz Fischer
>>>
Hi John,
Thank you for the patch.
On Monday 21 Nov 2016 16:37:32 John Stultz wrote:
> From: Archit Taneja
>
> On some adv7511 implementations, we can get some spurious
> disconnect signals which can cause monitor probing to fail.
>
> This patch enables HPD (hot plug detect) interrupt support
>
On Tuesday 22 November 2016 02:07 AM, Jon Hunter wrote:
On 21/11/16 12:49, Laxman Dewangan wrote:
On Monday 21 November 2016 04:38 PM, Jon Hunter wrote:
I had a discussion with the ASIC on this and as per them
1.8 V nominal is (1.62V, 1.98V)
3.3 V nominal is (2.97V,3.63V)
I am wor
On Tuesday 22 November 2016 02:31 AM, Jon Hunter wrote:
On 09/11/16 13:06, Laxman Dewangan wrote:
+ _entry_(32, "uart", UART, true, "vddio-uart"), \
+ _entry_(33, "usb0", USB0, true, NULL),\
+ _entry_(34, "usb1", USB1, true, NULL),
On 22 November 2016 at 00:04, Zach Brown wrote:
> On some boards, max SDIO frequency is limited by trace lengths and other
> layout
> choices. We would like a way to specify this limitation so the driver can
> behave accordingly.
>
> This patch set assumes that the limitation has been reported in
* Linus Torvalds wrote:
> On Sun, Nov 20, 2016 at 11:13 PM, Ingo Molnar wrote:
> >
> > So I have applied your fix that addresses the worst fallout directly:
> >
> > fc0e81b2bea0 x86/traps: Ignore high word of regs->cs in
> > early_fixup_exception()
> >
> > ... but otherwise we might be bette
perf report (with TUI) exits with error when it finds a sample of zero
length symbol(i.e. addr == sym->start == sym->end). Actually these are
valid samples. Don't exit TUI and show report with such symbols.
Link: https://lkml.org/lkml/2016/10/8/189
Reported-by: Anton Blanchard
Signed-off-by: Rav
On Tue, Nov 22, 2016 at 1:19 AM, Stephen Rothwell wrote:
> Hi Miklos,
>
> After merging the overlayfs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> In file included from fs/overlayfs/dir.c:20:0:
> fs/overlayfs/dir.c: In function 'ovl_set_redirect':
> fs/over
Hi all,
Today's linux-next merge of the clk tree got conflicts in:
arch/arm/boot/dts/r8a7779.dtsi
arch/arm/boot/dts/r8a7790.dtsi
arch/arm/boot/dts/r8a7791.dtsi
arch/arm/boot/dts/r8a7792.dtsi
arch/arm/boot/dts/r8a7793.dtsi
arch/arm/boot/dts/r8a7794.dtsi
arch/arm/mach-shmobile/setup-r
From: Tang Yuantian
Signed-off-by: Tang Yuantian
---
v2:
- remove commit message as it is duplicated to title
drivers/clk/clk-qoriq.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/clk/clk-qoriq.c b/drivers/clk/clk-qoriq.c
index 1bece0f..65c21d7 100644
--- a
On Tue, Nov 22, 2016 at 08:54:18AM +0100, Martin Kaiser wrote:
> The HM and TM fields in the LCDC DMA Control Register are 7 bits wide.
> Use the correct mask to allow setting all possible bits.
>
> Signed-off-by: Martin Kaiser
> ---
>
> This bug was discovered on a board that uses DMACR_TM(16).
On Mon, Nov 21, 2016 at 04:47:59PM -0500, Mark Hounschell wrote:
> OK, I did get this message before the reported BUG message.
>
> gpiohsd gpiohsd: DMA-API: device driver tries to free DMA memory it has not
> allocated [device address=0xffee8000] [size=8192 bytes]
>
> But I've verified t
On Wed, Nov 16, 2016 at 4:20 PM, Arnd Bergmann wrote:
> This function clearly never worked and always returns true,
> as pointed out by gcc-7:
>
> arch/arm/mach-ux500/pm.c: In function 'prcmu_is_cpu_in_wfi':
> arch/arm/mach-ux500/pm.c:137:212: error: ?: using integer constants in
> boolean conte
* Dave Jiang wrote:
> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
> However it does not take into account the memmap= parameter passed in from
> the kernel commandline.
memmap= parameters are often used as a list.
> [...] This results in the kernel sometimes being put
Hi Anton,
On Tuesday 22 November 2016 02:10 PM, Ravi Bangoria wrote:
> perf report (with TUI) exits with error when it finds a sample of zero
> length symbol(i.e. addr == sym->start == sym->end). Actually these are
> valid samples. Don't exit TUI and show report with such symbols.
>
> Link: https:
On Mon, Nov 21, 2016 at 07:33:45AM -0800, Guenter Roeck wrote:
> On 11/21/2016 06:23 AM, Heikki Krogerus wrote:
> > On Mon, Nov 21, 2016 at 03:11:03PM +0200, Heikki Krogerus wrote:
> > > Hi Greg,
> > >
> > > On Mon, Nov 21, 2016 at 11:35:28AM +0100, Greg KH wrote:
> > > > > +static void typec_part
On Tuesday 22 November 2016 02:19 PM, Ravi Bangoria wrote:
> Hi Anton,
>
> On Tuesday 22 November 2016 02:10 PM, Ravi Bangoria wrote:
>> perf report (with TUI) exits with error when it finds a sample of zero
>> length symbol(i.e. addr == sym->start == sym->end). Actually these are
>> valid sample
Hi all,
After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
Inconsistent kallsyms data
Try make KALLSYMS_EXTRA_PASS=1 as a workaround
Which is a vast improvement. I'll try adding 'KALLSYMS_EXTRA_PASS=1'
later and see how it goes. It would be nice n
On Fri, Nov 18, 2016 at 3:12 PM, Geliang Tang wrote:
> Use builtin_platform_driver() helper to simplify the code.
>
> Signed-off-by: Geliang Tang
Patch applied.
Yours,
Linus Walleij
On Tuesday, November 22, 2016 9:47:20 AM CET Linus Walleij wrote:
> On Wed, Nov 16, 2016 at 4:20 PM, Arnd Bergmann wrote:
>
> > This function clearly never worked and always returns true,
> > as pointed out by gcc-7:
> >
> > arch/arm/mach-ux500/pm.c: In function 'prcmu_is_cpu_in_wfi':
> > arch/ar
On Monday 21 November 2016 09:47 PM, Rob Herring wrote:
On Fri, Nov 18, 2016 at 08:05:55PM +0530, Laxman Dewangan wrote:
Some PWM regulator has the exponential transition in voltage change as
opposite to fixed slew-rate linear transition on other regulators.
For such PWM regulators, add the pro
On Mon, 21 Nov 2016, Pandruvada, Srinivas wrote:
> Your change below fixes the crash issue. Now I tested a case where the
> last cpu offlined from a package, it removed thermal zone and added
> zone back once any cpu from the package onlined. So this is working.
>
> I want to try to run some workl
On 11/18/2016 09:43 PM, Jarkko Sakkinen wrote:
On Fri, Nov 18, 2016 at 05:42:01PM +0530, Nayna wrote:
On 11/17/2016 11:12 PM, Jarkko Sakkinen wrote:
On Thu, Nov 17, 2016 at 05:20:36PM +0530, Nayna wrote:
I tested this for capability TPM2_CAP_PCRS. It seems TPM2_CAP_PCRS
capability always
Hi,
On Tuesday 22 November 2016 01:17 PM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Thu, Nov 10, 2016 at 2:33 PM, Vivek Gautam
> wrote:
>> Hi Kishon,
>>
>
+unsigned int msm8996_pciephy_tx_offsets[] = { 0x1000, 0x2000, 0x3000 };
+unsigned int msm8996_pciephy_rx_offsets[] = { 0x1200, 0
> -Original Message-
> From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com]
> Sent: 2016年11月21日 22:03
> To: Wenyou Yang - A41535
> Cc: Nicolas Ferre ; Russell King
> ; Rob Herring ; Pawel Moll
> ; Mark Rutland ; Ian Campbell
> ; Kumar Gala ; linux-
> ker...@vger.kernel.o
On Fri, Nov 18, 2016 at 3:12 PM, Geliang Tang wrote:
> Use builtin_platform_driver() helper to simplify the code.
>
> Signed-off-by: Geliang Tang
Patch applied.
Yours,
Linus Walleij
On Fri, Nov 18, 2016 at 3:12 PM, Geliang Tang wrote:
> Use builtin_platform_driver() helper to simplify the code.
>
> Signed-off-by: Geliang Tang
Patch applied.
Yours,
Linus Walleij
On Fri, Nov 18, 2016 at 3:12 PM, Geliang Tang wrote:
> Use builtin_platform_driver() helper to simplify the code.
>
> Signed-off-by: Geliang Tang
Patch applied with Hongzhou's ACK.
Yours,
Linus Walleij
Currently, in xmon, there is no obvious way to get an address for a
percpu symbol for a particular cpu. Having such an ability would be good
for debugging the system when percpu variables got involved.
Therefore, this patch introduces a new xmon command "lp" to lookup the
address for percpu symbol
On Saturday, November 19, 2016 12:39 AM, Rob Herring wrote:
> On Fri, Nov 18, 2016 at 09:35:46AM +0900, Eric Jeong wrote:
> >
> > From: Eric Jeong
> >
> > The change is to move pv88080 binding document from the regulator
> > directory to mfd binding directory for PV88080 PMIC MFD support.
> > And
The generic MSI layer doesn't have any PCI ties anymore, and the
build hack should have been removed some time ago.
Fixes: d9109698be6e ("genirq: Introduce msi_domain_alloc/free_irqs()")
Signed-off-by: Marc Zyngier
---
kernel/irq/msi.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
di
Hi,
I've got the following error report while fuzzing the kernel with syzkaller.
A reproducer is attached.
You may need to run it a few times.
On commit 9c763584b7c8911106bb77af7e648bef09af9d80 (4.9-rc6, Nov 20).
==
BUG: KASAN: use
Hi Guillaume,
Sorry, I was on vacation last week, couldn't reply.
As I can see a fix was already sent upstream.
Thanks!
On Thu, Nov 10, 2016 at 6:44 PM, Guillaume Nault wrote:
> On Mon, Nov 07, 2016 at 11:35:26PM +0100, Andrey Konovalov wrote:
>> Hi,
>>
>> I've got the following error report w
Xmon data-breakpoint feature is broken.
Whenever there is a watchpoint match occurs, hw_breakpoint_handler will
be called by do_break via notifier chains mechanism. If watchpoint is
registered by xmon, hw_breakpoint_handler won't find any associated
perf_event and returns immediately with NOTIFY_S
On 21 November 2016 at 15:37, Juri Lelli wrote:
> On 21/11/16 15:17, Peter Zijlstra wrote:
>> On Mon, Nov 21, 2016 at 01:53:08PM +, Juri Lelli wrote:
>> > On 21/11/16 13:26, Peter Zijlstra wrote:
>>
>> > > So the limited decay would be the dominant factor in ramp-up time,
>> > > leaving the re
On Monday 21 November 2016 10:29 PM, Axel Haslam wrote:
> This adds the DT node for the ohci controller and
> enables it for the omapl138-lckd platform.
>
> DEPENDENCIES:
>
> 1. [PATCH v6 0/5] USB: ohci-da8xx: Add device tree support
> https://lkml.org/lkml/2016/11/21/558
Looks like atleast this
Hi Stephen,
On Tue, Nov 22, 2016 at 9:41 AM, Stephen Rothwell wrote:
> Today's linux-next merge of the clk tree got conflicts in:
>
> arch/arm/boot/dts/r8a7779.dtsi
> arch/arm/boot/dts/r8a7790.dtsi
> arch/arm/boot/dts/r8a7791.dtsi
> arch/arm/boot/dts/r8a7792.dtsi
> arch/arm/boot/dts/r8a
Hi Zach,
Please do not resend a patch series so quickly (a simple ping is
enough).
BTW, I already asked Richard and Brian to have a look, let's wait a bit.
On Mon, 21 Nov 2016 13:51:34 -0600
Zach Brown wrote:
> For ONFI-compliant NAND devices, the ONFI parameters report the maximum number
> of
On Tue, Nov 22, 2016 at 10:33 AM, Sekhar Nori wrote:
> On Monday 21 November 2016 10:29 PM, Axel Haslam wrote:
>> This adds the DT node for the ohci controller and
>> enables it for the omapl138-lckd platform.
>>
>> DEPENDENCIES:
>>
>> 1. [PATCH v6 0/5] USB: ohci-da8xx: Add device tree support
>>
It has been determined that the highest resolution supported correctly
by LCDC rev1 is 800x600 on da850 due to memory bandwidth constraints.
Set the max_width property in da850.dtsi to 800.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/boot/dts/da850.dtsi | 1 +
1 file changed, 1 insertion(+)
Hi Thomas, Ingo,
This pull request contains a few changes.
- Unmap the region obtained by of_iomap in case of error in the init path for
the bcm2835 timer (Arvind Yadav).
- Add a boolean property in the DT for the arch_arm_timer in order to tell the
driver the hardware implementation has
>
> On Wed, Nov 16, 2016 at 07:03:38PM +0200, Tomas Winkler wrote:
> > Functions tpm_transmit and transmit_cmd are referenced from other
> > functions kdoc hence deserve documentation.
> >
> > Signed-off-by: Tomas Winkler
>
> Do you know how to make "make htmldocs" to generate documentation for
From: Brian Norris
The ARM specifies that the system counter "must be implemented in an
always-on power domain," and so we try to use the counter as a source of
timekeeping across suspend/resume. Unfortunately, some SoCs (e.g.,
Rockchip's RK3399) do not keep the counter ticking properly when
swit
From: Brian Norris
The "arm,no-tick-in-suspend" property was introduced to note
implementations where the system counter does not quite follow the ARM
specification that it "must be implemented in an always-on power
domain".
Particularly, RK3399's counter stops ticking when we switch from the
24
From: Stephen Boyd
Let's use the of_io_request_and_map() API so that the frame
region is protected and shows up in /proc/iomem.
Signed-off-by: Stephen Boyd
Signed-off-by: Daniel Lezcano
Acked-by: Marc Zyngier
---
drivers/clocksource/arm_arch_timer.c | 5 +++--
1 file changed, 3 insertions(+)
From: Arvind Yadav
Free memory mapping, if bcm2835_timer_init is not successful.
Signed-off-by: Arvind Yadav
Reviewed-by: Eric Anholt
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/bcm2835_timer.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/driv
On Tue, 2016-11-22 at 13:45 +0530, Laxman Dewangan wrote:
> On Tuesday 22 November 2016 02:31 AM, Jon Hunter wrote:
> > On 09/11/16 13:06, Laxman Dewangan wrote:
> > + _entry_(32, "uart", UART, true, "vddio-uart"), \
> > + _entry_(33, "usb0", USB0, true, NULL), \
> > +
On 11/22/2016 12:42 AM, Kevin Hilman wrote:
> Neil,
>
> Neil Armstrong writes:
>
>> Following the Amlogic Linux kernel, it seem the only differences
>> between the GXL and GXM SoCs are the CPU Clusters.
>>
>> This commit renames the gxl-s905d-p23x DTSI in a common file for
>> S905D p20x and S912
On Tuesday 22 November 2016 03:15 PM, Joe Perches wrote:
On Tue, 2016-11-22 at 13:45 +0530, Laxman Dewangan wrote:
On Tuesday 22 November 2016 02:31 AM, Jon Hunter wrote:
On 09/11/16 13:06, Laxman Dewangan wrote:
+ _entry_(32, "uart", UART, true, "vddio-uart"), \
+ _en
The DT binding for tildc is not consistent with the driver code - the
option in the binding is called 'max-width' while the code expects
'ti,max-width'.
Make the driver code consistent with the binding.
Signed-off-by: Bartosz Golaszewski
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 2 +-
1 file ch
* Daniel Lezcano wrote:
> Hi Thomas, Ingo,
>
> This pull request contains a few changes.
>
> - Unmap the region obtained by of_iomap in case of error in the init path for
>the bcm2835 timer (Arvind Yadav).
>
> - Add a boolean property in the DT for the arch_arm_timer in order to tell
>
Hi Scott,
> -Original Message-
> From: Scott Wood [mailto:o...@buserror.net]
> Sent: Wednesday, November 16, 2016 2:54 PM
> To: Y.T. Tang ; mturque...@baylibre.com
> Cc: sb...@codeaurora.org; linux-kernel@vger.kernel.org; Scott Wood
> ; linux-...@vger.kernel.org; linux-arm-
> ker...@lists.
Hi!
On 22.11.2016 10:37, Boris Brezillon wrote:
> Hi Zach,
>
> Please do not resend a patch series so quickly (a simple ping is
> enough).
> BTW, I already asked Richard and Brian to have a look, let's wait a bit.
It is on my TODO. Since I'm travelling I'm slow with reviewing.
Thanks,
//richard
On Monday 21 November 2016 09:45 PM, Axel Haslam wrote:
> The card detect gpio on the hawk board is gpio4_0 and not gpio3_12
>
> Signed-off-by: Axel Haslam
The LCDK and HawkBoard are different boards. The HawkBoard schematic
from eLinux.org page is broken, but looking for it on the net, I found
On Monday 21 November 2016 09:45 PM, Axel Haslam wrote:
> The hawk board does not have a write protect pin to read the card
> write protect status.
>
> So remove un-needed platform data declaration for this gpio.
>
> Signed-off-by: Axel Haslam
The schematic I found has the SD_WP pin connected t
Changes:
* add myself as maintainer, so patches land in my inbox.
* add qemu-devel mailing list.
* add drm-qemu git repo.
* flip bochs and qxl status to "Maintained".
Signed-off-by: Gerd Hoffmann
---
MAINTAINERS | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --gi
I recently encountered wreckage because access_ok() was used where it
should not be, add an explicit WARN when access_ok() is used wrongly.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/uaccess.h | 7 +--
include/linux/preempt.h| 21 +
2 files c
On Tue, Nov 22, 2016 at 10:51:31AM +0100, Ingo Molnar wrote:
>
> * Daniel Lezcano wrote:
>
> > Hi Thomas, Ingo,
> >
> > This pull request contains a few changes.
> >
> > - Unmap the region obtained by of_iomap in case of error in the init path
> > for
> >the bcm2835 timer (Arvind Yadav).
Also update Kconfig help text, explaining things:
Cirrus is obsolete, the hardware was designed in the 90ies
and can't keep up with todays needs. More background:
https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
Better alternatives are:
- stdvga (DRM_BOCHS, qemu -vga s
The new Amlogic GXM SoC (S912) is part of the Meson GX family and is nearly
identical to GXM but with a second Quad-A53 core cluster.
The GXM dtsi includes the GXL dtsi and the p20x dtsi is refactored in a
common p20x/q20x to support the GXM Q200 and Q201 board that uses the exact
same board layou
On Tue, Nov 22, 2016 at 12:29:46AM -0500, Len Brown wrote:
> +On a platform tasked with running multiple versions of Windows,
> +the BIOS could use _OS to enable/disable devices that and OS
^
Following the Amlogic Linux kernel, it seem the only differences
between the GXL and GXM SoCs are the CPU Clusters.
This commit renames the gxl-s905d-p23x DTSI in a common file for
S905D p23x and S912 q20x boards.
Then adds a meson-gxm dtsi and reproduce the P23x to Q20x boards
dts files since th
Add support for the Nexbox A1 board based on the Amlogic S912 SoC.
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/arm/amlogic.txt | 1 +
arch/arm64/boot/dts/amlogic/Makefile | 1 +
.../arm64/boot/dts/amlogic/meson-gxm-nexbox-a1.dts | 169 ++
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
ipc/sem.c: In function 'freeary':
ipc/sem.c:1125:2: error: implicit declaration of function 'WAKE_Q'
[-Werror=implicit-function-declaration]
WAKE_Q(wake_q);
^
ipc/sem.c:1125:9:
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/vfio/vfio_iommu_type1.c: In function 'vaddr_get_pfn':
drivers/vfio/vfio_iommu_type1.c:364:9: error: too few arguments to function
'get_user_pages_remote'
ret = get_user_pag
Commit-ID: 4e201566402c878a225d4425df8a4a664c6f251e
Gitweb: http://git.kernel.org/tip/4e201566402c878a225d4425df8a4a664c6f251e
Author: Marc Zyngier
AuthorDate: Tue, 22 Nov 2016 09:21:16 +
Committer: Thomas Gleixner
CommitDate: Tue, 22 Nov 2016 11:00:19 +0100
genirq/msi: Drop artifi
On 17 November 2016 at 17:59, Bjorn Helgaas wrote:
> Add a writeup about how PCI host bridges should be described in ACPI
> using PNP0A03/PNP0A08 devices, PNP0C02 devices, and the MCFG table.
>
> Signed-off-by: Bjorn Helgaas
> ---
> Documentation/PCI/00-INDEX |2 +
> Documentation/PCI/a
On Tue, Nov 22, 2016 at 10:53 AM, Sekhar Nori wrote:
> On Monday 21 November 2016 09:45 PM, Axel Haslam wrote:
>> The card detect gpio on the hawk board is gpio4_0 and not gpio3_12
>>
>> Signed-off-by: Axel Haslam
>
> The LCDK and HawkBoard are different boards. The HawkBoard schematic
> from eLi
On Thu, Nov 10, 2016 at 02:36:33PM -0800, Tim Chen wrote:
> +/*
> + * Return the lowest numbered (or highest priority) cpu
> + * in the intersection of two cpu masks. If no cpu is
> + * is in both masks, nr_cpu_ids will be returned.
> + */
> +int __weak arch_asym_max_cpu_and(const struct cpumask *
On Mon, 2016-11-21 at 21:35 -0800, Florian Fainelli wrote:
> Le 21/11/2016 à 08:47, Andrew Lunn a écrit :
> >
> > >
> > > What I did not realize when doing this patch for the realtek
> > > driver is
> > > that there is already 6 valid modes defined in the kernel
> > >
> > > #define MDIO_EEE_100T
On Tue, Nov 22, 2016 at 09:44:20AM +, Winkler, Tomas wrote:
> >
> > On Wed, Nov 16, 2016 at 07:03:38PM +0200, Tomas Winkler wrote:
> > > Functions tpm_transmit and transmit_cmd are referenced from other
> > > functions kdoc hence deserve documentation.
> > >
> > > Signed-off-by: Tomas Winkler
On Tue, Nov 22, 2016 at 12:31:39AM +, David Howells wrote:
> Provide the ability to perform mixed-mode runtime service calls for x86 in
> the same way that commit 0a637ee61247bd4bed9b2a07568ef7a1cfc76187 provides
Small nit, checkpatch usually complains that this should be written as
12-charact
Hi all,
Le 21/11/2016 à 11:51, Lee Jones a écrit :
> On Sat, 19 Nov 2016, Boris Brezillon wrote:
>
>> On Sat, 19 Nov 2016 09:35:46 +0200
>> Mika Westerberg wrote:
>>
>>> On Fri, Nov 18, 2016 at 07:04:26PM +, Lee Jones wrote:
On Mon, 14 Nov 2016, Mika Westerberg wrote:
> This
Hi all,
On Tue, 22 Nov 2016 19:58:32 +1100 Stephen Rothwell
wrote:
>
> After merging the powerpc tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> Inconsistent kallsyms data
> Try make KALLSYMS_EXTRA_PASS=1 as a workaround
>
> Which is a vast improvement. I'll try
This is the ARM64 CRC T10 DIF transform accelerated with the ARMv8
NEON instruction.The config CRYPTO_CRCT10DIF_NEON should be turned
on to enable the feature.The crc_t10dif crypto library function will
use this faster algorithm when crct10dif_neon module is loaded.
Tcrypt benchmark results:
HIP0
All users are DT-only and it makes no sense to keep
unused code which also prevents further cleanups.
Signed-off-by: Nicolae Rosia
---
Changes in v2:
Increased audience in CC list
drivers/mfd/Kconfig| 1 +
drivers/mfd/twl-core.c | 395 ++---
2 f
On Tuesday 22 November 2016 03:40 PM, Axel Haslam wrote:
> On Tue, Nov 22, 2016 at 10:53 AM, Sekhar Nori wrote:
>> On Monday 21 November 2016 09:45 PM, Axel Haslam wrote:
>>> The card detect gpio on the hawk board is gpio4_0 and not gpio3_12
>>>
>>> Signed-off-by: Axel Haslam
>>
>> The LCDK and H
Hi,
I've got the following error report while fuzzing the kernel with syzkaller.
It seems that skb_dst(skb) may end up being NULL.
As far as I can see the bug was introduced in commit 5d41ce29e ("net:
icmp6_send should use dst dev to determine L3 domain").
ICMP v4 probaly has similar issue due t
On Monday 21 November 2016 09:45 PM, Axel Haslam wrote:
> Currently the mmc driver is polling the gpio to know if the
> card was removed.
>
> By using a gpio descriptor instead of the platform callbacks, the
> driver will be able to register the gpio with the mmc core with API's
> designed for thi
On 22/11/16 11:42, Bartosz Golaszewski wrote:
> It has been determined that the highest resolution supported correctly
> by LCDC rev1 is 800x600 on da850 due to memory bandwidth constraints.
>
> Set the max_width property in da850.dtsi to 800.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> arch
2016-11-22 11:27 GMT+01:00 Tomi Valkeinen :
> On 22/11/16 11:42, Bartosz Golaszewski wrote:
>> It has been determined that the highest resolution supported correctly
>> by LCDC rev1 is 800x600 on da850 due to memory bandwidth constraints.
>>
>> Set the max_width property in da850.dtsi to 800.
>>
>>
1 - 100 of 916 matches
Mail list logo
