On Mon, Mar 25, 2019 at 05:53:50PM -0500, Scott Wood wrote:
> On Mon, 2019-03-25 at 11:07 +0800, Wu Hao wrote:
> > @@ -200,21 +228,32 @@ static int fme_mgr_write(struct fpga_manager *mgr,
> > pr_credit = FIELD_GET(FME_PR_STS_PR_CREDIT,
> > pr_status);
> > }
> >
>
SNVS IRQ is requested before necessary driver data initialized,
if there is a pending IRQ during driver probe phase, kernel
NULL pointer panic will occur in IRQ handler. To avoid such
scenario, just initialize necessary driver data before enabling
IRQ. This patch is inspired by NXP's internal
With calling dev_pm_set_wake_irq() to set SNVS ON/OFF button
as wakeup source for suspend, generic wake irq mechanism
will automatically enable it as wakeup source when suspend,
then the enable_irq_wake()/disable_irq_wake() can be removed
in suspend/resume callback, it simplifies the code.
On Wed, 2019-03-27 at 12:37 +0800, Wu Hao wrote:
> On Tue, Mar 26, 2019 at 04:22:34PM -0500, Scott Wood wrote:
> > On Tue, 2019-03-26 at 14:33 -0500, Alan Tull wrote:
> > > On Mon, Mar 25, 2019 at 5:58 PM Scott Wood wrote:
> > > > >
> > > Hi Scott,
> > >
> > > > On Mon, 2019-03-25 at 17:53
With calling dev_pm_set_wake_irq() to set SNVS RTC as wakeup
source for suspend, generic wake irq mechanism will automatically
enable it as wakeup source when suspend, then the suspend/resume
callback which are ONLY for enabling/disabling irq wake can be
removed, it simplifies the code.
On Wed, Mar 27, 2019 at 01:10:31AM -0500, Scott Wood wrote:
> On Wed, 2019-03-27 at 12:37 +0800, Wu Hao wrote:
> > On Tue, Mar 26, 2019 at 04:22:34PM -0500, Scott Wood wrote:
> > > On Tue, 2019-03-26 at 14:33 -0500, Alan Tull wrote:
> > > > On Mon, Mar 25, 2019 at 5:58 PM Scott Wood wrote:
> > >
On Wed, 2019-03-27 at 13:10 +0800, Wu Hao wrote:
> On Mon, Mar 25, 2019 at 05:58:36PM -0500, Scott Wood wrote:
> > On Mon, 2019-03-25 at 17:53 -0500, Scott Wood wrote:
> > > On Mon, 2019-03-25 at 11:07 +0800, Wu Hao wrote:
> > > > In early partial reconfiguration private feature, it only
> > > >
From: Yongqiang Niu
Here is two modifition in this patch:
1.bls->dpi0 and rdma1->dsi are differen usecase,
Split DISP_REG_CONFIG_DSI_SEL setting into anther usecase
2.remove DISP_REG_CONFIG_DPI_SEL setting, DPI_SEL_IN_BLS is 0 and
this is same with hardware defautl setting,
Signed-off-by:
From: Yongqiang Niu
This patch add commponent OVL0_2L
Signed-off-by: Yongqiang Niu
---
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 2 ++
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 2 ++
2 files changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c
Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb"
clock to determine if it needs to configure the IP block as operating
at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both
clocks as IMX6SX_CLK_SDMA result in driver incorrectly thinking that
ratio is 1:1 which
Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb"
clock to determine if it needs to configure the IP block as operating
at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both
clocks as IMX7D_CLK_SDMA result in driver incorrectly thinking that
ratio is 1:1 which
Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb"
clock to determine if it needs to configure the IP block as operating
at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both
clocks as IMX6QDL_CLK_SDMA result in driver incorrectly thinking that
ratio is 1:1 which
On Tue, Mar 26, 2019 at 11:55:07PM +0530, Anirudh Rayabharam wrote:
> Shorten the expression by re-using the part that was already computed to
This confused me. Better to phrase it like:
Shorten the expression by using the "psecuritypriv" pointer.
> fix the line over 80 characters warning
i.MX7D comes with 4 viewports, so configure PCIE node accordingly so
that the driver won't assume we only have 2.
Signed-off-by: Andrey Smirnov
Cc: Richard Zhu
Cc: Chris Healy
Cc: Lucas Stach
Cc: Fabio Estevam
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
i.MX6 comes with 4 viewports, so configure PCIE node accordingly so
that the driver won't assume we only have 2.
Signed-off-by: Andrey Smirnov
Cc: Richard Zhu
Cc: Chris Healy
Cc: Lucas Stach
Cc: Fabio Estevam
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
Add support for ZII's i.MX7 based Remote Peripheral Unit 2 (RPU2)
board.
Signed-off-by: Andrey Smirnov
Cc: Shawn Guo
Cc: Chris Healy
Cc: Andrew Lunn
Cc: Fabio Estevam
Cc: Rob Herring
Cc: linux-kernel@vger.kernel.org
Cc: devicet...@vger.kernel.org
---
arch/arm/boot/dts/Makefile |
Add support for ZII i.MX7 RPU2 board.
Signed-off-by: Andrey Smirnov
Cc: Shawn Guo
Cc: Chris Healy
Cc: Andrew Lunn
Cc: Fabio Estevam
Cc: Rob Herring
Cc: linux-kernel@vger.kernel.org
Cc: devicet...@vger.kernel.org
---
Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
1 file changed, 1
On Wed, Mar 27, 2019 at 01:58:45PM +0900, William Breathitt Gray wrote:
> This macro iterates for each 8-bit group of bits (clump) with set bits,
> within a bitmap memory region. For each iteration, "start" is set to the
> bit offset of the found clump, while the respective clump value is
> stored
Fix error bit operation in watchdog_start()
Fixes: 14b24a88a3660 ("watchdog: f71808e_wdt: Add F81866 support")
Signed-off-by: Ji-Ze Hong (Peter Hong)
---
drivers/watchdog/f71808e_wdt.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
Separate declaration and assignment in watchdog_start()
Signed-off-by: Ji-Ze Hong (Peter Hong)
---
drivers/watchdog/f71808e_wdt.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/watchdog/f71808e_wdt.c b/drivers/watchdog/f71808e_wdt.c
index
On Tue, 2019-03-26 at 23:23 +, Kirill Smelkov wrote:
> Using scripts/coccinelle/api/stream_open.cocci added in the previous
> patch, search and convert to stream_open all in-kernel nonseekable_open
> users for which read and write actually do not depend on ppos and where
> there is no other
You might be hitting a bug I found.
Try applying this patch:
https://marc.info/?l=linux-kernel=155355953012985=2
Unfortunately it did not change anything.
--
Meelis Roos
On 2019/3/26 下午4:13, Dan Carpenter wrote:
> I'm not the right person to send this to...
>
> $ ./scripts/get_maintainer.pl -f arch/arm64/Kconfig.platforms
> Catalin Marinas (maintainer:ARM64 PORT (AARCH64
> ARCHITECTURE))
> Will Deacon (maintainer:ARM64 PORT (AARCH64
> ARCHITECTURE))
>
On Wed, Mar 27, 2019 at 5:53 AM syzbot
wrote:
>
> syzbot has bisected this bug to:
>
> commit e950564b97fd0f541b02eb207685d0746f5ecf29
> Author: Miklos Szeredi
> Date: Tue Jul 24 13:01:55 2018 +
>
> vfs: don't evict uninitialized inode
>
> bisection log:
On 3/27/2019 5:23 AM, Huang Zijiang wrote:
The of_find_device_by_node() takes a reference to the underlying device
structure, we should release that reference.
Signed-off-by: Huang Zijiang
---
arch/arm/mach-socfpga/pm.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
On Wed, Mar 27, 2019 at 01:19:29AM -0500, Scott Wood wrote:
> On Wed, 2019-03-27 at 13:10 +0800, Wu Hao wrote:
> > On Mon, Mar 25, 2019 at 05:58:36PM -0500, Scott Wood wrote:
> > > On Mon, 2019-03-25 at 17:53 -0500, Scott Wood wrote:
> > > > On Mon, 2019-03-25 at 11:07 +0800, Wu Hao wrote:
> > > >
Hi
Here are a couple for fixes.
Adrian Hunter (2):
perf scripts python: exported-sql-viewer.py: Fix never-ending loop
perf scripts python: exported-sql-viewer.py: Fix python3 support
tools/perf/scripts/python/exported-sql-viewer.py | 77 +++-
1 file changed, 63
pyside version 1 fails to handle python3 large integers in some cases,
resulting in Qt getting into a never-ending loop. This affects:
samples Table
samples_view Table
All branches Report
Selected branches Report
Add workarounds for those cases.
Signed-off-by:
Unlike python2, python3 strings are not compatible with byte strings. That
results in disassembly not working for the branches reports. Fixup those
places overlooked in the port to python3.
Signed-off-by: Adrian Hunter
Fixes: beda0e725e5f ("perf script python: Add Python3 support to
Hi,
On 25/03/19 14:15, luca abeni wrote:
> syzbot reported the following warning:
> [ 948.126369] WARNING: CPU: 4 PID: 17089 at kernel/sched/deadline.c:255
> task_non_contending+0xae0/0x1950
> [ 948.130198] Kernel panic - not syncing: panic_on_warn set ...
> [ 948.130198]
> [ 948.134221]
On Wed, Mar 27, 2019 at 3:49 AM Ronald Tschalär wrote:
>
> This introduces print_hex_dump_to_cb() which contains all the hexdump
> formatting minus the actual printk() call, allowing an arbitrary print
> function to be supplied instead. And print_hex_dump() is re-implemented
> using
Sparse complains yama_task_prctl can be static. Fix it by making
it static.
Signed-off-by: Mukesh Ojha
---
security/yama/yama_lsm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/yama/yama_lsm.c b/security/yama/yama_lsm.c
index 57cc607..9c5a15b 100644
---
On Mon, Mar 25, 2019 at 09:46:59PM +0530, Anup Patel wrote:
> > Why do you even care about kernel mappings for non-existant ram.
>
> We care because there will always be some buggy kernel driver/code going
> out-of-bound and accessing non-existent RAM. If we by default map all
> possible kernel
Moved code to configure sync to where check enable_sync option before.
There is no need to check enable_sync twice. Configuring sync should be
executed immediately after enabling sync.
Signed-off-by: Sidong Yang
---
drivers/staging/pi433/pi433_if.c | 17 +++--
1 file changed, 7
Hello Nathan,
On Tue, Mar 26, 2019 at 10:01:27PM -0700, Nathan Chancellor wrote:
> Commit 008258d995a6 ("clocksource/drivers/timer-ti-dm: Make
> omap_dm_timer_set_load_start() static") made omap_dm_time_set_load_start
> static because its prototype was not defined in a header. Unfortunately,
>
Hi Jarkko,
my laptop fails to suspend/hibernate since v5.1-rc1, it worked fine
with v4.20 and previous.
My suspect is on tpm_tis driver, is there anything I can do to understand
what goes wrong here?
Best regards,
Domenico
[0.00] Linux version 5.1.0-rc2 (cavok@dumbo) (gcc version
Hi Mika,
Digging up this old thread again...
On Tue, Nov 21, 2017 at 8:13 PM Mika Westerberg
wrote:
>
> On Tue, Nov 21, 2017 at 07:54:26PM +0800, Chris Chiu wrote:
> > Yup, I checked the value of the corresponded pin. It shows following before
> > suspend
> > pin 18 (GPIO_18) GPIO 0x40800102
On 3/26/19 6:46 PM, Ulf Hansson wrote:
On Tue, 26 Mar 2019 at 10:11, Ludovic Barre wrote:
From: Ludovic Barre
This patch defines get_dctrl_cfg callback for legacy variants
whatever DMA_ENGINE configuration.
Signed-off-by: Ludovic Barre
---
drivers/mmc/host/mmci.c | 31
On 3/26/19 17:00, Takashi Iwai wrote:
On Tue, 26 Mar 2019 16:16:54 +0100,
Timo Wischer wrote:
On 3/26/19 15:23, Takashi Iwai wrote:
On Tue, 26 Mar 2019 12:25:37 +0100,
Timo Wischer wrote:
On 3/26/19 09:35, Takashi Iwai wrote:
On Tue, 26 Mar 2019 08:49:33 +0100,
wrote:
Hi Lorenzo/Bjorn,
Could you please help to review this patch series when you have time?
I believe I have addressed all your review comments.
Thanks,
Srinath.
On Fri, Mar 1, 2019 at 10:22 AM Srinath Mannam
wrote:
>
> This patch set extends support of new IPROC PCIe host controller features
> -
wt., 26 mar 2019 o 19:06 Bartosz Golaszewski
napisał(a):
>
> wt., 26 mar 2019 o 05:50 Andrew Jeffery napisał(a):
> >
> > gpio-aspeed implements support for PIN_CONFIG_INPUT_DEBOUNCE. As of
> > v5.1-rc1 we're seeing the following when booting a Romulus BMC kernel:
> >
> > > [ 21.373137]
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Tuesday, March 26, 2019 11:35 PM
> To: Liu, Yi L
> Subject: Re: [RFC v2 1/2] vfio/pci: export common symbols in vfio-pci
>
> On Tue, 26 Mar 2019 12:37:37 +
> "Liu, Yi L" wrote:
>
> > > From: Alex Williamson
On Tue 26-03-19 20:59:48, Qian Cai wrote:
[...]
> Unless there is a brave soul to reimplement the kmemleak to embed it's
> metadata into the tracked memory itself in a foreseeable future, this
> provides a good balance between enabling kmemleak in a low-memory
> situation and not introducing too
On Tue 26-03-19 20:56:14, Vitaly Mayatskikh wrote:
> This fixes OOPS when using under-initialized vhost_vsock object.
>
> The code had a combo of kzalloc plus vmalloc as a fallback
> initially, but it has been replaced by plain kvmalloc in
> commit 6c5ab6511f71 ("mm: support __GFP_REPEAT in
On 2019/3/26 下午7:54, Dan Carpenter wrote:
> On Sat, Mar 23, 2019 at 10:08:35PM +0800, qiaozhou wrote:
>> From: Qiao Zhou
>>
>> add clock driver support for ASR AquilaC SoC.
>>
>> We add clk-gate, clk-mix, and clk-pll drivers:
>> 1. clk-gate driver is for regisers which have different
On Wed, 27 Mar 2019, at 19:11, Bartosz Golaszewski wrote:
> wt., 26 mar 2019 o 19:06 Bartosz Golaszewski
> napisał(a):
> >
> > wt., 26 mar 2019 o 05:50 Andrew Jeffery napisał(a):
> > >
> > > gpio-aspeed implements support for PIN_CONFIG_INPUT_DEBOUNCE. As of
> > > v5.1-rc1 we're seeing the
On Tue, Mar 26, 2019 at 3:31 PM Aisheng Dong wrote:
>
> > From: Daniel Baluta
> > Sent: Tuesday, March 26, 2019 5:43 PM
> >
> > i.MX8QXP contains a total of 4 EDMA controllers of which two are primarily
> > for audio components and the other two are for non-audio periperhals.
> >
> > This patch
Mikhail Gavrilo reported the following bug being triggered in a Fedora
kernel based on 5.1-rc1 but it is relevant to a vanilla kernel.
kernel: page dumped because: VM_BUG_ON_PAGE(PagePoisoned(p))
kernel: [ cut here ]
kernel: kernel BUG at include/linux/mm.h:1021!
Hi Martin,
Thanks a lot.
On 2019/3/26 2:31, Martin Blumenstingl wrote:
Hi Liang,
On Mon, Mar 25, 2019 at 11:03 AM Liang Yang wrote:
Hi Martin,
On 2019/3/23 5:07, Martin Blumenstingl wrote:
Hi Matthew,
On Thu, Mar 21, 2019 at 10:44 PM Matthew Wilcox wrote:
On Thu, Mar 21, 2019 at
On Tue, Mar 26, 2019 at 03:18:21PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> The perf metric expression use duration_time internally to normalize
> events. Normal perf stat without -x also prints the duration time.
> But when using -x, the interval is not output anywhere, which
> is
On Wed, Mar 20, 2019 at 10:53 PM David Howells wrote:
>
> Signed-off-by: David Howells
> cc: Ilya Dryomov
> cc: "Yan, Zheng"
> cc: Sage Weil
> cc: ceph-de...@vger.kernel.org
> ---
>
> drivers/block/rbd.c | 362 +++-
> fs/ceph/cache.c |9 -
>
On Tue 26-03-19 19:58:56, Yang Shi wrote:
>
>
> On 3/26/19 11:37 AM, Michal Hocko wrote:
> > On Tue 26-03-19 11:33:17, Yang Shi wrote:
> > >
> > > On 3/26/19 6:58 AM, Michal Hocko wrote:
> > > > On Sat 23-03-19 12:44:25, Yang Shi wrote:
> > > > > With Dave Hansen's patches merged into Linus's
During system resume from suspend, this can be observed on ASM1062 PMP
controller:
<6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
<6>[12007.593469] ata10.02: hard resetting link
<6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
<6>[12007.911149] ata10.00:
I have now found out that the ledtrig modules don't load automatically.
I would have expected that the linux,default-trigger entries would cause
the load of the corresponding ledtrig modules.
But there is another problem, that the leds are on by default.
Shouldn't they be off by default?
From: Ludovic Barre
This patch series adds get_datactrl_cfg callback in mmci_host_ops
to allow to get datactrl configuration specific at variant.
change V4:
-keep mmci and ux500v2 variant init in the c file.
change V3:
-keep the common functions in mmci_start_data. define
function used by some
On Tue, Mar 26, 2019 at 09:36:48PM +0100, Matteo Croce wrote:
> Got it, sent a v3 with the printk removed.
> Anyway, I wonder if we can remove the 'size' argument and/or moving
> set_real_mode_mem() into realmode.h to have it inlined.
> Or maybe it's not worth it.
Sure, why not. Making the code
From: Ludovic Barre
This patch adds get_datactrl_cfg callback in mmci_host_ops
to allow to get datactrl configuration specific at variant.
Common helper function is defined and could be call by variant.
Signed-off-by: Ludovic Barre
---
drivers/mmc/host/mmci.h | 6 ++
1 file changed, 6
From: Ludovic Barre
This patch allows to get datactrl configuration specific
at variant. This introduce more flexibility on datactlr
value.
Signed-off-by: Ludovic Barre
---
drivers/mmc/host/mmci.c | 26 ++
drivers/mmc/host/mmci.h | 7 ---
2 files changed, 2
From: Ludovic Barre
This patch defines get_dctrl_cfg callback for sdmmc variant.
sdmmc variant has specific stm32 transfer modes.
sdmmc data transfer mode selection could be:
-Block data transfer ending on block count.
-SDIO multibyte data transfer.
-MMC Stream data transfer (not used).
-Block
From: Ludovic Barre
This patch defines get_dctrl_cfg callback for legacy variants
whatever DMA_ENGINE configuration.
Signed-off-by: Ludovic Barre
---
drivers/mmc/host/mmci.c | 30 --
1 file changed, 24 insertions(+), 6 deletions(-)
diff --git
From: Ludovic Barre
This patch defines get_dctrl_cfg callback for qcom variant.
qcom variant has a specific block size definition.
Signed-off-by: Ludovic Barre
---
drivers/mmc/host/mmci_qcom_dml.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/mmc/host/mmci_qcom_dml.c
From: Leon Romanovsky
Kernel is booted with less possible CPUs (possible_cpus kernel boot
option) than available CPUs will have prints like this:
[1.131039] APIC: NR_CPUS/possible_cpus limit of 8 reached. Processor
55/0x1f ignored.
[1.132228] ACPI: Unable to map lapic to logical cpu
On Wed, 27 Mar 2019 09:34:40 +0100,
Timo Wischer wrote:
>
> On 3/26/19 17:00, Takashi Iwai wrote:
> > On Tue, 26 Mar 2019 16:16:54 +0100,
> > Timo Wischer wrote:
> >> On 3/26/19 15:23, Takashi Iwai wrote:
> >>> On Tue, 26 Mar 2019 12:25:37 +0100,
> >>> Timo Wischer wrote:
> On 3/26/19 09:35,
Hi Helmut,
> -Original Message-
> From: Helmut Grohne
> Sent: Tuesday, March 26, 2019 6:57 PM
> To: Naga Sureshkumar Relli
> Cc: bbrezil...@kernel.org; miquel.ray...@bootlin.com; rich...@nod.at;
> dw...@infradead.org; computersforpe...@gmail.com; marek.va...@gmail.com;
> linux-
>
On Mon, 25 Mar 2019 11:54:32 -0400 (EDT)
Mathieu Desnoyers wrote:
> >> +++ b/sysdeps/unix/sysv/linux/s390/bits/rseq.h
> [...]
> >> +
> >> +/* Signature required before each abort handler code. */
> >> +#define RSEQ_SIG 0x53053053
> >
> > Why not a s390 specific value here?
>
> s390 also
On Wed, 2019-03-27 at 11:09 +0200, Leon Romanovsky wrote:
> Kernel is booted with less possible CPUs (possible_cpus kernel boot
> option) than available CPUs will have prints like this:
[]
> diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
[]
> @@ -2305,9 +2305,9 @@ int
Ben Gainey writes:
>> It was an unintentional side effect that it also
>> happened to coincide with context switches in the overwrite mode.
>
> I'm not using overwrite mode, I'm opening the mmap with PROT_WRITE
> (i.e. in truncate mode).
Now I get it. Does the below fix the problem for you?
On 3/27/19 10:11, Takashi Iwai wrote:
On Wed, 27 Mar 2019 09:34:40 +0100,
Timo Wischer wrote:
On 3/26/19 17:00, Takashi Iwai wrote:
On Tue, 26 Mar 2019 16:16:54 +0100,
Timo Wischer wrote:
On 3/26/19 15:23, Takashi Iwai wrote:
On Tue, 26 Mar 2019 12:25:37 +0100,
Timo Wischer wrote:
On
Hi Gwendal,
Unless my pwclient or patchwork is doing something weird I have some issues
trying to apply this patch. Could you check that is correctly formatted?
$ pwclient git-am 1055029
Applying patch #1055029 using u'git am'
Description: [v2] mfd: cros: Update EC protocol to match current EC
Hi Hoan,
Thanks for your work, and sorry for dropping the ball on this in v2.
On 2019-03-27 18:03:18 +0900, Nguyen An Hoan wrote:
> From: Hoan Nguyen An
>
> Fix setting value for IRQCTL register. We are setting the last 6 bits
> of (IRQCTL) to be 1 (0x3f), this is only suitable for H3ES1.*,
Hi Daniel,
Am Mittwoch, den 27.03.2019, 10:51 +0200 schrieb Daniel Baluta:
[...]
>
> > or
> > "fsl,imx8qxp-edma", "fsl,imx8qm-edma"?
>
> One thing that it is not clear for me is why there are places
> where we use two compatible strings?
>
> I understand the situation where are two distinct
On Di, 2019-03-26 at 21:03 +0100, Nicolas Saenz Julienne wrote:
> --- a/drivers/hid/hid-core.c
> +++ b/drivers/hid/hid-core.c
> @@ -218,13 +218,14 @@ static unsigned hid_lookup_collection(struct hid_parser
> *parser, unsigned type)
> * Add a usage to the temporary parser table.
> */
>
>
On Tue, Mar 26, 2019 at 06:48:07PM -0700, Ronald Tschalär wrote:
> The keyboard and trackpad on recent MacBook's (since 8,1) and
> MacBookPro's (13,* and 14,*) are attached to an SPI controller instead
> of USB, as previously. The higher level protocol is not publicly
> documented and hence has
Am Dienstag, den 26.03.2019, 23:38 -0700 schrieb Andrey Smirnov:
> i.MX7D comes with 4 viewports, so configure PCIE node accordingly so
> that the driver won't assume we only have 2.
>
> Signed-off-by: Andrey Smirnov
> Cc: Richard Zhu
> Cc: Chris Healy
> Cc: Lucas Stach
> Cc: Fabio Estevam
>
Am Dienstag, den 26.03.2019, 23:38 -0700 schrieb Andrey Smirnov:
> i.MX6 comes with 4 viewports, so configure PCIE node accordingly so
> that the driver won't assume we only have 2.
>
> Signed-off-by: Andrey Smirnov
> Cc: Richard Zhu
> Cc: Chris Healy
> Cc: Lucas Stach
> Cc: Fabio Estevam
>
On Wed, Mar 27, 2019 at 02:17:40AM -0700, Joe Perches wrote:
> On Wed, 2019-03-27 at 11:09 +0200, Leon Romanovsky wrote:
> > Kernel is booted with less possible CPUs (possible_cpus kernel boot
> > option) than available CPUs will have prints like this:
> []
> > diff --git
On Wed, 27 Mar 2019 10:26:56 +0100,
Timo Wischer wrote:
>
> On 3/27/19 10:11, Takashi Iwai wrote:
> > On Wed, 27 Mar 2019 09:34:40 +0100,
> > Timo Wischer wrote:
> >> On 3/26/19 17:00, Takashi Iwai wrote:
> >>> On Tue, 26 Mar 2019 16:16:54 +0100,
> >>> Timo Wischer wrote:
> On 3/26/19 15:23,
Hi
Thank you for your comments.
On 2019/03/26 18:57, Arnd Bergmann wrote:
On Tue, Mar 26, 2019 at 10:13 AM Sugaya Taichi
wrote:
diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
index 72966bc..961519b 100644
--- a/drivers/tty/serial/Kconfig
+++
Functions, like pr_err, are a more modern variant of printing compared to
printk. They could be used to denoise sources by using needed level in
the print function name, and by automatically inserting per-driver /
function / ... print prefix as defined by pr_fmt macro. pr_* are also
said to be
Miklos,
This is a resend of the patches that teach fs/fuse/ to give filesystems
full control over data cache if the filesystem server indicates to
kernel that it is fully responsible for data cache invalidation. This
functionality is essential when the data in cache are relatively big and
it is
On Wed, 2019-03-27 at 11:38 +0200, Leon Romanovsky wrote:
> On Wed, Mar 27, 2019 at 02:17:40AM -0700, Joe Perches wrote:
> > On Wed, 2019-03-27 at 11:09 +0200, Leon Romanovsky wrote:
> > > Kernel is booted with less possible CPUs (possible_cpus kernel boot
> > > option) than available CPUs will
On Tue, Mar 26, 2019 at 11:44 PM Angus Ainslie wrote:
>
> On 2019-03-19 07:31, Shawn Guo wrote:
> > On Fri, Mar 08, 2019 at 12:02:22PM +, Daniel Baluta wrote:
> >> SDMA1 is part of AIPS-3 region and SDMA2 is part
> >> of AIPS-1 region.
> >>
> >> Reviewed-by: Fabio Estevam
> >
> > Reviewed-by
On Tue, 2019-03-26 at 15:58 +, Lorenzo Pieralisi wrote:
> > We did that internally. You really don't want me telling engineers to
> > post to the list *first* without running things by me to get the basics
> > right. Not to start with, at least.
>
> Hi David,
>
> I am obviously in favour of
On Wed, Mar 27, 2019 at 02:49:02AM -0700, Joe Perches wrote:
> On Wed, 2019-03-27 at 11:38 +0200, Leon Romanovsky wrote:
> > On Wed, Mar 27, 2019 at 02:17:40AM -0700, Joe Perches wrote:
> > > On Wed, 2019-03-27 at 11:09 +0200, Leon Romanovsky wrote:
> > > > Kernel is booted with less possible CPUs
Commit-ID: f19501aa07f18268ab14f458b51c1c6b7f72a134
Gitweb: https://git.kernel.org/tip/f19501aa07f18268ab14f458b51c1c6b7f72a134
Author: Tony Luck
AuthorDate: Tue, 12 Mar 2019 10:09:38 -0700
Committer: Borislav Petkov
CommitDate: Wed, 27 Mar 2019 10:53:49 +0100
x86/mce: Fix
pon., 25 mar 2019 o 14:56 Axel Lin napisał(a):
>
> The pickable linear range is suitable for The MAX77651 SBB1.
> According to MAX77651 TV_SBB1 Code Table:
> Use BIT[1:0] as range selectors.
> Use BIT[5:2] as selectors for each linear range.
>
> The MAX77651 SBB1 supports up to selector 57,
Currently, we do local TLB flush on every MM switch. This is very harsh
on performance because we are forcing page table walks after every MM
switch.
This patch implements ASID allocator for assigning an ASID to every MM
context. The number of ASIDs are limited in HW so we create a logical
entity
On Tue, 2019-03-26 at 12:17 +, Lorenzo Pieralisi wrote:
> This code is basically identical to (apart from the string matching
> the DBI resource)
>
> drivers/pci/controller/pcie-hisi.c
>
> because, as you said, that's a DW quirk that is really not
> platform specific AFAICS.
>
> Not that I
On 26/03/2019 15:13, Vidya Sagar wrote:
> Add support for Synopsys DesignWare core IP based PCIe host controller
> present in Tegra194 SoC.
>
> Signed-off-by: Vidya Sagar
> ---
> drivers/pci/controller/dwc/Kconfig | 10 +
> drivers/pci/controller/dwc/Makefile|1 +
>
Liran Alon writes:
>> On 26 Mar 2019, at 15:48, Vitaly Kuznetsov wrote:
>>
>> Liran Alon writes:
>>
On 26 Mar 2019, at 15:07, Vitaly Kuznetsov wrote:
- Instread of putting the temporary HF_SMM_MASK drop to
rsm_enter_protected_mode() (as was suggested by Liran), move it to
On 26/03/2019 15:13, Vidya Sagar wrote:
> Add PCIe host controller driver for DesignWare core based
> PCIe controller IP present in Tegra194.
>
> Signed-off-by: Vidya Sagar
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On 26/03/2019 15:13, Vidya Sagar wrote:
> Add support for Tegra194 PCIe controllers. These controllers are based
> on Synopsys DesignWare core IP.
>
> Signed-off-by: Vidya Sagar
> ---
> .../bindings/pci/nvidia,tegra194-pcie.txt | 209
> +
>
Yan, Zheng wrote:
> > - if (fsopt->sb_flags != other->mount_options->sb_flags) {
> > + if (fc->sb_flags != sb->s_flags) {
Fixed with:
@@ -945,7 +945,7 @@ static int ceph_compare_super(struct super_block *sb,
struct fs_context *fc)
dout("fsid doesn't match\n");
On Wed, Mar 27, 2019 at 11:53:37AM +0200, Leon Romanovsky wrote:
> On Wed, Mar 27, 2019 at 02:49:02AM -0700, Joe Perches wrote:
> > On Wed, 2019-03-27 at 11:38 +0200, Leon Romanovsky wrote:
> > > On Wed, Mar 27, 2019 at 02:17:40AM -0700, Joe Perches wrote:
> > > > On Wed, 2019-03-27 at 11:09
On 3/27/2019 3:38 PM, Jon Hunter wrote:
On 26/03/2019 15:13, Vidya Sagar wrote:
Add PCIe host controller driver for DesignWare core based
PCIe controller IP present in Tegra194.
Signed-off-by: Vidya Sagar
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi Terry, thanks for the review!
On Tue, 2019-03-26 at 22:43 +, Junge, Terry wrote:
> Hi Nicolas,
>
> This patch looks good except for one comment/question below.
>
> Thanks,
> Terry
>
> On Tuesday, March 26, 2019 1:04 PM Nicolas Saenz Julienne <
> nsaenzjulie...@suse.de> wrote:
> > As
Hi Oliver, thanks for the review!
On Wed, 2019-03-27 at 10:35 +0100, Oliver Neukum wrote:
> On Di, 2019-03-26 at 21:03 +0100, Nicolas Saenz Julienne wrote:
> > --- a/drivers/hid/hid-core.c
> > +++ b/drivers/hid/hid-core.c
> > @@ -218,13 +218,14 @@ static unsigned hid_lookup_collection(struct
> >
On Wed, 2019-03-27 at 12:11 +0200, Leon Romanovsky wrote:
> On Wed, Mar 27, 2019 at 11:53:37AM +0200, Leon Romanovsky wrote:
> > On Wed, Mar 27, 2019 at 02:49:02AM -0700, Joe Perches wrote:
> > > On Wed, 2019-03-27 at 11:38 +0200, Leon Romanovsky wrote:
> > > > On Wed, Mar 27, 2019 at 02:17:40AM
> Hi,
>
> what tree is this patch based on, because it doesn't apply on top of v5.1-rc2.
Hi Bart,
You can use linux-next or regulator tree.
However, due to build dependency you need to manually apply max77650
mfd drvier manually because it's not exist in these tree.
Alternatively, you can check
On Wed, Mar 27, 2019 at 12:11:33PM +0200, Leon Romanovsky wrote:
> ok, I tested your variant and it still prints a t least on my systems,
Probably because your loglevel is set to debug. And no, we don't want to
have to enable some config option in order to see this.
Also, the ugly linebreak
1 - 100 of 1290 matches
Mail list logo
