Example:
mmc_csd: mmc0: struct: 0, cmdclass: 0x5b5, raw:
{0x400e0032,0x5b59,0x3b4b7f80,0xa404000}
Signed-off-by: Raul E Rangel
---
drivers/mmc/core/mmc.c | 4
drivers/mmc/core/sd.c | 2 ++
include/trace/events/mmc.h | 28
3 files changed, 34
On 4/15/19 10:46 AM, Thomas Gleixner wrote:
> Xose reported warnings when NX is disabled on the kernel command line.
Thank you for doing the dirty work.
>
> __early_set_fixmap() triggers:
>
> attempted to set unsupported pgprot:8163
> bits:
to clear it at all? Or should we really be locking the inode for
blockdevs after all? I'm not too familiar, but my gut says former
this reproducer is able to immediately crash machine running
linux-next-20190415:
#include
#include
#include
#include
#include
#include
#include
#include
On Mon, 15 Apr 2019 16:52:38 -0600
Raul E Rangel wrote:
> Example:
> sd_scr: mmc0: version: 2, spec3: 1, width: 5, cmds: 0, raw: {0x2b58000,0x0}
>
> Signed-off-by: Raul E Rangel
> ---
>
> drivers/mmc/core/sd.c | 4
> include/trace/events/mmc.h | 42
On Mon, 15 Apr 2019 16:52:39 -0600
Raul E Rangel wrote:
> Example:
> sd_ssr: mmc0: au: 8192, erase time: 0, erase offset: 0x0, raw:
> {0x0,0x300,0x1019000,0x1,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0}
>
> Signed-off-by: Raul E Rangel
> ---
>
> drivers/mmc/core/sd.c | 2
When we boot with the LED support (CONFIG_NEW_LEDS) disabled,
gpio_led_register_device() will return a NULL pointer and we try
to dereference it. Fix by checking also for a NULL pointer.
Fixes: 19a2668a8ae3 ("ARM: OMAP1: ams-delta: Provide GPIO lookup table for LED
device")
Signed-off-by: Aaro
> From: Peter Zijlstra
> Sent: Monday, April 15, 2019 5:21 AM
> To: Dexuan Cui
>
> On Fri, Apr 12, 2019 at 11:53:57PM +, Dexuan Cui wrote:
> > If smp_call_function_single() is calling the function for itself, it's safe
> > to run with irqs_disabled() == true.
> >
> > I hit the warning
syscall_get_error() is required to be implemented on all
architectures in addition to already implemented syscall_get_nr(),
syscall_get_arguments(), syscall_get_return_value(), and
syscall_get_arch() functions in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
syscall_get_* functions are required to be implemented on all
architectures in order to extend the generic ptrace API with
PTRACE_GET_SYSCALL_INFO request.
This adds remaining 2 syscall_get_* functions as documented in
asm-generic/syscall.h: syscall_get_error and syscall_get_return_value.
Cc:
All syscall_get_*() and syscall_set_*() functions must be defined
as static inline as on all other architectures, otherwise asm/syscall.h
cannot be included in more than one compilation unit.
This bug has to be fixed in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
syscall_get_error() is required to be implemented on all
architectures in addition to already implemented syscall_get_nr(),
syscall_get_arguments(), syscall_get_return_value(), and
syscall_get_arch() functions in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
From: Elvira Khabirova
PTRACE_GET_SYSCALL_INFO is a generic ptrace API that lets ptracer obtain
details of the syscall the tracee is blocked in.
There are two reasons for a special syscall-related ptrace request.
Firstly, with the current ptrace API there are cases when ptracer cannot
retrieve
syscall_get_error() is required to be implemented on this
architecture in addition to already implemented syscall_get_nr(),
syscall_get_arguments(), syscall_get_return_value(), and
syscall_get_arch() functions in order to extend the generic
ptrace API with PTRACE_GET_SYSCALL_INFO request.
Cc:
Check whether PTRACE_GET_SYSCALL_INFO semantics implemented in the kernel
matches userspace expectations.
Acked-by: Shuah Khan
Cc: Oleg Nesterov
Cc: Andy Lutomirski
Cc: Elvira Khabirova
Cc: Eugene Syromyatnikov
Cc: linux-kselft...@vger.kernel.org
Signed-off-by: Dmitry V. Levin
---
Notes:
This is the development kit board for the Librem 5. The current level of
support yields a working console and is able to boot userspace from the
Network or eMMC.
Additional subsystems that are active :
- Both USB ports
- SD card socket
- WiFi usdhc
- WWAN modem
- GNSS
- GPIO keys
- LEDs
- gyro
-
The Librem5 devkit is based on the imx8mq from NXP. This is a default
devicetree to boot the board to a command prompt.
Changes since v3:
Freshly sorted and pressed nodes.
Change the backlight to an interpolated scale.
Dropped i2c2.
Dropped devkit version number to match debian MR.
Changes
Add an entry for Purism, SPC
Signed-off-by: Angus Ainslie (Purism)
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index
On Mon, Apr 15, 2019 at 04:20:17PM -0700, Khazhismel Kumykov wrote:
> I was able to reproduce this by setting security.capability xattr on a
> blockdev file, then writing to it - when writing to the blockdev we
> never lock the inode, so when we clear the capability we hit this
> lockdep warning.
On Mon, Apr 15, 2019 at 2:26 PM Jonathan Kowalski wrote:
>
> On Mon, Apr 15, 2019 at 9:34 PM Andy Lutomirski wrote:
> > I would personally *love* it if distros started setting no_new_privs
> > for basically all processes. And pidfd actually gets us part of the
> > way toward a straightforward
stable-rc/linux-4.14.y boot: 107 boots: 1 failed, 96 passed with 9 offline, 1
untried/unknown (v4.14.111-70-g58023abef2c4)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.111-70-g58023abef2c4/
Full Build Summary:
On 4/12/19 1:47 AM, Michal Hocko wrote:
On Thu 11-04-19 11:56:50, Yang Shi wrote:
[...]
Design
==
Basically, the approach is aimed to spread data from DRAM (closest to local
CPU) down further to PMEM and disk (typically assume the lower tier storage
is slower, larger and cheaper than the
>>>Subject: Re: [PATCH] x86/hyper-v: implement EOI assist
>>>
>>>Vitaly Kuznetsov writes:
>>>
Hyper-V TLFS suggests an optimization to avoid imminent VMExit on EOI:
"The OS performs an EOI by atomically writing zero to the EOI Assist
field of the virtual VP assist page and checking
stable-rc/linux-4.19.y boot: 110 boots: 1 failed, 102 passed with 7 offline
(v4.19.34-102-ge4f859c2cd83)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.34-102-ge4f859c2cd83/
Full Build Summary:
On 4/16/2019 3:26 AM, Arnaldo Carvalho de Melo wrote:
Em Mon, Apr 15, 2019 at 08:09:09PM +0530, Ravi Bangoria escreveu:
On 4/12/19 7:29 PM, Jin Yao wrote:
diff --git a/tools/perf/Documentation/perf-stat.txt
b/tools/perf/Documentation/perf-stat.txt
index 39c05f8..1e312c2 100644
---
Kevin Hilman writes:
> Neil Armstrong writes:
>
>> Following [1], add regulators, bluetooth and ADC keys on :
>> - meson-g12a-x96-max
>> - meson-g12a-u200
>> - meson-g12a-sei510
>>
>> Dependencies :
>> - Patch 1, 2: None
>
> Queued for v5.2 (branch v5.2/dt64)
>
>> - Patch 3: SAR ADC node at [2]
Neil Armstrong writes:
> The register bitmask to power on/off the VPU memories was incorectly set
> to 0x2 instead of 0x3. While still working, let's use the recommended
> vendor value instead.
>
> Fixes: 75fcb5ca4b46 ("soc: amlogic: add Meson GX VPU Domains driver")
> Signed-off-by: Neil
stable-rc/linux-4.9.y boot: 92 boots: 0 failed, 83 passed with 9 offline
(v4.9.168-77-ga5905936a4b8)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.168-77-ga5905936a4b8/
Full Build Summary:
Neil Armstrong writes:
> Hi Kevin,
>
> Seems this patch is missing in
> https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git/log/?h=v5.2/dt64
>
Yup, I noticed it when applying the rest of the boards peripherals DT.
I've added it now.
Thanks,
Kevin
On Tue, Apr 16, 2019 at 07:23:42AM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> In commit
>
> 2e53582d158e ("crypto: mxc-scc - Remove broken driver")
>
> Fixes tag
>
> Fixes: d293b640ebd ("crypto: mxc-scc - add basic driver for the...")
>
> has these problem(s):
>
> - SHA1 should
Hi,
Thank you every much!
I found MSI in my system too and there are some errors found in bios log.
Replace the memorys can fix it.
L2GW_2680:/home/fsp/ycb # perf stat -C 1-11,14-25,29-39,42-52 --smi-cost
^C
Performance counter stats for 'CPU(s) 1-11,14-25,29-39,42-52':
SMI cycles% SMI#
Hi Marc,
sorry for ping you...
What's your suggestion for this patch? I look forward to your reply.
Thanks,
Hongbo.
On 4/8/2019 10:01 PM, Hongbo Yao wrote:
> Some definitions of Inner Cacheability attibutes need to be corrected.
>
> Fixes: 8c828a535e29f ("irqchip/gicv3-its: Restore all
ce_arr.array[] is always within the range [0, ce_arr.n-1].
However, the binary search code in __find_elem() uses ce_arr.n
as the maximum index, which could lead to an off-by-one
out-of-bound access when the element after the last is exactly
the one just got deleted, that is, 'min' returned to
cec_timer_fn() is a timer callback which reads ce_arr.array[]
and updates its decay values. Elements could be added to or
removed from this global array in parallel, although the array
itself will not grow or shrink. del_lru_elem_unlocked() uses
FULL_COUNT() as a key to find a right element to
Hi, PC
Thank you every much!
-Original Message-
From: Paul Clarke [mailto:p...@us.ibm.com]
Sent: 2019年4月15日 20:53
To: Linhaifeng ; linux-perf-us...@vger.kernel.org;
linux-kernel@vger.kernel.org
Subject: Re: perf tools:Is there any tools to found out the max latency by irq
or cpu idle
Hi,
I add one minor comment (KHZ -> hz).
On 19. 4. 15. 오후 11:54, Dmitry Osipenko wrote:
> The kHz to Hz is incorrectly converted in a few places in the code,
> this results in a wrong frequency being calculated because devfreq core
> uses OPP frequencies that are given in Hz to clamp the rate,
Hi,
On 19. 4. 15. 오후 11:54, Dmitry Osipenko wrote:
> The clk_set_min_rate() could fail and in this case clk_set_rate() sets
> rate to 0, which may drop EMC rate to minimum and make machine very
> difficult to use.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/devfreq/tegra-devfreq.c | 10
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
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
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 +
>
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
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
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
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
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
---
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
'TPM_MEMUNMAP'
TPM_MEMUNMAP(mapping, mapping_size);
^~~~
Caused by commit
05165bf3d231 ("tpm: Abstract crypto agile event size calculations")
and maybe
cdb75b359079 ("tpm: Reserve the TPM final events table")
I have used the tmpdd tree from next-20190415 fo
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
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
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,
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
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
---
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
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:
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..
> >
> >
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
+++
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 |
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
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
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
ted 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/arch/arm/
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.
>
>
(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 6dd7f57..cba6
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.
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.
>
>
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':
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)
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
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
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
---
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
---
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
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
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,
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
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
ming 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 have
> trig_readonly set so 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/
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
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
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:
>
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
Hello Martin and Miquel,
On 2019/4/12 6:00, Martin Blumenstingl wrote:
Use the recently introduced struct_size macro instead of open-coding
it's logic.
No functional changes.
Signed-off-by: Martin Blumenstingl
---
drivers/mtd/nand/raw/meson_nand.c | 3 +--
1 file changed, 1 insertion(+), 2
Fix an inverted result check for reusing unused kprobe correctly.
This has been introduced by commit 819319fc9346 ("kprobes: Return
error if we fail to reuse kprobe instead of BUG_ON()"), which
missed to handle the return value of kprobe_optready() as
error-value. In reality, the kprobe_optready()
On 2019/4/12 6:00, Martin Blumenstingl wrote:
Use the of_property_count_elems_of_size() helper instead of open-coding
it's logic. As a bonus this will now error out if the "reg" property
values use an incorrect size (anything other than sizeof(u32)).
Signed-off-by: Martin Blumenstingl
---
On 2019/4/12 6:00, Martin Blumenstingl wrote:
This simplifies the code because it gets rid of the casts to an
u8-pointer when passing "info_buf" from struct meson_nfc_nand_chip.
Also it gets rid of the cast of the u8 databuf pointer to a void
pointer.
The logic inside
On 2019/4/12 6:00, Martin Blumenstingl wrote:
Documentation/scheduler/completion.txt states:
Calling init_completion() on the same completion object twice is
most likely a bug as it re-initializes the queue to an empty queue and
enqueued tasks could get "lost" - use
Hi,
Any comments on this patch series?
Any more changes are needed or it looks good to be merged upstream?
- Yash
Hi all,
Today's linux-next merge of the vhost tree got a conflict in:
drivers/pci/of.c
between commit:
9cb30a71acd4 ("PCI: OF: Support "external-facing" property")
from the pci tree and commit:
e1c326663501 ("PCI: OF: Initialize dev->fwnode appropriately")
from the vhost tree.
I
If CONFIG_RANDOMIZE_KSTACK_OFFSET is selected,
the kernel stack offset is randomized upon each
entry to a system call after fixed location of pt_regs
struct.
This feature is based on the original idea from
the PaX's RANDKSTACK feature:
https://pax.grsecurity.net/docs/randkstack.txt
All the
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/pinctrl-rockchip.c:3221:2-8: ERROR: missing of_node_put;
acquired a node pointer with
On Thu, Apr 11, 2019 at 03:45:01PM +0800, Mao Han wrote:
> This patch add support for DWARF register mappings and libdw registers
> initialization, which is used by perf callchain analyzing when
> --call-graph=dwarf is given.
>
> CC: Peter Zijlstra
> CC: Ingo Molnar
> CC: Arnaldo Carvalho de
On Thu, 11 Apr 2019 11:08:31 -0700
Nick Desaulniers wrote:
> On Thu, Apr 11, 2019 at 1:52 AM Arnd Bergmann wrote:
> >
> > On Thu, Apr 11, 2019 at 12:14 AM 'Nick Desaulniers' via Clang Built
> > Linux wrote:
> > > On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote:
> > > >
> > > > The
On Sun, Apr 14, 2019 at 05:37:26PM +0200, Vincent Stehlé wrote:
> The `np->permission' structure is smaller than the `np' structure but
> sizeof(*np) worth of data is copied in there. Fix the size passed to
> copy_from_user() to avoid overrun.
>
> Fixes: 3d2ec9dcd5539d42 ("staging: Android: Add
1 - 100 of 1103 matches
Mail list logo