On Fri, Apr 12, 2019 at 7:44 AM Johannes Weiner wrote:
>
> During !CONFIG_CGROUP reclaim, we expand the inactive list size if
> it's thrashing on the node that is about to be reclaimed. But when
> cgroups are enabled, we suddenly ignore the node scope and use the
> cgroup scope only. The result is
Hi,
On 19. 4. 15. 오후 11:54, Dmitry Osipenko wrote:
> There is no real benefit from doing so, hence let's drop that rate setting
> for consistency.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/devfreq/tegra-devfreq.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/devfre
Hello,
Does anyone have any commnets on this?
On Mon, Mar 25, 2019 at 4:15 +, Kazuhiro Kasai wrote:
> Add Milbeaut AXI DMA controller. This DMA controller has
> only capable of memory to memory transfer.
>
> Signed-off-by: Kazuhiro Kasai
> ---
> drivers/dma/Kconfig | 8 +
> driv
Hi,
patch6/7/8/9 are for handling of exception handling in probe() function.
Actually, I'm not sure that there are special reason to split out
the patches. I think that you can squash patch6/7/8/9 to only one patch.
Also, even if patch6/7/8/9 handle the exception handling in probe(),
the tegra_de
on non-preempt kernels for filesystems with large number of groups we
may take a long time (>50 ticks) initializing all the groups.
Signed-off-by: Khazhismel Kumykov
---
fs/ext4/mballoc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 8ef5f12bbee2
Convert Intel Many Integrated Core architecture docs to ReST.
The conversion is trivial: just add title and literal block
markups, and adjust some identation.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/mic/mic_overview.txt | 6 ++-
Documentation/mic/scif_overview.txt | 58
This small file seems to be an attempt to start documenting
backlight drivers.
It contains descriptions of the controls for the driver
with could sound as an somewhat user-faced description, but
it's main focus is to describe, instead, the data that should
be passed via platform data and some driv
The conversion is trivial: just adjust title markups.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/ptp/ptp.txt | 26 +-
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git a/Documentation/ptp/ptp.txt b/Documentation/ptp/ptp.txt
index 11e904ee073f..65c84
The API described at sysfs.txt is deprecated.
Still, as it is still part of the Kernel (and will likely be
there for some time, as we don't simply remove APIs). So,
it makes sense to keep it there.
The conversion of this file is trivial.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/g
Convert the various documents at the driver-model, preparing
them to be part of the driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-model/binding.txt| 20 +-
Documentation/driver-model/bus.txt| 69 ++--
Documentation/driver-model/class.txt
arly_memunmap' was here
#define TPM_MEMUNMAP(start, size) early_memunmap(start, size)
^~
include/linux/tpm_eventlog.h:203:4: note: in expansion of macro 'TPM_MEMUNMAP'
TPM_MEMUNMAP(mapping, mapping_size);
^~~~
Caused by com
On Tue, Apr 9, 2019 at 11:11 PM Andy Shevchenko
wrote:
>
> Intel Comet Lake has the same LPSS than Intel Cannon Lake.
> Add the new IDs to the list of supported devices.
>
> Signed-off-by: Andy Shevchenko
> ---
> drivers/mfd/intel-lpss-pci.c | 13 +
> 1 file changed, 13 insertions(+)
On some platforms like i.MX8QXP, the thermal driver needs a
real HW sensor ID from DT thermal zone, the HW sensor ID is
used to get temperature from SCU firmware, and the virtual
sensor ID starting from 0 to N is NOT used at all, this patch
adds new API thermal_zone_of_get_sensor_id() to provide th
NXP i.MX8QXP is an ARMv8 SoC with a Cortex-M4 core inside as
system controller, the system controller is in charge of system
power, clock and thermal sensors etc. management, Linux kernel
has to communicate with system controller via MU (message unit)
IPC to get temperature from thermal sensors, th
i.MX8QXP is an ARMv8 SoC which has a Cortex-M4 system controller
inside, the system controller is in charge of controlling power,
clock and thermal sensors etc..
This patch adds i.MX system controller thermal driver support,
Linux kernel has to communicate with system controller via MU
(message un
This patch enables CONFIG_IMX_SC_THERMAL as module.
Signed-off-by: Anson Huang
---
No change.
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 17daa97..fbe3be7 100644
--- a/arch/arm64/configs/de
Add i.MX8QXP CPU thermal zone support.
Signed-off-by: Anson Huang
---
Changes since V11:
- add cooling device for all secondary CPUs.
---
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 37 ++
1 file changed, 37 insertions(+)
diff --git a/arch/arm64/boot/dts/fre
On Mon, Apr 15, 2019 at 11:50 AM Sami Tolvanen wrote:
>
> With LD_DEAD_CODE_DATA_ELIMINATION, we compile the kernel with
> -fdata-sections, which also splits the .bss section. Use the
> common BSS_MAIN macro in the linker script to properly merge all
> the generated sections.
>
> Signed-off-by: Sa
Hi, Daniel
Best Regards!
Anson Huang
> -Original Message-
>
> On 10/04/2019 09:43, Anson Huang wrote:
> > i.MX8QXP is an ARMv8 SoC which has a Cortex-M4 system controller
> > inside, the system controller is in charge of controlling power, clock
> > and thermal sensors etc..
> >
> > This
Hi, Daniel
Best Regards!
Anson Huang
> -Original Message-
>
>
> On 10/04/2019 09:43, Anson Huang wrote:
> > Add i.MX8QXP CPU thermal zone support.
> >
> > Signed-off-by: Anson Huang
> > ---
> > Changes since V10:
> > - remove property "imx,sensor-resource-id" and put HW resource
Add PCI IDs for SPI on Comet Lake.
Signed-off-by: Evan Green
---
drivers/spi/spi-pxa2xx.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
index b6ddba833d021..493223e1d032d 100644
--- a/drivers/spi/spi-pxa2xx.c
+++ b/drivers/spi/spi-p
Describing better what the function does, what the arguments are meant for, and
what SQ stands for.
Signed-off-by: Marcos Paulo de Souza
---
Changes from v1:
* Change "SQ" to "only one hw_queue (SQ)" in the function signature
documentation (suggested by Chaitanya)
block/blk-mq.c | 17
On 15-04-19, 10:18, Pierre-Louis Bossart wrote:
> Standards such as the MIPI DisCo for SoundWire 1.0 specification
> assume the _ADR field is 64 bits.
>
> _ADR is defined as an "Integer" represented as 64 bits since ACPI 2.0
> released in 2002. The low levels already use _ADR as 64 bits, e.g. in
>
On Mon, Apr 15, 2019 at 11:20 AM Paul Moore wrote:
>
> On Mon, Apr 15, 2019 at 11:05 AM Oleg Nesterov wrote:
> > On 04/15, Paul Moore wrote:
> > >
> > > On Mon, Apr 15, 2019 at 9:43 AM Oleg Nesterov wrote:
> > > > Well, acct("/proc/self/attr/current") doesn't look like a good idea,
> > > > but
On Fri, Oct 12, 2018 at 9:45 AM Kees Cook wrote:
>
> On Fri, Oct 12, 2018 at 7:29 AM, Theodore Y. Ts'o wrote:
> > On Thu, Oct 11, 2018 at 03:54:21PM -0700, Kees Cook wrote:
> >> Right now rand_initialize() is run as an early_initcall(), but it only
> >> depends on timekeeping_init() (for mixing k
at 19:42, Hans de Goede wrote:
Hi,
On 15-04-19 13:36, hotwater...@tutanota.com wrote:
Sorry for the delay.
By applying this patch I get next results:
Five finger tap and two finger scroll issues disappear, but after
suspend touchpad dies. Restarting module doesn't help.
So bascally the sa
On Mon, Apr 15, 2019 at 11:44 AM Alexander Popov wrote:
>
> On 11.04.2019 21:01, Kees Cook wrote:
> > Right now kernel hardening options are scattered around various Kconfig
> > files. This can be a central place to collect these kinds of options
> > going forward. This is initially populated with
ome unrelated sparse warnings about missing syscalls)
Patch is against 5.1-rc4 (localversion-next is 20190415)
arch/arm/mach-mvebu/board-v7.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-mvebu/board-v7.c b/arch/arm/mach-mvebu/board-v7.c
index 0b10acd..df84cb6 100644
--- a
On Tue, 16 Apr 2019 at 00:15, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.169 release.
> There are 76 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Res
X27ADS=y)
(with some unrelated sparse warnings about unimplemented syscalls)
Patch is against 5.1-rc4 (localversion-next is 20190415)
arch/arm/mach-imx/mach-mx27ads.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach-imx/mach-mx27ads.c b/arch/arm/mach-imx/mach-mx27ads.c
index 6dd
Commit eab09532d400 ("binfmt_elf: use ELF_ET_DYN_BASE only for PIE"),
made changes in the rare case when the ELF loader was directly invoked
(e.g to set a non-inheritable LD_LIBRARY_PATH, testing new versions of
the loader), by moving into the mmap region to avoid both ET_EXEC and PIE
binaries. Thi
get_maintainer.pl only returns linux-kernel@vger.kernel.org for the
drivers/soc/ux500/ files - fix it by adding drivers/soc/ux500/ entry
Signed-off-by: Nicholas Mc Guire
Suggested-by: Ulf Hansson
---
Patch is aginst 5.1-rc4 (localversion-next is 20190415)
MAINTAINERS | 1 +
1 file changed, 1
On Tue, 16 Apr 2019 at 00:32, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.112 release.
> There are 69 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
Hi all,
After merging the chrome-platform tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from drivers/platform/chrome/wilco_ec/debugfs.c:11:
drivers/platform/chrome/wilco_ec/debugfs.c: In function 'fops_h1_gpio_open':
drivers/platform/chrome/wilco_ec/
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.core/stacktrace
head: ee23ee068fe24272f77ff014181286db32179754
commit: 6f6b2fc2fbf712e39df84edc62265273259f8aa1 [28/32] livepatch: Simplify
stack trace retrieval
config: s390-performance_defconfig (attached as .config)
comp
The MT7621 MIPS-based SOC contains an sdhci unit that is
much the same as the units supported by mtk-sd.c.
These patches enhance the driver so that I can use it on my MT7621
board (gnubee.org).
Some thoughts:
- I wonder if voltage-ranges should be a standard option, processed
by mmc_of_parse(
When using devicetree for configuration, interrupt trigger type
should be described in the dts file, not hard-coded in the C code.
The mtk-sd silicon in the mt7621 soc uses an active-high interrupt
and so cannot be used with the current code.
So remove the trigger and leave it to be set from devi
If the mtk-sd silicon is used in a context where there is no explicit
regulator, it is not currently possible to specify the voltage
ranges. This is true for the MT7621 MIPS Soc.
So add a called to mmc_of_parse_voltage() so that voltage-ranges can
be given.
Signed-off-by: NeilBrown
---
Documen
The mtk-sd silicon has integrated card-detect logic that is
enabled, at least, on the MT7621 as used in the GNUBEE NAS.
If the sdhci isn't marked non-removable and doesn't have a
cd-gpio configured, assume the internal cd logic should be used.
Signed-off-by: NeilBrown
---
drivers/mmc/host/mtk-s
mt7620 family MIPS SOCs contain the mtk-sd silicon.
Add support for this.
Signed-off-by: NeilBrown
# Conflicts:
# drivers/mmc/host/mtk-sd.c
---
Documentation/devicetree/bindings/mmc/mtk-sd.txt |1 +
drivers/mmc/host/mtk-sd.c| 12
2 files changed,
The mtk-sd silicon has integrated write-protect detection logic.
If the sdhci isn't marked no-write-protect and doesn't have a
ro-gpio configured, assume the internal wp logic should be used.
Signed-off-by: NeilBrown
---
drivers/mmc/host/mtk-sd.c | 30 +-
1 file ch
Hi Srinivas,
Thanks for the patch,
By default NVMEM_SYSFS should be set true, those whose don't want they
can disable the same.
If we go with disable option, there are chances of eeprom may break in
below case:
if (config->compat) {
rval = nvmem_sysfs_setup_compat(nvmem, con
On Wed, Apr 10, 2019 at 8:54 PM Thomas Gleixner wrote:
> On Tue, 9 Apr 2019, Daniel Drake wrote:
> > On Wed, Apr 3, 2019 at 7:21 PM Thomas Gleixner wrote:
> > > - Prevent the TSC calibration code from touching PIT/HPET. It
> > >should do that already when the TSC frequency ca
On Wed, Apr 10, 2019 at 11:50:49AM -0400, Joe Lawrence wrote:
> Hi folks,
>
> This is the third installment of the klp-convert tool for generating and
> processing livepatch symbols for livepatch module builds. For those
> following along at home, archive links to previous versions:
>
> RFC:
>
hi will and all:
>
> The following is schematic diagram of the program before and after the
> modification.
>
> Before:
> if (memstart_addr + linear_region_size < memblock_end_of_DRAM()) {} --(a)
> if (memory_limit != PHYS_ADDR_MAX) {} --(b)
> if (IS_ENABLED(CONFIG_BLK
w will break userspace that is assuming the default trigger is set.
> (setting a trigger should always be a userspace decision, rather than hard
> coded unless there is a clear one to one mapping - mind you we have this
> same problem if we have a fixed trigger, though in that case we
From: Jumin Li
Add USB DTS node to the mt8183 and mt8183-evb.
Signed-off-by: Jumin Li
Signed-off-by: Chunfeng Yun
---
this patch is based on v5.1-rc1 and these patches:
https://patchwork.kernel.org/patch/10856987/
https://patchwork.kernel.org/patch/10839021/
https://patchwork.kernel.org/patch/
On Thu, Apr 11, 2019 at 01:14:12AM +0200, Stefan Agner wrote:
> The common ARM architecture code provides a generic function to exit
> coherency called v7_exit_coherency_flush(). Replace the machine
> specific implementation using the generic function.
>
> Tested on a i.MX 6Dual by hotplugging the
On Mon, 15 Apr 2019 20:46:41 +0200
Vitor Soares wrote:
> Currently in case of mixed slow bus topologie and all i2c devices
> support FM+ speed, the i3c subsystem limite the SCL to FM speed.
"
Currently the I3C framework limits SCL frequency to FM speed when
dealing with a mixed slow bus, even if
On Fri, Apr 12, 2019 at 02:02:23PM +0800, Wen Yang wrote:
> The call to of_parse_phandle returns a node pointer with refcount
> incremented thus it must be explicitly decremented after the last
> usage.
>
> Detected by coccinelle with the following warnings:
> ./drivers/pinctrl/zte/pinctrl-zx.c:41
On 16.04.2019 01:24, Life is hard, and then you die wrote:
> Hi Andrzej,
>
> On Mon, Apr 15, 2019 at 10:58:09AM +0200, Andrzej Hajda wrote:
>> On 15.04.2019 10:12, Ronald Tschalär wrote:
>>> commit d6abe6df706c (drm/bridge: sil_sii8620: do not have a dependency
>>> of RC_CORE) changed the driver
Hi,
It looks good to me to drop the primary interrupt handler
but I have some comments. Please check it.
On 19. 4. 15. 오후 11:54, Dmitry Osipenko wrote:
> There is no real need in the primary interrupt handler, hence move
> everything to the secondary (threaded) handler. In a result locking
> is c
Hi Vitor,
On Mon, 15 Apr 2019 20:46:42 +0200
Vitor Soares wrote:
> The i3c bus spec define a bus configuration where the i2c devices
^defines I2C devices...
> doesn't have the 50ns filter yet they allow the SDR max speed.
^don't^ a 50ns fil
On Mon, 15 Apr 2019 21:31:50 +0200
Arnd Bergmann wrote:
> gpio-ep93xx.h, hardware.h, and platform.h are only used in
> arch/arm/mach-ep93xx, so we can move them one there and no
> longer expose them to device drivers.
>
> Signed-off-by: Arnd Bergmann
> ---
> arch/arm/mach-ep93xx/adssphere.c
+Przemek
On Mon, 15 Apr 2019 20:46:43 +0200
Vitor Soares wrote:
> This patch add limited bus mode support for DesignWare i3c master
>
> Signed-off-by: Vitor Soares
> Cc: Boris Brezillon
> Cc:
> ---
> drivers/i3c/master/dw-i3c-master.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
Typo in the subject: s/remap/regmap/
On Mon, 15 Apr 2019 21:19:39 +0200
Vitor Soares wrote:
> Add basic support for I3C bus.
> This is a simple implementation that only give support
> for Read and Write commands.
>
> Signed-off-by: Vitor Soares
> ---
> drivers/base/regmap/Kconfig | 6 ++
On Mon, 15 Apr 2019 21:19:40 +0200
Vitor Soares wrote:
> This helper return the i3c_device_id structure in order the client
> have access to the driver data.
>
> Signed-off-by: Vitor Soares
> ---
> drivers/i3c/device.c | 8
> include/linux/i3c/device.h | 1 +
> 2 files changed,
and next-20190415
Thank you,
Eric Jeong, Dialog Semiconductor Ltd.
Eric Jeong (3):
MAINTAINERS: slg51000 updates to the Dialog Semiconductor search
terms
Documentation: devicetree: regulator: add binding for slg51000
regulator: slg51000: add slg51000 regulator driver
.../devicetree
From: Eric Jeong
Add device tree binding information for slg51000 regulator driver.
Signed-off-by: Eric Jeong
---
This patch applies against linux-next and next-20190415
.../devicetree/bindings/regulator/slg51000.txt | 88
1 file changed, 88 insertions
From: Eric Jeong
This patch adds the slg51000 bindings doc and driver to the Dialog
Semiconductor support list.
Signed-off-by: Eric Jeong
---
MAINTAINERS |2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 002d564..9783eba 100644
--- a/MAINTAINERS
+++ b
applies against linux-next and next-20190415
drivers/regulator/Kconfig |9 +
drivers/regulator/Makefile |1 +
drivers/regulator/slg51000-regulator.c | 548
drivers/regulator/slg51000-regulator.h | 505
Hi Dmitry,
I already replied against patch6 about the exception handling
of tegra_devfreq_probe(). This patchset split out the patch
related to error handling for probe(). I think that you can
squash the patches regarding of exception handling for probe()
to one patch instead of split out the mult
On Mon, 15 Apr 2019 21:19:41 +0200
Vitor Soares wrote:
> For today the st_lsm6dsx driver support lsm6dso sensor only in
> spi and i2c mode.
>
> The lsm6dso is also i3c capable so lets give i3c support to it.
>
> Signed-off-by: Vitor Soares
> ---
> drivers/iio/imu/st_lsm6dsx/Kconfig |
Commit-ID: 6a03469a1edc94da52b65478f1e00837add869a3
Gitweb: https://git.kernel.org/tip/6a03469a1edc94da52b65478f1e00837add869a3
Author: Sami Tolvanen
AuthorDate: Mon, 15 Apr 2019 09:49:56 -0700
Committer: Ingo Molnar
CommitDate: Tue, 16 Apr 2019 08:20:55 +0200
x86/build/lto: Fix trunca
On 2019/4/15 16:53, Mao Wenan wrote:
> There is one warning exist while compiling
> drivers/pci/controller/dwc/pcie-hisi.c.
> make allmodconfig ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-
> make C=2 drivers/pci/controller/dwc/pcie-hisi.o ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu-
> drivers/pci
Hi Vitor,
On Mon, 15 Apr 2019 21:19:38 +0200
Vitor Soares wrote:
I like the very detailed description in your cover letter :P.
Anyway, glad to see I3C support added to regmap. Also happy to have a
new driver for an I3C device.
Thanks for working on that.
Boris
> Vitor Soares (3):
> remap: A
AVX-512 components use could cause core turbo frequency drop. So
it's useful to expose AVX-512 usage elapsed time as a heuristic hint
for the user space job scheduler to cluster the AVX-512 using tasks
together.
Tensorflow example:
$ while [ 1 ]; do cat /proc/tid/status | grep AVX; sleep 1; done
A
The architecture specific information of the running processes could
be useful to the userland. Add support to examine process architecture
specific information externally.
Signed-off-by: Aubrey Li
Cc: Peter Zijlstra
Cc: Andi Kleen
Cc: Tim Chen
Cc: Dave Hansen
Cc: Arjan van de Ven
Cc: Linux
Added AVX512_elapsed_ms in /proc//status. Report it
in Documentation/filesystems/proc.txt
Signed-off-by: Aubrey Li
Cc: Peter Zijlstra
Cc: Andi Kleen
Cc: Tim Chen
Cc: Dave Hansen
Cc: Arjan van de Ven
Cc: Linux API
Cc: Alexey Dobriyan
Cc: Andrew Morton
---
Documentation/filesystems/proc.tx
From: Yury Norov
Remove __bitmap_parselist helper and split the function to logical
parts.
Signed-off-by: Yury Norov
---
lib/bitmap.c | 255 ---
1 file changed, 142 insertions(+), 113 deletions(-)
diff --git a/lib/bitmap.c b/lib/bitmap.c
index c
From: Yury Norov
Add tests for non-number character, empty regions, integer overflow.
Signed-off-by: Yury Norov
Reviewed-by: Andy Shevchenko
---
lib/test_bitmap.c | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/lib/test_bitmap.c b/lib/test_bitmap.c
index
From: Yury Norov
Currently we parse user data byte after byte which leads to
overcomplification of parsing algorithm. The only user of
bitmap_parselist_user() is not performance-critical, and so we
can duplicate user data to kernel buffer and simply call
bitmap_parselist(). This rework lets us un
From: Yury Norov
test_bitmap_parselist currently uses get_cycles which is not
implemented on some platforms, so use ktime_get() instead.
Signed-off-by: Yury Norov
Reviewed-by: Andy Shevchenko
---
lib/test_bitmap.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/li
From: Yury Norov
Propagate existing bitmap_parselist() tests to bitmap_parselist_user().
Signed-off-by: Yury Norov
Reviewed-by: Andy Shevchenko
---
lib/test_bitmap.c | 46 --
1 file changed, 36 insertions(+), 10 deletions(-)
diff --git a/lib/test_b
bitmap_parselist has been evolved from a pretty simple idea for long and
now lacks for refactoring. It is not structured, has nested loops and a
set of opaque-named variables.
Things are more complicated because bitmap_parselist() is a part of user
interface, and its behavior should not change.
I
Hi, Sean:
On Sun, 2019-04-14 at 16:01 -0700, Sean Wang wrote:
> Hi, Light
>
> On Thu, Apr 11, 2019 at 8:15 PM Light Hsieh wrote:
> >
> > The orginal PINCTRL_MTK_PARIS/PINCTRL_MTK_MOORE need more effort for
> > specifying register bases when porting platform driver:
> > 1. Write mt_pinctrl_re
From: Chen-Yu Tsai
The VBUS current limit value macros have VBUS typed as VBUC, while
the bitmask macro is named correctly. Fix it.
Fixes: 69fb4dcada77 ("power: Add an axp20x-usb-power driver")
Signed-off-by: Chen-Yu Tsai
---
drivers/power/supply/axp20x_usb_power.c | 16
1 fil
From: Chen-Yu Tsai
This adds the "x-powers,axp813-usb-power-supply" to the list of
compatibles for AXP20X VBUS power supply driver.
Reviewed-by: Rob Herring
Signed-off-by: Chen-Yu Tsai
---
Changes since v2:
- Collected Rob's Reviewed-by
---
.../devicetree/bindings/power/supply/axp20x_usb_
From: Chen-Yu Tsai
Hi everyone,
This is v4 of my A83T USB power supply / OTG series. Hopefully this is
the last revision even though it's kind of late in the -rc cycle for
the patches to make the next release. Fingers crossed.
Changes since v3:
- Dropped patch for disabling current limit
-
From: YueHaibing
Syzkaller report this:
BUG: KASAN: use-after-free in __list_add_valid+0xd4/0xe0 lib/list_debug.c:26
Read of size 8 at addr 8881ef61ae20 by task syz-executor.0/5996
CPU: 1 PID: 5996 Comm: syz-executor.0 Tainted: G C5.0.0+ #5
Hardware name: QEMU Standard PC (i
On i.MX8MM, we are running Dual Linux OS, with 1st Linux using SD Card
as rootfs storage, 2nd Linux using eMMC as rootfs storage. We let the
the 1st linux configure power/clock for the 2nd Linux.
When the 2nd Linux is booting into rootfs stage, we let the 1st Linux
to destroy the 2nd linux, then r
On 4/15/2019 4:07 PM, Colin King wrote:
From: Colin Ian King
Fix spelling mistakes in rx stats text. I missed these from an earlier
round of fixing the same spelling mistake.
Signed-off-by: Colin Ian King
Reviewed-by: Mukesh Ojha
Cheers,
-Mukesh
---
drivers/net/wireless/intel/iwlegac
Hi all,
On Fri, 29 Mar 2019 13:39:14 +1100 Stephen Rothwell
wrote:
>
> After merging the akpm-current tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> lib/list_sort.c:17:36: warning: 'pure' attribute ignored [-Wattributes]
>struct list_head const *, struc
On Mon, 15 Apr 2019 at 03:49, Matheus Castello wrote:
>
> According datasheet max17040 has a pin for alert host for low SOC.
> This pin can be used as external interrupt, so we need to check for
> interrupts assigned for device and handle it.
>
> In hadler we are checking and storing fuel gauge re
On Mon, 15 Apr 2019 at 03:50, Matheus Castello wrote:
>
> For configure low level state of charge threshold alert signaled from
> max17040 we add "maxim,alert-soc-level" property.
>
> Signed-off-by: Matheus Castello
> ---
> .../power/supply/max17040_battery.txt | 24 +++
>
Add documentation to describe Xilinx ZynqMP fpga driver
bindings.
Signed-off-by: Nava kishore Manne
Reviewed-by: Rob Herring
Acked-by: Alan Tull
Acked-by: Moritz Fischer
---
Changes for v5:
-None.
.../bindings/fpga/xlnx,zynqmp-pcap-fpga.txt | 25 +++
1 file
Nava kishore Manne (3):
firmware: xilinx: Add fpga API's
dt-bindings: fpga: Add bindings for ZynqMP fpga driver
fpga manager: Adding FPGA Manager support for Xilinx zynqmp
.../bindings/fpga/xlnx,zynqmp-pcap-fpga.txt | 25 +++
drivers/firmware/xilinx/zynqmp.c | 45 +
dri
This Patch Adds fpga API's to support the Bitstream loading
by using firmware interface.
Signed-off-by: Nava kishore Manne
Reviewed-by: Moritz Fischer
---
Changes for v5:
-Modified API's doc as suggested by Moritz.
drivers/firmware/xilinx/zynqmp.c | 45 +
This patch adds FPGA Manager support for the Xilinx
ZynqMP chip.
Signed-off-by: Nava kishore Manne
Reviewed-by: Moritz Fischer
Acked-by: Alan Tull
---
Changes for v5:
-Removed hardcoded macro values and used BIT(x)
as suggested by Moritz.
drivers/fpga/Kconfig
* Elena Reshetova wrote:
> This is an example of produced assembly code for gcc x86_64:
>
> ...
> add_random_stack_offset();
> 0x810022e9 callq 0x81459570
> 0x810022ee movzbl %al,%eax
> 0x810022f1 add$0x16,%rax
> 0x810022f5 and$0x1f8,%eax
> 0
On Mon, 15 Apr 2019 at 03:51, Matheus Castello wrote:
>
> For configuration of fuel gauge alert for a low level state of charge
> interrupt we add a function to config level threshold and a device tree
> binding property to set it in flatned device tree node.
>
> Now we can use "maxim,alert-soc-le
On Mon, Apr 15, 2019 at 11:19 AM Christoph Hellwig wrote:
>
> On Sat, Apr 13, 2019 at 03:38:35PM +, Anup Patel wrote:
> > It's better to have all RISC-V spec related defines in one place
> > so this patch adds separate asm/encoding.h for such defines which
> > can be included in assembly as we
On Mon, 15 Apr 2019 at 03:48, Matheus Castello wrote:
>
> Notify core through power_supply_changed() in case of changes in state
> of charge. This is useful for user-space to efficiently update current
> battery level.
>
> Signed-off-by: Matheus Castello
> ---
> drivers/power/supply/max17040_bat
As JuHyung Park reported in mailing list:
https://sourceforge.net/p/linux-f2fs/mailman/message/36639787/
generic_make_request: Trying to write to read-only block-device loop0 (partno 0)
WARNING: CPU: 0 PID: 23437 at block/blk-core.c:2174
generic_make_request_checks+0x594/0x630
generic_make_req
Üdvözlöm!
2019 januárjától jelentősen átalakult mind a juttatások adózása, mind a piacon
elérhető juttatási termékek köre.
Amennyiben Önnek is fejtörést okoz, mivel pótolja a korábban használt Erzsébet
utalványt, ismerje meg kártyáinkat és utalványainkat, melyek az Ön cégének is
kíváló alter
On Sat, Apr 13, 2019 at 07:54:48AM +0200, Lukas Bulwahn wrote:
> Mimi Zohar used spaces instead of a tab when adding Jarkko Sakkinen as
> further maintainer to the KEYS-TRUSTED section entry.
>
> In fact, ./scripts/checkpatch.pl -f MAINTAINERS complains:
>
> WARNING: MAINTAINERS entries use one
On Saturday, April 04/13/19, 2019 at 21:30:26 +0530, Colin King wrote:
> From: Colin Ian King
>
> Currently if alloc_skb fails to allocate the skb a null skb is passed
> to t4_set_arp_err_handler and this ends up dereferencing the null skb.
> Avoid the null pointer dereference by checking for a n
On 2019-04-11 21:14, Alexandre Belloni wrote:
Readout the enabled state so it is possible to get the pre-userspace
handler working. Also, avoid disabling the watchdog to ensure it
continues
working and triggers if there is an issue later in the boot or if
userspace
fails to start.
Signed-off-
Hi all,
After merging the netfilter-next tree, today's linux-next build (powerpc
allyesconfig) failed like this:
ld: net/netfilter/nf_conntrack_netlink.o: in function `__crc_nf_ct_get_id':
(.rodata+0x0): multiple definition of `__crc_nf_ct_get_id';
net/netfilter/nf_conntrack_core.o:(.rodata+0x20
On 2019-04-11 16:12, Alexandre Belloni wrote:
While the UDA1380 is described in some lpc3250 device trees, there is
currently no real user of that codec. Anyway, if the codec needs a
clock,
it should take it explicitly.
lpc3250_machine_init is called for all the lpc32xx machines and some
are
301 - 400 of 1116 matches
Mail list logo
