On 1/29/2019 3:36 PM, Billy Laws wrote:
> Sure, that's fine with me, will send then this gets accepted. Two
> other things: you should probably set the reg to 0 if the property
> isn't specified as regmap_add_irqchip sets it to 0xff (basically all
> enabled on highest limit), and you haven't update
Hi Matthias,
On Monday 28 Jan 2019 at 11:02:51 (-0800), Matthias Kaehlcke wrote:
> > +/**
> > + * of_dev_pm_opp_get_cpu_power() - Estimates the power of a CPU
> > + * @mW:pointer to the power estimate in milli-watts
> > + * @KHz: pointer to the OPP's frequency, in kilo-hertz
>
> nit
On Tue, Jan 29, 2019 at 09:48:51AM +0100, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jan 28, 2019 at 09:00:37AM -0800, Andi Kleen escreveu:
> > > > also now it won't make sample for slave events
> > > > with zero value/period read
> > > >
> > > > note the patch needs to be split into more patches,
Hi Jonas,
On Tue, 29 Jan 2019 at 05:28, Jonas Bonn wrote:
>
> Hi,
>
> On 28/01/2019 19:10, Mark Brown wrote:
> > On Sat, Jan 26, 2019 at 05:32:19PM +0100, Jonas Bonn wrote:
> >
> >> @@ -164,6 +166,7 @@ struct spi_device {
> >> charmodalias[SPI_NAME_SIZE];
> >> const c
On Mon, Jan 28, 2019 at 03:45:05PM +0100, Michal Hocko wrote:
> From: Michal Hocko
>
> Mikhail has reported the following VM_BUG_ON triggered when reading
> sysfs removable state of a memory block:
> page:03d082008000 is uninitialized and poisoned
> page dumped because: VM_BUG_ON_PAGE(PageP
On 28/01/2019 16:07, Stefan Agner wrote:
The imx-ocotp nvmem driver supports the i.MX 7D SoC too. Allow to select
the imx-ocotp driver even if only the i.MX 7D SoC has been selected.
Fixes: 711d45477931 ("nvmem: octop: Add i.MX7D support")
Signed-off-by: Stefan Agner
Applied thanks,
srin
Hello Bartosz,
On Tue, Jan 29, 2019 at 09:44:05AM +0100, Bartosz Golaszewski wrote:
> -void irq_sim_fire(struct irq_sim *sim, unsigned int offset)
> +void irq_sim_fire_type(struct irq_sim *sim,
> +unsigned int offset, unsigned int type)
> {
> struct irq_sim_irq_ctx *ctx
On Mon, Jan 28, 2019 at 09:54:59PM +0100, Jernej Skrabec wrote:
> This adds a compatible for H6. H6 VPU supports 10-bit HEVC decoding and
> additional AFBC output format for HEVC.
>
> Signed-off-by: Jernej Skrabec
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Ke
On Mon, Jan 28, 2019 at 09:55:00PM +0100, Jernej Skrabec wrote:
> H6 VPU doesn't work if DMA offset is set.
>
> Add a quirk for it.
>
> Signed-off-by: Jernej Skrabec
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
signatur
On Mon, Jan 28, 2019 at 09:55:01PM +0100, Jernej Skrabec wrote:
> H6 has improved VPU. It supports 10-bit HEVC decoding and AFBC output
> format for HEVC.
>
> Signed-off-by: Jernej Skrabec
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://
Em Mon, Jan 28, 2019 at 02:35:26PM +0100, Jiri Olsa escreveu:
> On Tue, Jan 15, 2019 at 06:38:38PM +0100, Jiri Olsa wrote:
> > On Tue, Jan 15, 2019 at 04:13:16PM +, Nick Clifton wrote:
> > > Just to be awkward, if you are going to ignore STV_HIDDEN
> > > symbols then you should probably al
On Mon, Jan 28, 2019 at 09:55:02PM +0100, Jernej Skrabec wrote:
> This introduces a new compatible for the H6 SRAM C1 section, that is
> compatible with the SRAM C1 section as found on the A10.
>
> Signed-off-by: Jernej Skrabec
Applied, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux a
On Mon, Jan 28, 2019 at 03:45:06PM +0100, Michal Hocko wrote:
> From: Mikhail Zaslonko
>
> If memory end is not aligned with the sparse memory section boundary, the
> mapping of such a section is only partly initialized. This may lead to
> VM_BUG_ON due to uninitialized struct pages access from t
On Mon, Jan 28, 2019 at 09:55:03PM +0100, Jernej Skrabec wrote:
> Add a node for H6 SRAM C1 section.
>
> Manual calls it VE SRAM, but for consistency with older SoCs, SRAM C1
> name is used.
>
> Signed-off-by: Jernej Skrabec
Applied, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and
Hi Viresh,
On Tuesday 29 Jan 2019 at 10:40:30 (+0530), Viresh Kumar wrote:
> > +int of_dev_pm_opp_get_cpu_power(unsigned long *mW, unsigned long *KHz, int
> > cpu)
>
> I would suggest to change the return type to unsigned long and return 0 for
> errors and positive values for mW.
Well, I can't
On Sat, Jan 26, 2019 at 8:13 PM Jonathan Cameron wrote:
>
> On Fri, 25 Jan 2019 22:14:32 -0200
> Rodrigo Ribeiro wrote:
>
> > Em sex, 25 de jan de 2019 às 21:46, Rodrigo Ribeiro
> > escreveu:
> > >
> > > Em sex, 25 de jan de 2019 às 06:20, Alexandru Ardelean
> > > escreveu:
> > > >
> > > > On T
Some updates (2):
http://8ch.net/tech/res/1018729.html#1024398
Anonymous 01/29/19 (Tue) 08:47:02 No.1024601
1024597
HOW MUCH DID YOU FUCKING PAY ME?
Nothing. Thank God for that.
ARE WE IN A CONTRACT?
No.
IT IS A BARE LICENSE.
Is this lawyer speak? I'm not a lawyer, sorry.
I CAN RESCIND
On Tuesday 29 Jan 2019 at 11:00:41 (+0530), Viresh Kumar wrote:
> On 28-01-19, 16:55, Quentin Perret wrote:
> > Now that PM_OPP provides a helper function to estimate the power
> > consumed by CPUs, make sure to try and register an Energy Model (EM)
> > from cpufreq-dt, hence ensuring interested su
"cat /sys/kernel/debug/bcm2835_thermal/regset" causes a NULL pointer
dereference in bcm2835_thermal_debugfs. The driver makes use of the
implementation details of the thermal framework to retrieve a pointer
to its private data from a struct thermal_zone_device, and gets it
wrong - leading to the cr
On Tue 29-01-19 10:06:05, Oscar Salvador wrote:
> On Mon, Jan 28, 2019 at 03:45:05PM +0100, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > Mikhail has reported the following VM_BUG_ON triggered when reading
> > sysfs removable state of a memory block:
> > page:03d082008000 is uninitializ
On Tue 29-01-19 10:09:08, Oscar Salvador wrote:
> On Mon, Jan 28, 2019 at 03:45:06PM +0100, Michal Hocko wrote:
> > From: Mikhail Zaslonko
> >
> > If memory end is not aligned with the sparse memory section boundary, the
> > mapping of such a section is only partly initialized. This may lead to
>
On Tue, Jan 29, 2019 at 6:46 AM Amit Kucheria wrote:
>
> On Tue, Jan 29, 2019 at 11:06 AM Viresh Kumar wrote:
> >
> > On 29-01-19, 10:25, Amit Kucheria wrote:
> > > All cpufreq drivers do similar things to register as a cooling device.
> > > Provide a cpufreq driver flag so drivers can just ask t
Em Tue, Jan 22, 2019 at 08:45:12PM +0300, Alexey Budankov escreveu:
>
> It has been observed that trace reading thread runs on the same hw thread
> most of the time during perf record sampling collection. This scheduling
> layout leads up to 30% profiling overhead in case when some cpu intensive
>
On 29/01/2019 10:04, Baolin Wang wrote:
Hi Jonas,
On Tue, 29 Jan 2019 at 05:28, Jonas Bonn wrote:
Hi,
On 28/01/2019 19:10, Mark Brown wrote:
On Sat, Jan 26, 2019 at 05:32:19PM +0100, Jonas Bonn wrote:
@@ -164,6 +166,7 @@ struct spi_device {
charmodalias[SPI_NAM
On Tuesday 29 Jan 2019 at 10:51:44 (+0530), Viresh Kumar wrote:
> On 28-01-19, 11:36, Matthias Kaehlcke wrote:
> > I think this patch will result in error messages at registration on
> > platforms that use the cpufreq-dt driver and don't specify
> > 'dynamic-power-coefficient' for the CPUs in the D
Hi,
On Mon, Jan 28, 2019 at 07:24:33PM +0100, Bastien Nocera wrote:
> On Mon, 2019-01-28 at 18:03 +0100, Guido Günther wrote:
> > From what I've seen in vendor trees it's fine to treat this as gt1x¹.
> >
> > [1]:
> > https://github.com/TadiT7/android_kernel_mtk-4.4/tree/master/drivers/input/touch
On Tue, Jan 29, 2019 at 8:09 AM Viresh Kumar wrote:
>
> On 29-01-19, 11:50, Amit Kucheria wrote:
> > On Tue, Jan 29, 2019 at 11:16 AM Amit Kucheria
> > wrote:
> > >
> > > On Tue, Jan 29, 2019 at 11:06 AM Viresh Kumar
> > > wrote:
> > > >
> > > > On 29-01-19, 10:25, Amit Kucheria wrote:
> > > >
On 29/01/2019 03:35, Joseph Lo wrote:
> On 1/28/19 11:09 PM, Thierry Reding wrote:
>> On Mon, Jan 28, 2019 at 05:18:11PM +0800, Joseph Lo wrote:
>>> Add support for the Tegra210 timer that runs at oscillator clock
>>> (TMR10-TMR13). We need these timers to work as clock event device and to
>>> re
On Tue, Jan 29, 2019 at 12:05:21AM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The device links used by rockchip-iommu and exynos-iommu are
> completely managed by these drivers within the IOMMU framework,
> so there is no reason to involve the driver core in the management
> of
Hello,
syzbot found the following crash on:
HEAD commit:085c4c7dd2b6 net: lmc: remove -I. header search path
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12347128c0
kernel config: https://syzkaller.appspot.com/x/.config?x=505743eba4e4f68
dashboard l
Hello,
syzbot found the following crash on:
HEAD commit:983542434e6b Merge tag 'edac_fix_for_5.0' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17476498c0
kernel config: https://syzkaller.appspot.com/x/.config?x=505743eba4e4f68
das
Hi, Bibby:
On Tue, 2019-01-29 at 15:32 +0800, Bibby Hsieh wrote:
> The interrupt mask and thread number has positive correlation,
> so we move the CMDQ_IRQ_MASK into cmdq driver data and calculate
> it by thread number.
>
> Signed-off-by: Bibby Hsieh
> ---
> drivers/mailbox/mtk-cmdq-mailbox.c |
Michael Bringmann writes:
> On 1/25/19 10:09 AM, Michael Bringmann wrote:
>> Adding Nathan Lynch
>>
>> On 1/24/19 6:04 PM, Tyrel Datwyler wrote:
>>> On 12/14/2018 12:50 PM, Michael Bringmann wrote:
Define interface to acquire arch-specific drc info to match against
hotpluggable devices.
On 28/01/2019 19:14, Sai Prakash Ranjan wrote:
SDM845 has ETMv4.2 and can use the existing etm4x driver.
But the current etm driver checks only for ETMv4.0 and
errors out for other etm4x versions. This patch adds this
missing support to enable SoC's with ETMv4x to use same
driver by checking o
> -Original Message-
> From: h...@infradead.org [mailto:h...@infradead.org]
> Sent: 2019年1月28日 16:00
> To: Peng Fan
> Cc: h...@infradead.org; Stefano Stabellini ;
> m...@redhat.com; jasow...@redhat.com; xen-de...@lists.xenproject.org;
> linux-remotep...@vger.kernel.org; linux-kernel@vger
On 28/01/2019 19:14, Sai Prakash Ranjan wrote:
Instead of overriding the peripheral id(PID) check in AMBA
by hardcoding them in DT, add the PIDs to the ETM4x driver.
Here we use Unique Component Identifier(UCI) for MSM8996
since the ETM and CPU debug module shares the same PIDs.
SDM845 does no
Add support for the Tegra210 timer that runs at oscillator clock
(TMR10-TMR13). We need these timers to work as clock event device and to
replace the ARMv8 architected timer due to it can't survive across the
power cycle of the CPU core or CPUPORESET signal. So it can't be a wake-up
source when CPU
The Tegra210 timer provides fourteen 29-bit timer counters and one 32-bit
timestamp counter. The TMRs run at either a fixed 1 MHz clock rate derived
from the oscillator clock (TMR0-TMR9) or directly at the oscillator clock
(TMR10-TMR13). Each TMR can be programmed to generate one-shot periodic,
or
Hi, Bibby:
On Tue, 2019-01-29 at 15:32 +0800, Bibby Hsieh wrote:
> GCE hardware stored event information in own internal sysram,
> if the initial value in those sysram is not zero value
> it will cause a situation that gce can wait the event immediately
> after client ask gce to wait event but not
This is done via RPC call to SCU.
Signed-off-by: Daniel Baluta
---
drivers/firmware/imx/misc.c | 29 +++
include/linux/firmware/imx/svc/misc.h | 3 +++
2 files changed, 32 insertions(+)
diff --git a/drivers/firmware/imx/misc.c b/drivers/firmware/imx/misc.c
ind
Tyrel Datwyler writes:
> On 12/14/2018 12:50 PM, Michael Bringmann wrote:
>> Define interface to acquire arch-specific drc info to match against
>> hotpluggable devices. The current implementation exposes several
>> pseries-specific dynamic memory properties in generic kernel code.
>> This patch
Hi Kishon,
On 14/01/2019 13:24, Kishon Vijay Abraham I wrote:
> commit beb4641a787df79a ("PCI: dwc: Add MSI-X callbacks handler") while
> adding MSI-X callback handler, introduced dw_pcie_ep_find_capability and
> __dw_pcie_ep_find_next_cap for finding the MSI and MSIX capability.
>
> However if M
> > However, you should at least change the comment in vcpu_enter_guest to
> > mention "before reading PIR" instead of "before reading PIR.ON".
>
> Will do that. I think the "checking PIR.ON" should be PID.ON. I will fix it.
>
Hi Paolo,
I reconsidered the comment in vcpu_enter_guest() and thi
Vlad,
On Mon, Jan 28, 2019 at 12:18 PM Oleg Nesterov wrote:
>
> On 01/28, Benjamin Tissoires wrote:
> >
> > Oleg, can you provide some feedback before I push this?
>
> Looks good to me, feel free to add
>
> Reviewed-by: Oleg Nesterov
>
> > > + set_current_state(TASK_RUNNING);
>
> I
On Tue, Jan 29, 2019 at 10:01:08AM +0100, Heiko Carstens wrote:
> However now I see every now and then the following failure from the
> same test case:
>
> tst-robustpi8: ../nptl/pthread_mutex_lock.c:425: __pthread_mutex_lock_full:
> Assertion `INTERNAL_SYSCALL_ERRNO (e, __err) != ESRCH || !robu
On Mon, 2019-01-28 at 22:10 -0800, Stephen Boyd wrote:
> The clk_ops::get_parent function is limited in ability to return errors
> because it returns a u8. A "workaround" to return an error is to return
> a number >= the number of parents of a clk. This will in turn cause the
> framework to "orphan
On Tue, Jan 29, 2019 at 11:19:38AM +0530, Sumit Garg wrote:
> On ARM SoC's with TrustZone enabled, peripherals like entropy sources
> might not be accessible to normal world (linux in this case) and rather
> accessible to secure world (OP-TEE in this case) only. So this driver
> aims to provides a
On Tue, 29 Jan 2019 at 17:14, Jonas Bonn wrote:
>
>
>
> On 29/01/2019 10:04, Baolin Wang wrote:
> > Hi Jonas,
> > On Tue, 29 Jan 2019 at 05:28, Jonas Bonn wrote:
> >>
> >> Hi,
> >>
> >> On 28/01/2019 19:10, Mark Brown wrote:
> >>> On Sat, Jan 26, 2019 at 05:32:19PM +0100, Jonas Bonn wrote:
> >>>
On Tue, Jan 29, 2019 at 12:32:12AM -0800, Roman Kiryanov wrote:
> > How does QEMU do this today? There isn't a virtio or some other virtual
> > memory device that allows memory regions to be shared? I can't believe
> > that there isn't one yet. If not, then this should be some kind of
> > "gener
On Mon, Jan 28, 2019 at 02:27:26PM +0200, Elena Reshetova wrote:
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 3cd13a3..a1e87d2 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -1171,7 +1171,7 @@ static void perf_event_ctx_deactivate(struct
> perf_event_co
Some updates (3):
http://8ch.net/tech/res/1018729.html
Anonymous 01/29/19 (Tue) 09:23:25 No.1024608
1024606
https://copyleft.org/guide/comprehensive-gpl-guidech8.html#x11-540007.4
Sorry lad.
Anonymous 01/29/19 (Tue) 09:25:16 No.1024609
1024604
Cites previously anonomyous paralegal
Adopt the SPDX license identifier headers to ease license compliance
management. Also change the description for one more appropriate.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_sysfs.c | 24
This driver no longer has any pr_{level} messages. Remove the pr_fmt().
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_sysfs.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/platform/ch
Adopt the SPDX license identifier headers to ease license compliance
management. Also change the term 'Chrome OS' for 'ChromeOS' to be
coherent with other drivers.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3: None
Changes in v2: None
.../platform/chrome/
Adopt the SPDX license identifier headers to ease license compliance
management. Also change the description for one more appropriate.
Signed-off-by: Enric Balletbo i Serra
---
Changes in v3:
- cros_ec_spi: Fix SPDX license tag.
Changes in v2: None
drivers/platform/chrome/cros_ec_spi.c | 20 +
Hi,
After the patchset to move cros_ec sysfs attributes to its own drivers,
I'd like to do some cleanup and switch to the SPDX license on all the
platform/chrome drivers.
Best regards,
Enric
Changes in v3:
- Add Reviewed-by tags.
- cros_ec_i2c: Fix SPDX license tag.
- cros_ec_spi: Fix SPDX lic
Adopt the SPDX license identifier headers to ease license compliance
management. Also fix the module license mismatch and change the
description for a more descriptive phrase.
Signed-off-by: Enric Balletbo i Serra
---
Changes in v3:
- cros_ec_i2c: Fix SPDX license tag.
Changes in v2: None
dri
Adopt the SPDX license identifier headers to ease license compliance
management.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_lightbar.c | 22 --
1 file changed, 4 insertions(+)
Adopt the SPDX license identifier headers to ease license compliance
management. Also remove the license boiler-plate and redundant driver
description.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_
This driver no longer has any pr_{level} messages. Remove the pr_fmt().
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_lightbar.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/platform
On Tue, Jan 29, 2019 at 5:09 PM Maxime Ripard wrote:
>
> On Tue, Jan 29, 2019 at 04:44:35PM +0900, Alexandre Courbot wrote:
> > On Fri, Jan 25, 2019 at 10:04 PM Paul Kocialkowski
> > > On Thu, 2019-01-24 at 20:23 +0800, Ayaka wrote:
> > > >
> > > > Sent from my iPad
> > > >
> > > > > On Jan 24, 20
Adopt the SPDX license identifier headers to ease license compliance
management.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_vbc.c | 24 +---
1 file changed, 5 insertions(+), 1
Adopt the SPDX license identifier headers to ease license compliance
management.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_debugfs.c | 22 --
1 file changed, 4 insertions(+),
Adopt the SPDX license identifier headers to ease license compliance
management.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_proto.c | 19 ---
1 file changed, 4 insertions(+), 15 d
Adopt the SPDX license identifier headers to ease license compliance
management. Also fix the module license mismatch and change the term
'Chrome OS' for 'ChromeOS' to be coherent with other drivers.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Guenter Roeck
---
Changes in v3:
- Add Revie
On Mon, Jan 28, 2019 at 02:27:25PM +0200, Elena Reshetova wrote:
> Another set of old patches, rebased and this time the commits
> also updated since we merged the docs in past and also
> refcount_dec_and_test() gets new acquire ordering on success
> very soon, which is also reflected in commit mes
On Tue, 29 Jan 2019 08:31:19 +
Yogesh Narayan Gaur wrote:
> Add MODULE_LICENSE info to fix below warning:
> WARNING: modpost: missing MODULE_LICENSE() in drivers/spi/spi-nxp-fspi.o
>
You miss Fixes and Reported-by tags here.
> Signed-off-by: Yogesh Narayan Gaur
> ---
> drivers/spi/spi-nx
syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:085c4c7dd2b6 net: lmc: remove -I. header search path
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12347128c0
> kernel config: https://syzkaller.appspot.com/x/.config
On Wed, Jan 23, 2019 at 12:45:01AM -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Warning level 3 was used: -Wimplicit-fallthrough=3
>
> This patch is part of the ongoing efforts to enabling
>
On 1/29/19 12:48 AM, shuah wrote:
> Hi Hans,
>
> On 1/28/19 5:03 AM, Hans Verkuil wrote:
>> Hi Shuah,
>>
>> On 1/24/19 9:32 PM, Shuah Khan wrote:
>>> Media Device Allocator API to allows multiple drivers share a media device.
>>> This API solves a very common use-case for media devices where one p
Ravi Bangoria writes:
> On 1/14/19 9:44 AM, Ravi Bangoria wrote:
>> Powerpc hw does not have inbuilt latency filter (--ldlat) for mem-load
>> event and, perf_mem_events by default includes ldlat=30 which is
>> causing failure on powerpc. Refactor code to support perf mem/c2c on
>> powerpc.
>>
>>
On Tue, 29 Jan 2019, Heiko Carstens wrote:
> On Mon, Jan 28, 2019 at 04:53:19PM +0100, Thomas Gleixner wrote:
> > Patch below cures that.
>
> With your patch the kernel warning doesn't occur anymore. So if this
> is supposed to be the fix feel free to add:
Yes, it's supposed to be the fix.
>
> H
On Mon, Jan 28, 2019 at 06:00:15PM +0100, Ard Biesheuvel wrote:
> From: Marc Zyngier
>
> Commit 8208d1708b88b412ca97f50a6d951242c88cbbac upstream.
>
> The way we allocate events works fine in most cases, except
> when multiple PCI devices share an ITS-visible DevID, and that
> one of them is try
Add MODULE_LICENSE info to fix below warning:
WARNING: modpost: missing MODULE_LICENSE() in drivers/spi/spi-nxp-fspi.o
Typo fix in Boris Brezillon last name.
Fixes: a5356aef6a90 ("spi: spi-mem: Add driver for NXP FlexSPI controller")
Reported-by: Stephen Rothwell
Signed-off-by: Yogesh Narayan Ga
On 29/01/2019 10:35, Baolin Wang wrote:
On Tue, 29 Jan 2019 at 17:14, Jonas Bonn wrote:
On 29/01/2019 10:04, Baolin Wang wrote:
Hi Jonas,
On Tue, 29 Jan 2019 at 05:28, Jonas Bonn wrote:
Hi,
On 28/01/2019 19:10, Mark Brown wrote:
On Sat, Jan 26, 2019 at 05:32:19PM +0100, Jonas Bonn w
The interrupt handler contains a workaround for RX hang applicable
to Zynq and AT91RM9200 only. Subsequent versions do not need this
workaround. This workaround unnecessarily resets RX whenever RX used
bit read is observed, which can be often under heavy traffic. There
is no other action performed
On Mon, Jan 28, 2019 at 03:29:10PM +0100, Andrea Parri wrote:
> > diff --git a/arch/x86/include/asm/refcount.h
> > b/arch/x86/include/asm/refcount.h
> > index dbaed55..ab8f584 100644
> > --- a/arch/x86/include/asm/refcount.h
> > +++ b/arch/x86/include/asm/refcount.h
> > @@ -67,16 +67,29 @@ static
Mike Rapoport writes:
> From: Christophe Leroy
>
> Since only the virtual address of allocated blocks is used,
> lets use functions returning directly virtual address.
>
> Those functions have the advantage of also zeroing the block.
>
> [ MR:
> - updated error message in alloc_stack() to be mo
On 29/01/2019 10:10, Phil Elwell wrote:
> "cat /sys/kernel/debug/bcm2835_thermal/regset" causes a NULL pointer
> dereference in bcm2835_thermal_debugfs. The driver makes use of the
> implementation details of the thermal framework to retrieve a pointer
> to its private data from a struct thermal_zo
Em Tue, Jan 29, 2019 at 08:45:44PM +1100, Michael Ellerman escreveu:
> Ravi Bangoria writes:
>
> > On 1/14/19 9:44 AM, Ravi Bangoria wrote:
> >> Powerpc hw does not have inbuilt latency filter (--ldlat) for mem-load
> >> event and, perf_mem_events by default includes ldlat=30 which is
> >> causin
On Tue, Jan 29, 2019 at 11:01:56AM +0800, Axel Lin wrote:
> With current n_voltages setting, regulator_list_voltage will return
> -EINVAL when selector >=57. The highest selector is 0x41, so the
> n_voltages should be 0x41+1, i.e. 66.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/lochnag
"cat /sys/kernel/debug/bcm2835_thermal/regset" causes a NULL pointer
dereference in bcm2835_thermal_debugfs. The driver makes use of the
implementation details of the thermal framework to retrieve a pointer
to its private data from a struct thermal_zone_device, and gets it
wrong - leading to the cr
Mike Rapoport writes:
> diff --git a/arch/arm64/mm/numa.c b/arch/arm64/mm/numa.c
> index ae34e3a..2c61ea4 100644
> --- a/arch/arm64/mm/numa.c
> +++ b/arch/arm64/mm/numa.c
> @@ -237,6 +237,10 @@ static void __init setup_node_data(int nid, u64
> start_pfn, u64 end_pfn)
> pr_info("Ini
Michael Ellerman writes:
> Mike Rapoport writes:
>
>> diff --git a/arch/arm64/mm/numa.c b/arch/arm64/mm/numa.c
>> index ae34e3a..2c61ea4 100644
>> --- a/arch/arm64/mm/numa.c
>> +++ b/arch/arm64/mm/numa.c
>> @@ -237,6 +237,10 @@ static void __init setup_node_data(int nid, u64
>> start_pfn, u64 e
On 29.01.19 08:18, Michal Hocko wrote:
> On Mon 28-01-19 22:09:14, David Hildenbrand wrote:
>> On 28.01.19 21:19, Michal Hocko wrote:
> [...]
>>> David, could you reformulate the changelog accordingly please? My ack
>>> still holds.
>>
>> You mean reformulating + resending for stable kernels only?
On 28.01.19 23:56, Andrew Morton wrote:
> On Mon, 28 Jan 2019 14:53:09 -0800 Andrew Morton
> wrote:
>
>> On Fri, 25 Jan 2019 08:58:33 +0100 Oscar Salvador wrote:
>>
>>> On Wed, Jan 23, 2019 at 11:33:56AM +0100, David Hildenbrand wrote:
If you use {} for the else case, please also do so for
On Mon, Jan 21, 2019 at 4:30 AM Kai-Heng Feng
wrote:
>
>
>
> > On Jan 18, 2019, at 23:50, Benjamin Tissoires
> > wrote:
> >
> > Hi Kai-Heng,
> >
> > On Mon, Jan 7, 2019 at 8:24 AM Kai-Heng Feng
> > wrote:
> >>
> >> While using Elan touchpads, the message floods:
> >> [ 136.138487] i2c_hid i2c-
Hi Jonas, Baolin,
On Tue, Jan 29, 2019 at 10:50 AM Jonas Bonn wrote:
> On 29/01/2019 10:35, Baolin Wang wrote:
> > On Tue, 29 Jan 2019 at 17:14, Jonas Bonn wrote:
> >> On 29/01/2019 10:04, Baolin Wang wrote:
> >>> On Tue, 29 Jan 2019 at 05:28, Jonas Bonn wrote:
> On 28/01/2019 19:10, Mark
On 29.01.19 09:43, Oscar Salvador wrote:
> On Fri, Jan 25, 2019 at 09:53:35AM +0100, David Hildenbrand wrote:
> Hi David,
>
>> I only had a quick glimpse. I would prefer if the caller of add_memory()
>> can specify whether it would be ok to allocate vmmap from the range.
>> This e.g. allows ACPI d
Hi Stephen,
Stephen Boyd wrote on Mon, 28 Jan 2019 22:10:12
-0800:
> There are a couple problems with clk parent handling in the common clk
> framework. This patch series combines a few different topics together as
> all this code is closely related.
>
> First off, we don't do well at determini
On Mon, 2019-01-28 at 22:10 -0800, Stephen Boyd wrote:
> The common clk framework is lacking in ability to describe the clk
> topology without specifying strings for every possible parent-child
> link. There are a few drawbacks to the current approach:
>
> 1) String comparisons are used for every
On Mon 28-01-19 22:41:41, John Hubbard wrote:
> On 1/28/19 5:23 PM, Jerome Glisse wrote:
> > On Mon, Jan 28, 2019 at 04:22:16PM -0800, John Hubbard wrote:
> > > On 1/23/19 11:04 AM, Jerome Glisse wrote:
> > > > On Wed, Jan 23, 2019 at 07:02:30PM +0100, Jan Kara wrote:
> > > > > On Tue 22-01-19 11:4
On 29-01-19, 14:35, Andrew-sh Cheng wrote:
> From: "Andrew-sh.Cheng"
>
> For new mediatek chip mt8183,
> cci and little cluster share the same buck,
> so need to modify the attribute of regulator from exclusive to optional
>
> Intermediate clock is not always enabled by ccf in different projects
On Tue, Jan 29, 2019 at 01:27:09AM +0300, Dmitry Osipenko wrote:
> 29.01.2019 1:15, Sowjanya Komatineni пишет:
> >
> >
> > Update I2C transfer timeout based on transfer bytes and I2C bus rate
> > to allow enough time during max transfer size based on the speed.
>
> Could it be
On Fri, Jan 25, 2019 at 2:08 PM Matias Bjørling wrote:
>
> On 1/25/19 11:09 AM, Javier González wrote:
> > In order to respect mw_cuinits, pblk's write buffer maintains a
> > backpointer to protect data not yet persisted; when writing to the write
> > buffer, this backpointer defines a threshold t
Hi Daniel,
On 29/01/2019 09:52, Daniel Lezcano wrote:
> On 29/01/2019 10:10, Phil Elwell wrote:
>> "cat /sys/kernel/debug/bcm2835_thermal/regset" causes a NULL pointer
>> dereference in bcm2835_thermal_debugfs. The driver makes use of the
>> implementation details of the thermal framework to retri
On Tue, Jan 29, 2019 at 11:15:05AM +0100, Thierry Reding wrote:
> On Tue, Jan 29, 2019 at 01:27:09AM +0300, Dmitry Osipenko wrote:
> > 29.01.2019 1:15, Sowjanya Komatineni пишет:
> > >
> > >
> > > Update I2C transfer timeout based on transfer bytes and I2C bus rate
> > > to allow enough
Hi Gustavo,
On 29/01/19 2:55 PM, Gustavo Pimentel wrote:
> Hi Kishon,
>
> On 14/01/2019 13:24, Kishon Vijay Abraham I wrote:
>> commit beb4641a787df79a ("PCI: dwc: Add MSI-X callbacks handler") while
>> adding MSI-X callback handler, introduced dw_pcie_ep_find_capability and
>> __dw_pcie_ep_find_
VOP is broken in mainline since commit 1ce9e6055fa0a9043 ("virtio_ring:
introduce packed ring support"); attempting to use the virtqueues leads
to various kernel crashes. I'm testing it with my not-yet-merged
loopback patches, but even the in-tree MIC hardware cannot work.
The problem is not in t
From: Martin Kepplinger
Use devm_gpiod_get_optional() and gpiod_set_value_cansleep() instead
of the old API. The st1232_ts_power() now passes on the inverted "poweron"
value to reflect the correct logical value.
Signed-off-by: Martin Kepplinger
---
Tested and works. thanks for your help Dmitry
101 - 200 of 1483 matches
Mail list logo
