From: Mathieu Poirier
Introducing function partition_sched_domains_locked() by taking
the mutex locking code out of the original function. That way
the work done by partition_sched_domains_locked() can be reused
without dropping the mutex lock.
No change of functionality is introduced by this p
callback_lock grants the holder read-only access to cpusets. For fixing
a synchronization issue between cpusets and scheduler core, it is now
required to make callback_lock available to core scheduler code.
Convert callback_lock to raw_spin_lock, so that it will be always safe
to acquire it from
If a task happens to be throttled while the CPU it was running on gets
hotplugged off, the bandwidth associated with the task is not correctly
migrated with it when the replenishment timer fires (offline_migration).
Fix things up, for this_bw, running_bw and total_bw, when replenishment
timer fire
Hi,
v7 of a series of patches, originally authored by Mathieu, with the intent
of fixing a long standing issue of SCHED_DEADLINE bandwidth accounting.
As originally reported by Steve [1], when hotplug and/or (certain)
cpuset reconfiguration operations take place, DEADLINE bandwidth
accounting info
These are build artifacts, which should be ignored by git.
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Fix a typo in subject: "vdso.so" -> "vdso.lds"
arch/nds32/kernel/.gitignore | 1 +
arch/nds32/kernel/vdso/.gitignore | 1 +
2 files changed, 2 insertions(+)
create mode 100644
On Mon, Mar 18, 2019 at 03:09:55AM +, Anson Huang wrote:
> The System Controller Firmware (SCFW) controls RTC, thermal
> and WDOG etc., these resources' interrupt function are managed
> by SCU. When any IRQ pending, SCU will notify Linux via MU general
> interrupt channel #3, and Linux kernel n
Hello Lee,
Thanks for taking a look on this again =) I agree with most of the
comments and correct them at next version.
On Wed, Apr 03, 2019 at 08:31:52AM +0100, Lee Jones wrote:
> On Mon, 25 Mar 2019, Matti Vaittinen wrote:
>
> > ROHM BD70528MWV is an ultra-low quiescent current general
> > pu
cpuset_common_seq_show operations atomicity is currently guarded by
callback_lock. Since these operations are initiated by userspace holding
a raw_spin_lock is not wise.
Convert the function to use cpuset_mutex to fix the problem.
Signed-off-by: Juri Lelli
---
kernel/cgroup/cpuset.c | 4 ++--
1
When the topology of root domains is modified by CPUset or CPUhotplug
operations information about the current deadline bandwidth held in the
root domain is lost.
This patch addresses the issue by recalculating the lost deadline
bandwidth information by circling through the deadline tasks held in
No synchronisation mechanism exists between the cpuset subsystem and calls
to function __sched_setscheduler(). As such, it is possible that new root
domains are created on the cpuset side while a deadline acceptance test
is carried out in __sched_setscheduler(), leading to a potential oversell
of C
- $(call if_changed,...) must have FORCE as a prerequisite
- vdso.lds is a generated file, so it should be prefixed with
$(obj)/ instead of $(src)/.
- cmd_vdsosym is a one-liner rule, so the assignment with '='
is simpler.
Signed-off-by: Masahiro Yamada
---
arch/arm64/kernel/vdso/Makefile
From: Mathieu Poirier
Calls to task_rq_unlock() are done several times in function
__sched_setscheduler(). This is fine when only the rq lock needs to be
handled but not so much when other locks come into play.
This patch streamlines the release of the rq lock so that only one
location need to
On 03.04.19 10:46, Michal Hocko wrote:
> On Thu 28-03-19 14:43:18, Oscar Salvador wrote:
>> From: Michal Hocko
>>
>> arch_add_memory, __add_pages take a want_memblock which controls whether
>> the newly added memory should get the sysfs memblock user API (e.g.
>> ZONE_DEVICE users do not want/need
On Wed 03-04-19 10:41:35, David Hildenbrand wrote:
> On 03.04.19 10:37, Michal Hocko wrote:
[...]
> > That being said it should be the caller of the hotplug code to tell
> > the vmemmap allocation strategy. For starter, I would only pack vmemmaps
> > for "regular" kernel zone memory. Movable zones
On Tue, Apr 02, 2019 at 10:37:21AM -0700, Sowjanya Komatineni wrote:
> This patch adds suspend and resume PM ops for tegra SDHCI.
>
> Signed-off-by: Sowjanya Komatineni
> ---
> drivers/mmc/host/sdhci-tegra.c | 56
> +-
> 1 file changed, 55 insertions(+),
On Wed, Apr 03, 2019 at 10:41:35AM +0200, David Hildenbrand wrote:
> > That being said it should be the caller of the hotplug code to tell
> > the vmemmap allocation strategy. For starter, I would only pack vmemmaps
> > for "regular" kernel zone memory. Movable zones should be more careful.
> > We
Add ChromeOS EC ISHTP driver.
Sends ChromeOS EC host commands over ISHTP to ISH firmware.
Signed-off-by: Rushikesh S Kadam
---
v2
- Dropped unused "reset" parameter in function cros_ec_init()
- Change driver name to cros_ec_ishtp to be consistent with other
references in the code.
- Fixed
On 03.04.19 10:49, Michal Hocko wrote:
> On Wed 03-04-19 10:41:35, David Hildenbrand wrote:
>> On 03.04.19 10:37, Michal Hocko wrote:
> [...]
>>> That being said it should be the caller of the hotplug code to tell
>>> the vmemmap allocation strategy. For starter, I would only pack vmemmaps
>>> for
On Fri, Mar 29, 2019 at 07:44:21AM +, Anson Huang wrote:
> Hi, Guenter/Shawn
> Since DT has been acked, would you pick up this patch series if no
> additional comments?
>
Applied patch #3 and #4, thanks.
On 03.04.19 10:50, Oscar Salvador wrote:
> On Wed, Apr 03, 2019 at 10:41:35AM +0200, David Hildenbrand wrote:
>>> That being said it should be the caller of the hotplug code to tell
>>> the vmemmap allocation strategy. For starter, I would only pack vmemmaps
>>> for "regular" kernel zone memory. Mo
Hi,
On 03-04-19 07:43, Kai-Heng Feng wrote:
i2c-designware-platdrv fails to work after the system restored from
hibernation:
[ 272.775692] i2c_designware 80860F41:00: Unknown Synopsys component type:
0x
Commit 48402cee6889 ("ACPI / LPSS: Resume BYT/CHT I2C controllers from
resume_noirq
On Tue, Apr 02, 2019 at 12:06:06PM -0700, Guenter Roeck wrote:
> On Mon, Apr 01, 2019 at 07:00:12PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.0.6 release.
> > There are 146 patches in this series, all will be posted as a response
> > to this one. I
On Tue, Apr 02, 2019 at 05:34:16PM -0600, shuah wrote:
> On 4/1/19 11:00 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.0.6 release.
> > There are 146 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with t
From: Bartosz Golaszewski
This series adds support for max77650 ultra low-power PMIC. It provides
the core mfd driver and a set of five sub-drivers for the regulator,
power supply, gpio, leds and input subsystems.
Patches 1-4 add the DT binding documents. Patch 5 documents mfd_add_devices().
Pat
From: Bartosz Golaszewski
Add a kernel doc for mfd_add_devices().
Signed-off-by: Bartosz Golaszewski
Acked-by: Pavel Machek
---
drivers/mfd/mfd-core.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c
index 94e3f32ce935..1ade4c8
From: Bartosz Golaszewski
This adds basic support for LEDs for the max77650 PMIC. The device has
three current sinks for driving LEDs.
Signed-off-by: Bartosz Golaszewski
Acked-by: Jacek Anaszewski
---
drivers/leds/Kconfig | 6 ++
drivers/leds/Makefile| 1 +
drivers/leds/le
From: Bartosz Golaszewski
Add the core mfd driver for max77650 PMIC. We define five sub-devices
for which the drivers will be added in subsequent patches.
Signed-off-by: Bartosz Golaszewski
---
drivers/mfd/Kconfig | 14 +++
drivers/mfd/Makefile | 1 +
drivers/mfd/max77650.c
From: Bartosz Golaszewski
Add basic support for the battery charger for max77650 PMIC.
Signed-off-by: Bartosz Golaszewski
---
drivers/power/supply/Kconfig| 7 +
drivers/power/supply/Makefile | 1 +
drivers/power/supply/max77650-charger.c | 367
From: Bartosz Golaszewski
Add GPIO support for max77650 mfd device. This PMIC exposes a single
GPIO line.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Linus Walleij
---
drivers/gpio/Kconfig | 7 ++
drivers/gpio/Makefile| 1 +
drivers/gpio/gpio-max77650.c | 190 +
From: Bartosz Golaszewski
I plan on extending this set of drivers so add myself as maintainer.
Signed-off-by: Bartosz Golaszewski
---
MAINTAINERS | 14 ++
1 file changed, 14 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 43b36dbed48e..d8bdaeb72b95 100644
--- a/MAINTAIN
From: Bartosz Golaszewski
Add support for the push- and slide-button events for max77650.
Signed-off-by: Bartosz Golaszewski
Acked-by: Dmitry Torokhov
Acked-by: Pavel Machek
---
drivers/input/misc/Kconfig | 9 +++
drivers/input/misc/Makefile | 1 +
drivers/input/misc/max
From: Bartosz Golaszewski
Add the DT binding document for the LEDs module of max77650.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Rob Herring
---
.../bindings/leds/leds-max77650.txt | 57 +++
1 file changed, 57 insertions(+)
create mode 100644 Documentation/dev
From: Bartosz Golaszewski
Add the DT binding document for the onkey module of max77650.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Rob Herring
---
.../bindings/input/max77650-onkey.txt | 26 +++
1 file changed, 26 insertions(+)
create mode 100644 Documentation/de
From: Bartosz Golaszewski
Add the DT binding document for the battery charger module of max77650.
Signed-off-by: Bartosz Golaszewski
---
.../power/supply/max77650-charger.txt | 27 +++
1 file changed, 27 insertions(+)
create mode 100644
Documentation/devicetree/bindin
From: Bartosz Golaszewski
Add a DT binding document for max77650 ultra-low power PMIC. This
describes the core mfd device and the GPIO module.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Rob Herring
Acked-by: Pavel Machek
Acked-for-MFD-by: Lee Jones
---
.../devicetree/bindings/mfd/max77
And thanks again for fixing the language. Appreciated!
On Wed, Apr 03, 2019 at 08:34:26AM +0100, Lee Jones wrote:
> On Mon, 25 Mar 2019, Matti Vaittinen wrote:
>
> > Document bindings for regulators (3 bucks, 3 LDOs and 2 LED
> > drivers) and 4 GPIO pins which can be configured for I/O or
> > as
On Tue, Apr 02, 2019 at 05:36:20PM +0530, Mukesh Ojha wrote:
>
> On 4/2/2019 4:01 PM, Greg Kroah-Hartman wrote:
> > There are a few remaining drivers/staging/*/Makefile files that do not
> > have SPDX identifiers in them. Add the correct GPL-2.0 identifier to
> > them to make scanning tools happy
On Tue, Apr 02, 2019 at 12:37:57PM +0200, Stefan Wahren wrote:
> Am 02.04.19 um 12:31 schrieb Greg Kroah-Hartman:
> > Now that the SPDX tag is in all vc04_services files, that identifies the
> > license in a specific and legally-defined manner. So the extra GPL and
> > BSD text wording can be remo
Hi,
On 02-04-19 18:04, Luís Ferreira wrote:
Some ultrabooks, like Teclast F6 Pro, use KIOX010A sensor on display
and KIOX020A sensor on keyboard base, to detect tablet mode or screen
orientation.
I deliberately left out the KIOX020A id for now, because currently
userspace cannot really deal wi
On Tue, Mar 26, 2019 at 07:22:56PM +0100, Jonathan Neuschäfer wrote:
> There are a few differences between the i.MX50 clock tree and those of
> i.MX51 and i.MX53 that are not yet handled in clk-imx51-imx53.c. This
> series handles two of them.
>
> Jonathan Neuschäfer (2):
> clk: imx5: Fix i.MX5
From: Miaohe Lin
It should be IPv6|UDP instead of IPv4|UDP for NETIF_F_IPV6_CSUM
Signed-off-by: linmiaohe
---
include/linux/skbuff.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index 69b5538adcea..9683e00a5a79 100644
--- a
On 4/2/2019 7:44 PM, Thierry Reding wrote:
On Tue, Apr 02, 2019 at 12:47:48PM +0530, Vidya Sagar wrote:
On 3/30/2019 2:22 AM, Bjorn Helgaas wrote:
[...]
+static int tegra_pcie_dw_host_init(struct pcie_port *pp)
+{
[...]
+ val_w = dw_pcie_readw_dbi(pci, CFG_LINK_STATUS);
+ while (
On Wed 03-04-19 10:00:04, Anshuman Khandual wrote:
> Memory hot remove uses get_nid_for_pfn() while tearing down linked sysfs
> entries between memory block and node. It first checks pfn validity with
> pfn_valid_within() before fetching nid. With CONFIG_HOLES_IN_ZONE config
> (arm64 has this enabl
at 22:08, wrote:
-Original Message-
From: Kai Heng Feng
Sent: Monday, April 1, 2019 11:18 PM
To: Limonciello, Mario
Cc: Andy Shevchenko; hdego...@redhat.com; benjamin.tissoi...@redhat.com;
hotwater...@tutanota.com; ji...@kernel.org; swb...@chromium.org;
bige...@linutronix.de; d...@chr
Display controller reset must be done as soon as possible after enable
the clock to avoid partial refresh on screen.
Signed-off-by: Yannick Fertré
---
drivers/gpu/drm/stm/ltdc.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/
From: NeilBrown
> Sent: 02 April 2019 22:11
>
> On Tue, Apr 02 2019, David Laight wrote:
>
> > From: NeilBrown
> >> Sent: 02 April 2019 00:08
> >>
> >> This patch changes rhashtables to use a bit_spin_lock on BIT(1) of the
> >> bucket pointer to lock the hash chain for that bucket.
> > ...
> >> T
> > Subject: [PATCH 2/6] input: da9063_onkey: remove platform_data support
> >
> > There are no in-kernel users anymore, so remove this outdated interface.
> >
> > Signed-off-by: Wolfram Sang
> > ---
> > drivers/input/misc/da9063_onkey.c | 11 ++-
> > 1 file changed, 2 insertions(+), 9
On Wed 03-04-19 10:00:05, Anshuman Khandual wrote:
> From: Robin Murphy
>
> Enabling ZONE_DEVICE (through ARCH_HAS_ZONE_DEVICE) for arm64 reveals that
> memremap's internal helpers for sparsemem sections conflict with arm64's
> definitions for hugepages which inherit the name of "sections" from e
On Wed, 03 Apr 2019, Matti Vaittinen wrote:
> Hello Lee,
>
> Thanks for taking a look on this again =) I agree with most of the
> comments and correct them at next version.
>
> On Wed, Apr 03, 2019 at 08:31:52AM +0100, Lee Jones wrote:
> > On Mon, 25 Mar 2019, Matti Vaittinen wrote:
> >
> > > R
On 03.04.19 06:30, Anshuman Khandual wrote:
> From: Robin Murphy
>
> Enabling ZONE_DEVICE (through ARCH_HAS_ZONE_DEVICE) for arm64 reveals that
> memremap's internal helpers for sparsemem sections conflict with arm64's
> definitions for hugepages which inherit the name of "sections" from earlier
On 03.04.19 06:30, Anshuman Khandual wrote:
> Memory hot remove uses get_nid_for_pfn() while tearing down linked sysfs
> entries between memory block and node. It first checks pfn validity with
> pfn_valid_within() before fetching nid. With CONFIG_HOLES_IN_ZONE config
> (arm64 has this enabled) pfn
On 28/03/2019 14:31, Rob Herring wrote:
On Tue, Mar 12, 2019 at 02:35:17PM +0530, Vignesh Raghavendra wrote:
Add dt bindings for TI syscon gate clock.
Signed-off-by: Vignesh Raghavendra
---
.../bindings/clock/ti,syscon-gate-clock.txt | 35 +++
1 file changed, 35 insertions
On Wed, Apr 03, 2019 at 10:37:57AM +0200, Michal Hocko wrote:
> That being said it should be the caller of the hotplug code to tell
> the vmemmap allocation strategy. For starter, I would only pack vmemmaps
> for "regular" kernel zone memory. Movable zones should be more careful.
> We can always re
On Tue, Mar 26, 2019 at 11:38:40PM -0700, Andrey Smirnov wrote:
> 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
> C
From: Finley Xiao
>From Rockchips fractional divider usage, some clocks can be generated
by fractional divider, but the input clock frequency of fractional
divider should be less than a specified value.
Signed-off-by: Finley Xiao
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/clk-px30.c
1. Support for some new features
2. fix up some error
Elaine Zhang (4):
clk: rockchip: fix up the frac clk get rate error
clk: rockchip: add a clock-type for muxes based in the pmugrf
clk: rockchip: add pll up and down when change pll freq
clk: rockchip: support pll setting by auto
Finley
support fractional divider with only one level parent clock
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/clk.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/drivers/clk/rockchip/clk.c b/drivers/clk/rockchip/clk.c
index e04bf300ea0a..0256a99f06f3
On 4/3/2019 12:01 AM, Bjorn Helgaas wrote:
On Tue, Apr 02, 2019 at 12:47:48PM +0530, Vidya Sagar wrote:
On 3/30/2019 2:22 AM, Bjorn Helgaas wrote:
On Tue, Mar 26, 2019 at 08:43:26PM +0530, Vidya Sagar wrote:
Add support for Synopsys DesignWare core IP based PCIe host controller
present in Tegr
Rockchip socs often have some tiny number of muxes not controlled from
the core clock controller but through bits set in the pmugrf.
Use MUXPMUGRF() to cover this special clock-type.
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/clk.c | 9 +
drivers/clk/rockchip/clk.h | 17 ++
From: Finley Xiao
The div offset of some clocks are different from their mux offset
and the COMPOSITE clock-type require that div and mux offset are
the same, so add a new COMPOSITE_DIV_OFFSET clock-type to handle that.
Signed-off-by: Finley Xiao
Signed-off-by: Elaine Zhang
---
drivers/clk/ro
If setting freq is not support in rockchip_pll_rate_table,
It can calculate and set pll params by auto.
Signed-off-by: Elaine Zhang
---
drivers/clk/rockchip/clk-pll.c | 215 ++---
1 file changed, 200 insertions(+), 15 deletions(-)
diff --git a/drivers/clk/roc
set pll sequence:
->set pll to slow mode or other plls
->set pll down
->set pll params
->set pll up
->wait pll lock status
->set pll to normal mode
To slove the system error:
wait_pll_lock: timeout waiting for pll to lock
pll_set_params: pll update u
tested with: X86_64_defconfig + SPI=y, IIO=m
STAGING=y, ADIS16203=m
Patch is against 5.1-rc3 (localversion-next is next-20190403)
drivers/staging/iio/accel/adis16203.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/iio/accel/adis16203.c
b/drivers/staging/iio/accel/adis16203.c
tested with: x86_64_defconfig + SPI=y, IIO=m
STAGING=y, ADIS16240=m
Patch is against 5.1-rc3 (localversion-next is next-20190403)
drivers/staging/iio/accel/adis16240.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/iio/accel/adis16240.c
b/drivers/staging/iio/accel/adis16240.c
I use linux 5.1.0-rc3 on s390 and got this WARN_ON_ONCE message:
WARNING: CPU: 15 PID: 0 at kernel/events/core.c:330
event_function_local.constprop.79+0xe2/0xe8
which was introduced with
commit cca2094605ef ("perf/core: Fix event_function_local()").
This is the WARN_ON_ONCE me
"Yan, Zheng" writes:
> On Fri, Mar 22, 2019 at 6:04 PM Luis Henriques wrote:
>>
>> Luis Henriques writes:
>>
>> > "Yan, Zheng" writes:
>> >
>> >> On Tue, Mar 19, 2019 at 12:22 AM Luis Henriques
>> >> wrote:
>> >>>
>> >>> "Yan, Zheng" writes:
>> >>>
>> >>> > On Mon, Mar 18, 2019 at 6:33 PM L
On Tue, Apr 02, 2019 at 06:18:53AM -0700, Paul E. McKenney wrote:
> On Tue, Apr 02, 2019 at 09:09:53AM +0200, Peter Zijlstra wrote:
> > On Mon, Apr 01, 2019 at 10:22:57AM -0700, Paul E. McKenney wrote:
> > > Or am I missing something that gets the scheduler on the job faster?
> >
> > Oh urgh, yah
Assalamu Alaikum Wa Rahmatullahi Wa Barakatuh,
hello dear
I came across your contact during my private search. Mrs Aisha Al-
Qaddafi is my name, the only daughter of late Libyan president, am a
single Mother and a Widow with three Children.I have funds the sum of
$27.5 million USD for, investme
From: Ajit Pandey
There is a second AEC loopback on cs47l90 so the registers for it should
be readable.
Signed-off-by: Ajit Pandey
Signed-off-by: Charles Keepax
---
drivers/mfd/cs47l90-tables.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mfd/cs47l90-tables.c b/drivers/mfd/cs
From: Richard Fitzgerald
There is a second AEC loopback on cs47l35 so the registers for it should
be readable.
Signed-off-by: Richard Fitzgerald
Signed-off-by: Charles Keepax
---
drivers/mfd/cs47l35-tables.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mfd/cs47l35-tables.c b/
On Wed, 27 Feb 2019, Amelie Delaunay wrote:
> STMicroelectronics Multi-Function eXpander (STMFX) is a slave controller
> using I2C for communication with the main MCU. Main features are:
> - 16 fast GPIOs individually configurable in input/output
> - 8 alternate GPIOs individually configurable in
On Mon, 01 Apr 2019, Maxime Ripard wrote:
> On Mon, Apr 01, 2019 at 10:36:24PM +1100, Stephen Rothwell wrote:
> > Hi Lee,
> >
> > On Mon, 1 Apr 2019 11:27:32 +0100 Lee Jones wrote:
> > >
> > > On Thu, 28 Mar 2019, Stephen Rothwell wrote:
> > >
> > > > I reported that a while ago (x86_64 allmodcon
Vinod,
Thanks for your review, I'm preparing v2.
On 11/02/2019 at 12:58, Vinod Koul wrote:
> On 05-02-19, 12:03, Nicolas Ferre wrote:
>> Complement the identification of errors with stoping the channel and
>> dumping the descriptor that led to the error case.
>>
>> Signed-off-by: Nicolas Ferre
>
On Wed, 13 Feb 2019, tudor.amba...@microchip.com wrote:
> From: Tudor Ambarus
>
> Adopt the SPDX license identifiers to ease license compliance
> management.
>
> Signed-off-by: Tudor Ambarus
> ---
> include/linux/mfd/syscon/atmel-matrix.h | 6 +-
> include/linux/mfd/syscon/atmel-mc.h
On Wed, Apr 03, 2019 at 10:30:15AM +0100, Lee Jones wrote:
> On Wed, 03 Apr 2019, Matti Vaittinen wrote:
>
> > Hello Lee,
> >
> > Thanks for taking a look on this again =) I agree with most of the
> > comments and correct them at next version.
> >
> > On Wed, Apr 03, 2019 at 08:31:52AM +0100, Le
The overflow error flag (ROI: Request Overflow Error) is only relevant
for the case when the channel handles a peripheral synchronized transfer.
Not in the case of memory to memory transfer where there is no hardware
request signal.
Remove the use of this interrupt source in such a case. It's base
Complement the identification of errors with stoping the channel and
dumping the descriptor that led to the error case.
Signed-off-by: Nicolas Ferre
Acked-by: Ludovic Desroches
---
v2: added Ludovic's tag
address Vinod's comments (typo, comment, empty line before logical blocks)
drivers/dm
Even if this case shouldn't happen when controller is properly programmed,
it's still better to avoid dumping a kernel Oops for this.
As the sequence may happen only for debugging purposes, log the error and
just finish the tasklet call.
Signed-off-by: Nicolas Ferre
Acked-by: Ludovic Desroches
-
From: Bai Ping
The system counter (sys_ctr) is a programmable system counter
which provides a shared time base to the Cortex A15, A7, A53 etc cores.
It is intended for use in applications where the counter is always
powered on and supports multiple, unrelated clocks. The sys_ctr hardware
supports
From: Bai Ping
Add the binding doc for nxp system counter timer module.
Signed-off-by: Bai Ping
---
change v1->v2
- remove the blank line at EOF
change v2->v3
- update the binding example based on the driver change
---
.../devicetree/bindings/timer/nxp,sysctr-timer.txt | 25 +
Vinod,
Please disregard this series: I'm sending a v3 right now. Sorry for the
noise.
Best regards,
Nicolas
On 03/04/2019 at 12:09, Nicolas Ferre wrote:
> Even if this case shouldn't happen when controller is properly programmed,
> it's still better to avoid dumping a kernel Oops for this.
>
The overflow error flag (ROI: Request Overflow Error) is only relevant
for the case when the channel handles a peripheral synchronized transfer.
Not in the case of memory to memory transfer where there is no hardware
request signal.
Remove the use of this interrupt source in such a case. It's base
Complement the identification of errors with stopping the channel and
dumping the descriptor that led to the error case.
Signed-off-by: Nicolas Ferre
Acked-by: Ludovic Desroches
---
v3: Typo in commit message, alignment in multi-line dev_dbg()
v2: added Ludovic's tag
address Vinod's comments
Even if this case shouldn't happen when controller is properly programmed,
it's still better to avoid dumping a kernel Oops for this.
As the sequence may happen only for debugging purposes, log the error and
just finish the tasklet call.
Signed-off-by: Nicolas Ferre
Acked-by: Ludovic Desroches
-
Commit 6bd288569b50bc89fa5513031086746968f585cb upstream.
Debug exception handlers may be called for exceptions generated both by
user and kernel code. In many cases, this is checked explicitly, but
in other cases things either happen to work by happy accident or they
go slightly wrong.
Fix this
Commit b9a4b9d084d978f80eb9210727c81804588b42ff upstream.
FAR_EL1 is UNKNOWN for all debug exceptions other than those caused by
taking a hardware watchpoint. Unfortunately, if a debug handler returns
a non-zero value, then we will propagate the UNKNOWN FAR value to
userspace via the si_addr field
Commit 6bd288569b50bc89fa5513031086746968f585cb upstream.
Debug exception handlers may be called for exceptions generated both by
user and kernel code. In many cases, this is checked explicitly, but
in other cases things either happen to work by happy accident or they
go slightly wrong. For exampl
Commit b9a4b9d084d978f80eb9210727c81804588b42ff upstream.
FAR_EL1 is UNKNOWN for all debug exceptions other than those caused by
taking a hardware watchpoint. Unfortunately, if a debug handler returns
a non-zero value, then we will propagate the UNKNOWN FAR value to
userspace via the si_addr field
Commit b9a4b9d084d978f80eb9210727c81804588b42ff upstream.
FAR_EL1 is UNKNOWN for all debug exceptions other than those caused by
taking a hardware watchpoint. Unfortunately, if a debug handler returns
a non-zero value, then we will propagate the UNKNOWN FAR value to
userspace via the si_addr field
$ grep -r 'call if_changed,' -B
shows a few more FWIW:
drivers/scsi/Makefile
drivers/gpu/drm/radeon/Makefile
arch/c6x/boot/Makefile
arch/arm64/kernel/vdso/Makefile
arch/x86/entry/vdso/Makefile
arch/x86/entry/syscalls/Makefile
arch/powerpc/platforms/cell/spufs/Makefile
arch/powerpc/kernel/syscalls
Commit-ID: 1279e41d535e28cc3b56fa4a09e71a709641cae6
Gitweb: https://git.kernel.org/tip/1279e41d535e28cc3b56fa4a09e71a709641cae6
Author: Shaokun Zhang
AuthorDate: Wed, 3 Apr 2019 14:54:24 +0800
Committer: Ingo Molnar
CommitDate: Wed, 3 Apr 2019 11:40:02 +0200
perf/headers: Fix stale com
This patch series has implementation for "virtio pmem".
"virtio pmem" is fake persistent memory(nvdimm) in guest
which allows to bypass the guest page cache. This also
implements a VIRTIO based asynchronous flush mechanism.
Sharing guest kernel driver in this patchset with the
changes
Commit-ID: d7262457e35dbe239659e62654e56f8ddb814bed
Gitweb: https://git.kernel.org/tip/d7262457e35dbe239659e62654e56f8ddb814bed
Author: Peter Zijlstra
AuthorDate: Thu, 21 Mar 2019 13:38:49 +0100
Committer: Ingo Molnar
CommitDate: Wed, 3 Apr 2019 11:40:32 +0200
perf/x86/intel: Initializ
On Wed, Apr 03, 2019 at 11:47:00AM +0200, Thomas-Mich Richter wrote:
> I use linux 5.1.0-rc3 on s390 and got this WARN_ON_ONCE message:
>
> WARNING: CPU: 15 PID: 0 at kernel/events/core.c:330
> event_function_local.constprop.79+0xe2/0xe8
>
> which was introduced with
>commit c
Commit-ID: 914123fa39042e651d79eaf86bbf63a1b938dddf
Gitweb: https://git.kernel.org/tip/914123fa39042e651d79eaf86bbf63a1b938dddf
Author: Lendacky, Thomas
AuthorDate: Tue, 2 Apr 2019 15:21:14 +
Committer: Ingo Molnar
CommitDate: Wed, 3 Apr 2019 11:40:32 +0200
x86/perf/amd: Resolve ra
Virtio pmem provides asynchronous host page cache flush
mechanism. We don't support 'MAP_SYNC' with virtio pmem
and ext4.
Signed-off-by: Pankaj Gupta
---
fs/ext4/file.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/fs/ext4/file.c b/fs/ext4/file.c
index 69d65d4
Commit-ID: 6d3edaae16c6c7d238360f2841212c2b26774d5e
Gitweb: https://git.kernel.org/tip/6d3edaae16c6c7d238360f2841212c2b26774d5e
Author: Lendacky, Thomas
AuthorDate: Tue, 2 Apr 2019 15:21:16 +
Committer: Ingo Molnar
CommitDate: Wed, 3 Apr 2019 11:40:32 +0200
x86/perf/amd: Resolve NM
Virtio pmem provides asynchronous host page cache flush
mechanism. we don't support 'MAP_SYNC' with virtio pmem
and xfs.
Signed-off-by: Pankaj Gupta
---
fs/xfs/xfs_file.c | 8
1 file changed, 8 insertions(+)
diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
index 1f2e2845eb76..dced2e
18.03.2019 1:52, Dmitry Osipenko пишет:
> Hello,
>
> This patchset adds support for the Trusted Foundations firmware on
> NVIDIA Tegra30. Pretty much all of Tegra30 consumer devices have that
> firmware and upstream kernel can't boot on those devices without the
> firmware support. This series was
Commit-ID: 60f52ab61c7dc0a991125903ae06a35d1812698c
Gitweb: https://git.kernel.org/tip/60f52ab61c7dc0a991125903ae06a35d1812698c
Author: Lendacky, Thomas
AuthorDate: Tue, 2 Apr 2019 15:21:18 +
Committer: Ingo Molnar
CommitDate: Wed, 3 Apr 2019 11:40:32 +0200
x86/perf/amd: Remove nee
101 - 200 of 957 matches
Mail list logo
