On 2019/9/2 17:35, Borislav Petkov wrote:
On Mon, Sep 02, 2019 at 05:30:24PM +0800, Zhenzhong Duan wrote:
Builds kernel with "make bzImage EXTRA_CFLAGS=-Wall", gcc complains:
arch/x86/boot/compressed/pgtable_64.c: In function 'paging_prepare':
arch/x86/boot/compressed/pgtable_64.c:92:7: warni
From: Colin Ian King
The return statement is incorrect, the error exit should be by
assigning ret with the error code and exiting via label out.
Thanks to Valdis Klētnieks for correcting my original fix.
Addresses-Coverity: ("Structurally dead code")
Signed-off-by: Colin Ian King
---
V2: exit
Acked-by: Hugues Fruchet
On 8/27/19 4:09 PM, Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 27 Aug 2019 16:00:13 +0200
>
> A null pointer would be passed to a call of the function “of_node_put”
> immediately after a call of the function “of_graph_get_next_endpoint”
> failed at one pl
On Tue, 09 Jul 2019, Matthias Kaehlcke wrote:
> Backlight brightness curves can have different shapes. The two main
> types are linear and non-linear curves. The human eye doesn't
> perceive linearly increasing/decreasing brightness as linear (see
> also 88ba95bedb79 "backlight: pwm_bl: Compute br
On Mon, 02 Sep 2019 12:03:12 +1000
Michael Ellerman wrote:
> Michal Suchanek writes:
> > On bigendian ppc64 it is common to have 32bit legacy binaries but much
> > less so on littleendian.
>
> I think the toolchain people will tell you that there is no 32-bit
> little endian ABI defined at al
Hi,
On 02/09/2019 05:54, Cheng-Yi Chiang wrote:
> In the designware databook, the sequence of enabling audio clock and
> setting format is not clearly specified.
> Currently, audio clock is enabled in the end of hw_param ops after
> setting format.
>
> On some monitors, there is a possibility tha
On Sun, 18 Aug 2019, Frank Wunderlich wrote:
> paths in dt-bindings should be relative as suggested by Lee Johnes
>
> Suggested-By: Lee Jones
> Signed-off-by: Frank Wunderlich
> ---
> changes since v5: splitted from dt-bindings: add powercontroller
> ---
> Documentation/devicetree/bindings/mfd
On Sun, 18 Aug 2019, Frank Wunderlich wrote:
> From: Josef Friedl
>
> add mt6323 to rtc-bindings
>
> Signed-off-by: Josef Friedl
> Signed-off-by: Frank Wunderlich
> ---
> changes since v5: splitted from "dt-bindings: add powercontroller"
> ---
> Documentation/devicetree/bindings/mfd/mt6397.t
Hi Martin,
On 9/2/2019 5:38 AM, Martin Blumenstingl wrote:
Hi,
On Fri, Aug 30, 2019 at 5:02 AM Chuan Hua, Lei
wrote:
Hi Martin,
On 8/30/2019 5:40 AM, Martin Blumenstingl wrote:
Hi,
On Thu, Aug 29, 2019 at 4:51 AM Chuan Hua, Lei
wrote:
I'm not surprised that we got some of the IP block
On Sun, 18 Aug 2019, Frank Wunderlich wrote:
> From: Josef Friedl
>
> - add powercontroller-section to existing binding-document
> - add mt6323-pwrc bindings-document with example
>
> Suggested-by: Frank Wunderlich
> Signed-off-by: Josef Friedl
> Signed-off-by: Frank Wunderlich
> Acked-for-M
On Sun, 18 Aug 2019, Frank Wunderlich wrote:
> From: Josef Friedl
>
> move code to separate header-file to reuse definitions later
> in poweroff-driver (drivers/power/reset/mt6323-poweroff.c)
>
> Suggested-by: Frank Wunderlich
> Signed-off-by: Josef Friedl
> Signed-off-by: Frank Wunderlich
>
On Mon, Sep 02, 2019 at 10:11:30AM +0300, Sakari Ailus wrote:
> On Fri, Aug 30, 2019 at 03:53:14PM +0300, Andy Shevchenko wrote:
> > On Thu, Aug 29, 2019 at 01:10:40PM +0300, Sakari Ailus wrote:
> > > Instead of implementing our own means of discovering parent nodes, node
> > > names or counting ho
On Sun, 18 Aug 2019, Frank Wunderlich wrote:
> From: Josef Friedl
>
> add missing mutex.h
In future, please use correct English grammar in commit messages.
I will fix them for this submission.
> Signed-off-by: Josef Friedl
> Signed-off-by: Frank Wunderlich
> ---
> changes since v5: separate
On Sun, 18 Aug 2019, Frank Wunderlich wrote:
> From: Josef Friedl
>
> simplyfications (resource definitions my DEFINE_RES_* macros)
>
> Signed-off-by: Josef Friedl
> Signed-off-by: Frank Wunderlich
> Acked-for-MFD-by: Lee Jones
> ---
> changes since v5: none
> changes since v4: do not touch
On Sun, 18 Aug 2019, Frank Wunderlich wrote:
> From: Josef Friedl
>
> add entry for rtc and power-controller to mt6323
>
> Signed-off-by: Josef Friedl
> Signed-off-by: Frank Wunderlich
> Acked-for-MFD-by: Lee Jones
> ---
> changes since v5: none
> changes since v4: none
> changes since v3: n
Hi,
Now that rc1 is released is time to send another patchset rebased on
top. This is an attempt to clean up a bit more the cros-ec driver
to have a better separation on what is part of the MFD subsystem and
what is part of platform/chrome.
The major changes introduced by this patchset are:
1. Mo
With the purpose of remove the things that far extends the bounds of
what a MFD was designed to do, instantiate the new platform misc
cros-ec-chardev driver and get rid of all the unneeded code. After this
patch the misc chardev driver is a sub-device of the MFD, and all the
new file operations sho
That's a driver to talk with the ChromeOS Embedded Controller via a
miscellaneous character device, it creates an entry in /dev for every
instance and implements basic file operations for communicating with the
Embedded Controller with an userspace application. The API is moved to
the uapi folder,
Now, the ChromeOS EC core driver has nothing related to an MFD device, so
move that driver from the MFD subsystem to the platform/chrome subsystem.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Andy Shevchenko
Acked-by: Thierry Reding
Acked-by: Mark Brown
Acked-by: Wolfram Sang
Acked-by: Ne
The cros-ec-dev is a multifunction device that now doesn't implement any
chardev communication interface. MFD_CROS_EC_CHARDEV doesn't look
a good name to describe that device and can cause confusion. Hence
rename it to CROS_EC_DEV.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Andy Shevchenko
An MFD is a device that contains several sub-devices (cells). For instance,
the ChromeOS EC fits in this description as usually contains a charger and
can have other devices with different functions like a Real-Time Clock,
an Audio codec, a Real-Time Clock, ...
If you look at the driver, though, w
Use mfd_add_hotplug_devices() helper to register the subdevices. The
helper allows us to reduce the boiler plate and also registers the
subdevices in the same way as used in other functions used in this
files.
Signed-off-by: Enric Balletbo i Serra
Reviewed-by: Gwendal Grignou
Tested-by: Gwendal
The CrOS EC is gaining lots of subdevices that are autodetectable by
sending the EC_FEATURE_GET_CMD, it takes fair amount of boiler plate
code to add those devices. So, add a struct that can be used to quickly
add new subdevices without having to duplicate code.
Signed-off-by: Enric Balletbo i Ser
With the increasing use of dedicated CrOS EC MCUs, it takes a fair amount
of boiler plate code to add those devices, add a struct that can be used
to specify a dedicated CrOS EC MCU so we can just add a new item to it to
define a new dedicated MCU.
Signed-off-by: Enric Balletbo i Serra
Acked-by:
There is a bit of mess between cros-ec mfd includes and platform
includes. For example, we have a linux/mfd/cros_ec.h include that
exports the interface implemented in platform/chrome/cros_ec_proto.c. Or
we have a linux/mfd/cros_ec_commands.h file that is non related to the
multifunction device (in
This patch makes use of cros_ec_cmd_xfer_status() instead of
cros_ec_cmd_xfer() so we can remove some redundant code. It also uses
kzalloc instead of kmalloc so we can remove more redundant code.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Andy Shevchenko
Reviewed-by: Gwendal Grignou
Tested
On 8/31/2019 6:43 PM, Michael S. Tsirkin wrote:
> On Fri, Aug 30, 2019 at 05:58:23PM +, Matej Genci wrote:
>> On 8/30/2019 3:02 PM, Michael S. Tsirkin wrote:
>>> On Tue, Aug 27, 2019 at 03:20:57PM +, Matej Genci wrote:
Compilers such as g++ 7.3 complain about assigning void* variable t
On Wed, Aug 21, 2019 at 06:35:40PM +0300, Jonathan Chocron wrote:
> This series adds support for Amazon's Annapurna Labs DT-based PCIe host
> controller driver.
> Additionally, it adds 3 quirks (ACS, VPD and MSI-X) and 2 generic DWC patches.
>
> Changes since v3:
> - Removed PATCH 8/8 since the us
On Sun, Sep 01, 2019 at 06:17:58AM -0400, Michael S. Tsirkin wrote:
> On Sun, Sep 01, 2019 at 04:26:19AM -0400, Michael S. Tsirkin wrote:
> > On Thu, Aug 01, 2019 at 03:36:16PM +0200, Stefano Garzarella wrote:
> > > On Thu, Aug 01, 2019 at 09:21:15AM -0400, Michael S. Tsirkin wrote:
> > > > On Thu,
On Sat, Aug 31, 2019 at 11:09:14AM +0800, Peter Cai wrote:
> On GPD P2 Max, the firmware could not reset the touch panel correctly.
> The kernel needs to take on the job instead, but the GpioInt definition
> in DSDT specifies ActiveHigh while the GPIO pin should actually be
> ActiveLow.
>
> We nee
Original pin node values of ASUS UX431FL with ALC294:
0x12 0xb7a60140
0x13 0x4000
0x14 0x90170110
0x15 0x41f0
0x16 0x41f0
0x17 0x90170111
0x18 0x41f0
0x19 0x41f0
0x1a 0x41f0
0x1b 0x41f0
0x1d 0x4066852d
0x1e 0x41f0
0x1f 0x41f0
0x21 0x04211020
1. Has duplicated i
On Sat, Aug 31, 2019 at 11:09:15AM +0800, Peter Cai wrote:
> The firmware of GPD P2 Max could not handle panel resets although code
> is present in DSDT. The kernel needs to take on this job instead, but
> the DSDT does not provide _DSD, rendering kernel helpless when trying to
> find the respectiv
On Sun, Sep 01, 2019 at 04:23:03PM +0200, Remi Pommarel wrote:
> advk_pcie_wait_pio() can be called while holding a spinlock (from
> pci_bus_read_config_dword()), then depends on jiffies in order to
> timeout while polling on PIO state registers. In the case the PIO
> transaction failed, the timeou
From: "amy.shih"
According to kernel hwmon sysfs-interface documentation, temperature
critical max value, typically greater than corresponding temp_max values.
Thus, reads the LTD_HV_HL (LTD HIGH VALUE HIGH LIMITATION) and LTD_LV_HL
(LTD LOW VALUE HIGH LIMITATION) for case hwmon_temp_crit and
hwm
On Mon, Sep 02, 2019 at 10:08:46AM +0100, Catalin Marinas wrote:
> On Mon, Sep 02, 2019 at 11:44:43AM +1000, Michael Ellerman wrote:
> > Stephen Rothwell writes:
> > > Hi all,
> > >
> > > Today's linux-next merge of the powerpc tree got a conflict in:
> > >
> > > arch/Kconfig
> > >
> > > between
On 19/9/2 17:34, Colin King wrote:
> From: Colin Ian King
>
> At the end of ocfs2_inode_lock_tracker tmp_oh is true because an
> earlier check on tmp_oh being false returns out of the function.
> Since tmp_oh is true, the function will always return 1 so remove
> the redundant check and return
On Mon, Sep 02, 2019 at 11:32:30AM +0300, Sakari Ailus wrote:
> The software_node_get_parent() returned a pointer to the parent swnode,
> but did not take a reference to it, leading the caller to put a reference
> that was not taken. Take that reference now.
>
Missed already given
Reviewed-by: A
From: Eugen Hristev
Some i2c controllers have a built-in digital or analog filter.
This is specifically required depending on the hardware PCB/board.
Some controllers also allow specifying the maximum width of the
spikes that can be filtered. The width length can be specified in nanoseconds.
Sig
From: Eugen Hristev
Add compatible for new Microchip SoC, sam9x60
Reviewed-by: Rob Herring
Signed-off-by: Eugen Hristev
---
Documentation/devicetree/bindings/i2c/i2c-at91.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-at91.t
From: Eugen Hristev
Add new platform data support for digital filtering for i2c.
The sama5d4, sama5d2 and sam9x60 support this feature.
Signed-off-by: Eugen Hristev
---
drivers/i2c/busses/i2c-at91-core.c | 9 +
drivers/i2c/busses/i2c-at91-master.c | 9 +
drivers/i2c/busses/i2
From: Eugen Hristev
Add new platform data support for the sam9x60 SoC
Signed-off-by: Eugen Hristev
---
drivers/i2c/busses/i2c-at91-core.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/i2c/busses/i2c-at91-core.c
b/drivers/i2c/busses/i2c-at91-core.c
index 435c7d7..caf
From: Eugen Hristev
This optional timing property specifies the width of the spikes on the i2c
lines (in ns) that can be filtered out by built-in analog or digital filters
which are embedded in some i2c controllers.
Include it in the timings structure and read it as integer property.
Signed-off-
From: Eugen Hristev
Add support for analog filtering for i2c lines.
The sama5d2 and sam9x60 support this feature.
Signed-off-by: Eugen Hristev
---
drivers/i2c/busses/i2c-at91-core.c | 9 +
drivers/i2c/busses/i2c-at91-master.c | 18 ++
drivers/i2c/busses/i2c-at91.h
From: Eugen Hristev
Add new platform data support for advanced digital filtering for i2c.
The sama5d2 and sam9x60 support this feature.
This digital filter allows the user to configure the maximum
width of the spikes that can be filtered.
Signed-off-by: Eugen Hristev
---
drivers/i2c/busses/i2c
On Mon, Sep 02, 2019 at 11:32:32AM +0300, Sakari Ailus wrote:
> Move fwnode_get_parent() above fwnode_get_next_parent(), making the order
> the same as in the header file.
>
Reviewed-by: Andy Shevchenko
> Signed-off-by: Sakari Ailus
> ---
> drivers/base/property.c | 26 +--
From: Eugen Hristev
Hello,
This series adds support for analog and digital filters for i2c controllers
This series is based on the series:
[PATCH v2 0/9] i2c: at91: filters support for at91 SoCs
and enhanced to add the bindings for all controllers plus an extra binding
for the width of the spik
From: Eugen Hristev
Add property for analog and digital filter for i2c1 and i2c2 nodes
for sama5d2_xplained
Signed-off-by: Eugen Hristev
---
arch/arm/boot/dts/at91-sama5d2_xplained.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/at91-sama5d2_xplained.dts
b/arch
From: Eugen Hristev
Add property for digital filter for i2c0 node sama5d4_xplained
Signed-off-by: Eugen Hristev
---
arch/arm/boot/dts/at91-sama5d4_xplained.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/at91-sama5d4_xplained.dts
b/arch/arm/boot/dts/at91-sama5d4_xpla
On Mon, Sep 02, 2019 at 11:32:33AM +0300, Sakari Ailus wrote:
> Add two convenience functions for accessing node's parents:
>
> fwnode_count_parents() returns the number of parent nodes a given node
> has. fwnode_get_nth_parent() returns node's parent at a given distance
> from the node itself.
>
On Mon, Sep 02, 2019 at 11:32:35AM +0300, Sakari Ailus wrote:
> The prefix is used for printing purpose before a node, and it also works
> as a separator between two nodes.
>
Reviewed-by: Andy Shevchenko
> Signed-off-by: Sakari Ailus
> Acked-by: Rob Herring (for OF)
> ---
> drivers/acpi/prop
On Wed, Aug 28, 2019 at 10:58:47PM +0530, Vidya Sagar wrote:
> Add support to configure sideband signal pins when information is present
> in respective controller's device-tree node.
>
> Signed-off-by: Vidya Sagar
Reviewed-by: Andrew Murray
> ---
> V3:
> * Used 'dev' instead of 'pcie->dev'
>
On Mon, Sep 02, 2019 at 11:32:38AM +0300, Sakari Ailus wrote:
> Factor out static kobject_string() function that simply calls
> device_node_string(), and thus remove references to kobjects (as these are
> struct device_node).
>
FWIW,
Reviewed-by: Andy Shevchenko
> Signed-off-by: Sakari Ailus
>
This patchset workarounds an PP2 HW limitation which prevents to use
per-cpu rx buffers.
The first patch is just a refactor to prepare for the second one.
The second one allocates percpu buffers if the following conditions are met:
- CPU number is less or equal 4
- no port is using jumbo frames
If
Every mvpp2 unit can use up to 8 buffers mapped by the BM (the HW buffer
manager). The HW will place the frames in the buffer pool depending on the
frame size: short (< 128 bytes), long (< 1664) or jumbo (up to 9856).
As any unit can have up to 4 ports, the driver allocates only 2 pools,
one for s
Refactor mvpp2_bm_pool_create(), mvpp2_bm_pool_destroy() and
mvpp2_bm_pools_init() so that they accept a struct device instead
of a struct platform_device, as they just need platform_device->dev.
Removing such dependency makes the BM code more reusable in context
where we don't have a pointer to t
Catalin Marinas writes:
> On Mon, Sep 02, 2019 at 11:44:43AM +1000, Michael Ellerman wrote:
>> Stephen Rothwell writes:
>> > Hi all,
>> >
>> > Today's linux-next merge of the powerpc tree got a conflict in:
>> >
>> > arch/Kconfig
>> >
>> > between commit:
>> >
>> > 5cf896fb6be3 ("arm64: Add s
On Wed, Aug 28, 2019 at 10:58:48PM +0530, Vidya Sagar wrote:
> Add support to get regulator information of 3.3V and 12V supplies of a PCIe
> slot from the respective controller's device-tree node and enable those
> supplies. This is required in platforms like p2972- where the supplies
> to x16
In the comment for arch_prepare_optimized_kprobe, "instuction" should
actually be "instruction". This patch fixes the typo.
Signed-off-by: Marco Ammon
---
arch/x86/kernel/kprobes/opt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/kprobes/opt.c b/arch/x86/ke
In the documentation for text_poke_early, "protected again" should
actually be "protected against". This patch fixes the spelling mistake.
Signed-off-by: Marco Ammon
---
arch/x86/include/asm/text-patching.h | 4 ++--
arch/x86/kernel/alternative.c| 4 ++--
2 files changed, 4 insertions(+)
In the documentation for alternative_instructions, "a unlikely" should
actually be "an unlikely". This patch fixes the mistake.
Signed-off-by: Marco Ammon
---
arch/x86/kernel/alternative.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/alternative.c b/arch/x8
There's a misplaced traceline in rxrpc_input_packet() which is looking at a
packet that just got released rather than the replacement packet.
Fix this by moving the traceline after the assignment that moves the new
packet pointer to the actual packet pointer.
Fixes: d0d5c0cd1e71 ("rxrpc: Use skb_
Hi Jose,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Jose-Abreu/net-stmmac-Improvements-for-next/20190902-160927
config: mips-allmodconfig (attached as .config)
compiler: mips-linux-gcc (GCC
Enjoy!
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
ib-mfd-extcon-hid-i2c-iio-input-media-chrome-power-pwm-rtc-sound-v
On Wed, Aug 28, 2019 at 10:58:45PM +0530, Vidya Sagar wrote:
> Add optional bindings "pinctrl-names" and "pinctrl-0" to describe pin
> configuration information of a particular PCIe controller.
>
> Signed-off-by: Vidya Sagar
Reviewed-by: Andrew Murray
> ---
> V3:
> * None
>
> V2:
> * None
>
On Wed, Aug 28, 2019 at 10:58:46PM +0530, Vidya Sagar wrote:
> Add optional bindings "vpcie3v3-supply" and "vpcie12v-supply" to describe
> regulators of a PCIe slot's supplies 3.3V and 12V provided the platform
> is designed to have regulator controlled slot supplies.
>
> Signed-off-by: Vidya Saga
When cpus != maxcpus cpuidle-haltpoll will fail to register all vcpus
past the online ones and thus fail to register the idle driver.
This is because cpuidle_add_sysfs() will return with -ENODEV as a
consequence from get_cpu_device() return no device for a non-existing
CPU.
Instead switch to cpuid
On 2019-09-02 12:11, eugen.hris...@microchip.com wrote:
> From: Eugen Hristev
>
> Add compatible for new Microchip SoC, sam9x60
>
> Reviewed-by: Rob Herring
> Signed-off-by: Eugen Hristev
> ---
> Documentation/devicetree/bindings/i2c/i2c-at91.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1
On 28/08/2019 12:18, Nagarjuna Kristam wrote:
> Tegra fuse clock handle is retrieved in tegra_fuse_probe().
> tegra_fuse_readl() is exported symbol, which can be called from drivers
> at any time. tegra_fuse_readl() enables fuse clock and reads corresponding
> fuse register offset.
>
> Calling t
On Wed, Aug 28, 2019 at 10:58:49PM +0530, Vidya Sagar wrote:
> Add support to configure PCIe C5's sideband signals PERST# and CLKREQ#
> as output and bi-directional signals respectively which unlike other
> PCIe controllers sideband signals are not configured by default.
>
> Signed-off-by: Vidya S
On Wed, Aug 28, 2019 at 10:58:50PM +0530, Vidya Sagar wrote:
> Add 3.3V and 12V supplies regulators information of x16 PCIe slot in
> p2972- platform which is owned by C5 controller and also enable C5
> controller.
>
> Signed-off-by: Vidya Sagar
Reviewed-by: Andrew Murray
> ---
> V3:
> * N
On 2019-09-02 12:12, eugen.hris...@microchip.com wrote:
> From: Eugen Hristev
>
> Some i2c controllers have a built-in digital or analog filter.
> This is specifically required depending on the hardware PCB/board.
> Some controllers also allow specifying the maximum width of the
> spikes that can
On 8/29/19 4:27 PM, Marcelo Tosatti wrote:
> On Thu, Aug 29, 2019 at 04:10:27PM +0100, Joao Martins wrote:
>> When cpus != maxcpus cpuidle-haltpoll will fail to register all vcpus
>> past the online ones and thus fail to register the idle driver.
>> This is because cpuidle_add_sysfs() will return w
On 2019-09-02 10:10, Neil Armstrong wrote:
> On 01/09/2019 18:14, Jonas Karlman wrote:
>> Update CEC phys addr and EDID on HPD event, fixes lost CEC phys addr and
>> stale EDID when HDMI cable is unplugged/replugged or AVR is powered on/off.
>>
>> Signed-off-by: Jonas Karlman
>> ---
>> drivers/gp
On Mon, Sep 02, 2019 at 09:58:59AM +0200, Christoph Hellwig wrote:
> On Mon, Sep 02, 2019 at 05:51:58AM +, Jason Gunthorpe wrote:
> > On Sun, Sep 01, 2019 at 01:35:16PM -0700, Guenter Roeck wrote:
> > > > I belive the macros above are missing brackets.. Can you confirm the
> > > > below takes c
Hi all,
After merging the hmm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
ERROR: "__nd_driver_register" [drivers/dax/pmem/dax_pmem_compat.ko] undefined!
ERROR: "nvdimm_namespace_common_probe" [drivers/dax/pmem/dax_pmem_core.ko]
undefined!
ERROR: "devm_nsio_disable" [dr
My @arm.com email address will stop working in a few weeks, so add an
entry to .mailmap so others have a way to reach me if they want to.
While at it, move some entries around to keep the file in alphabetical
order.
Signed-off-by: Quentin Perret
---
Hi guys,
Will/Catalin: any chance this could
On Sun, Sep 01, 2019 at 04:23:03PM +0200, Remi Pommarel wrote:
> advk_pcie_wait_pio() can be called while holding a spinlock (from
> pci_bus_read_config_dword()), then depends on jiffies in order to
> timeout while polling on PIO state registers. In the case the PIO
> transaction failed, the timeou
On Mo, 2019-08-19 at 06:17 +, Wei Yongjun wrote:
> Add the missing unlock before return from function
> etnaviv_iommuv1_context_alloc()
> in the error handling case.
>
> Fixes: 27b67278e007 ("drm/etnaviv: rework MMU handling")
> Signed-off-by: Wei Yongjun
Thanks, applied.
For my education,
On Mon, Sep 02, 2019 at 08:50:17PM +1000, Stephen Rothwell wrote:
> Hi all,
> ERROR: "nd_region_provider_data" [drivers/acpi/nfit/nfit.ko] undefined!
> ERROR: "to_nd_blk_region" [drivers/acpi/nfit/nfit.ko] undefined!
> ERROR: "nvdimm_region_notify" [drivers/acpi/nfit/nfit.ko] undefined!
> ERROR: "
On 22/08/2019 04:17, Rik van Riel wrote:
> The current implementation of the CPU controller uses hierarchical
> runqueues, where on wakeup a task is enqueued on its group's runqueue,
> the group is enqueued on the runqueue of the group above it, etc.
>
> This increases a fairly large amount of ove
All other boards use compatible = "omap36xx".
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-evm-37xx.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-evm-37xx.dts
b/arch/arm/boot/dts/omap3-evm-37xx.dts
index e0c0382388f0..311550ee
In addition, move omap3 from whitelist to blacklist in cpufreq-dt-platdev
in the same patch, because doing either first breaks operation and
may make trouble in bisect.
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap34xx.dtsi | 59 +++-
arch/arm/boot/d
This patch set converts the opp tables to opp-v2 format
and extends the ti-cpufreq to support omap3.
It adds 720 MHz (omap34xx) and 1 GHz (omap36xx) OPPs but
tells the ti-cpufreq driver to disable them if the speed
binned / 720MHz grade eFuse bits indicate that the chip
is not rated for that speed
This adds code and tables to read the silicon revision and
eFuse (speed binned / 720 MHz grade) bits for selecting
opp-v2 table entries.
Since these bits are not always part of the syscon register
range (like for am3, am4, dra7), we add code to directly read
the register values using ioremap() if
Matching the ti-cpufreq driver needs to specify explicitly if
a board uses an omap34xx or omap36xx chip.
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-beagle.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/arch/arm/b
With opp-v2 in omap36xx.dtsi and ti-cpufreq driver the
1GHz capability is automatically detected.
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-n950-n9.dtsi | 7 ---
1 file changed, 7 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-n950-n9.dtsi
b/arch/arm/boot/dts/omap3
Hello Maxime,
On Mon, Sep 02, 2019 at 09:27:35AM +0200, Maxime Ripard wrote:
> Hi,
>
> On Sun, Sep 01, 2019 at 11:52:14PM +0200, Ondřej Jirman wrote:
> > Hello Yangtao,
> >
> > On Sat, Aug 10, 2019 at 05:28:11AM +, Yangtao Li wrote:
> > > This patchset add support for A64, H3, H5, H6 and R40
Michael,
On Mon, 2 Sep 2019, Alexandre Belloni wrote:
> On 31/08/2019 20:32:06+0200, Michael wrote:
> > currently I have a problem with the alarmtimer i'm using to cyclically wake
> > up my i.MX6 ULL board from suspend to RAM.
> >
> > The problem is that in principle the timer wake ups work fine
Since BUG() and WARN() may use a trap (e.g. UD2 on x86) to
get the address where the BUG() has occurred, kprobes can not
do single-step out-of-line that instruction. So prohibit
probing on such address.
Without this fix, if someone put a kprobe on WARN(), the
kernel will crash with invalid opcode
La 02.09.2019 10:39, Pavel Machek a scris:
Hi!
+ u64 p0, p1;
int ret;
atomic_set(&late_cpus_in, 0);
atomic_set(&late_cpus_out, 0);
+ p0 = rdtsc_ordered();
+
ret = stop_machine_cpuslocked(__reload_late, NULL, cpu_online_mask);
+
+ p1 = rdtsc_o
On Mon, Sep 02, 2019 at 11:48:59AM +1000, Michael Ellerman wrote:
> "Alastair D'Silva" writes:
> > On Wed, 2019-08-21 at 22:27 +0200, Christophe Leroy wrote:
> >> Can we be 100% sure that GCC won't add any code accessing some
> >> global data or stack while the Data MMU is OFF ?
> >
> > +mpe
> >
>
Commit 5aa068ea4082 ("printk: remove games with previous record flags")
abolished the practice of setting the log flag to 'c' for the first
continuation line and '+' for subsequent lines. Now all continuation
lines are flagged with 'c' and '+' is never used.
Update the 'dev-kmsg' documentation to
Supporting VMAP_STACK with KASAN_VMALLOC is straightforward:
- clear the shadow region of vmapped stacks when swapping them in
- tweak Kconfig to allow VMAP_STACK to be turned on with KASAN
Reviewed-by: Dmitry Vyukov
Signed-off-by: Daniel Axtens
---
arch/Kconfig | 9 +
kernel/fork.c
Test kasan vmalloc support by adding a new test to the module.
Signed-off-by: Daniel Axtens
--
v5: split out per Christophe Leroy
---
lib/test_kasan.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/lib/test_kasan.c b/lib/test_kasan.c
index 49cc4d570a40..328d33b
Currently, vmalloc space is backed by the early shadow page. This
means that kasan is incompatible with VMAP_STACK.
This series provides a mechanism to back vmalloc space with real,
dynamically allocated memory. I have only wired up x86, because that's
the only currently supported arch I can work
In the case where KASAN directly allocates memory to back vmalloc
space, don't map the early shadow page over it.
We prepopulate pgds/p4ds for the range that would otherwise be empty.
This is required to get it synced to hardware on boot, allowing the
lower levels of the page tables to be filled d
Hook into vmalloc and vmap, and dynamically allocate real shadow
memory to back the mappings.
Most mappings in vmalloc space are small, requiring less than a full
page of shadow space. Allocating a full shadow page per mapping would
therefore be wasteful. Furthermore, to ensure that different mapp
Provide the current number of vmalloc shadow pages in
/sys/kernel/debug/kasan_vmalloc/shadow_pages.
Signed-off-by: Daniel Axtens
---
Merging this is probably overkill, but I leave it to the discretion
of the broader community.
On v4 (no dynamic freeing), I saw the following approximate figures
From 69f508e27f8eb41215c782509766fbf95f5c2a05 Mon Sep 17 00:00:00 2001
From: YunFeng Ye
Date: Mon, 2 Sep 2019 15:19:57 +0800
Subject: [PATCH] genirq: modify the comment for irq_desc
commit 0c6f8a8b917a ("genirq: Remove compat code") deleted the @status
member of irq_desc, but forgot to update the
On Sat, 31 Aug 2019, Michael Kelley wrote:
> From: Maya Nakamura Sent: Friday, July 12, 2019
> 1:28 AM
> >
> > Define the ring buffer size as a constant expression because it should
> > not depend on the guest page size.
> >
> > Signed-off-by: Maya Nakamura
> > Reviewed-by: Michael Kelley
>
201 - 300 of 874 matches
Mail list logo
