On Fri, Jul 12, 2019 at 02:04:08AM +0800, Zeng Tao wrote:
> The phy framework now allows runtime configurations, but only limited
> to mipi now, and it's not reasonable to introduce user specified
> configurations into the union phy_configure_opts structure. An simple
> way is to replace with a voi
On Wed, Jul 10, 2019 at 04:27:09PM -0400, Steven Rostedt wrote:
> But isn't it easier for them to just pull the quick fix in, if it is in
Steve, I've not yet seen a quick fix that actually fixes all the
problems.
Your initial one only fixes the IRQ tracing one, but leaves the context
tracking on
-EINVAL is not a valid return value for .of_map_mode, return
REGULATOR_MODE_INVALID instead.
Signed-off-by: Axel Lin
---
drivers/regulator/rk808-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/rk808-regulator.c
b/drivers/regulator/rk808-regulato
On Thu, Jul 11, 2019 at 3:17 AM Andrii Nakryiko
wrote:
>
> On Mon, Jul 8, 2019 at 3:42 PM Krzesimir Nowak wrote:
> >
> > The test case can now specify a custom length of the data member,
> > context data and its length, which will be passed to
> > bpf_prog_test_run_xattr. For backward compatilibi
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun7i-a20-bananapi.dts | 91 +-
1 file changed, 91 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20-bananapi.dts
b/arch/arm/boot/dts/sun7i-a20-bananapi.dts
index 4df921632f7a..cecc4eb26082 100644
--- a/arch/arm/boo
The older CSI drivers have camera capture interface different from the one
in the newer ones.
This IP is pretty simple. Some variants (one controller out of two
instances on some SoCs) have an ISP embedded, but there's no code that make
use of it, so we ignored that part for now.
Signed-off-by: M
On Thu, Jul 11, 2019 at 02:12:27PM +0200, Benjamin Gaignard wrote:
> Le jeu. 11 juil. 2019 à 13:51, William Breathitt Gray
> a écrit :
> >
> > On Tue, May 07, 2019 at 11:12:24AM +0200, Benjamin Gaignard wrote:
> > > Quadrature feature is now hosted on it own framework.
> > > Remove quadrature rela
The Allwinner A10 CMOS Sensor Interface is a camera capture interface also
used in later (A10s, A13, A20, R8 and GR8) SoCs.
On some SoCs, like the A10, there's multiple instances of that controller,
with one instance supporting more channels and having an ISP.
Reviewed-by: Rob Herring
Signed-off
On Wed, Jul 10, 2019 at 12:12 PM Amit Kucheria wrote:
>
> The network_latency and network_throughput flags for PM-QoS have not
> found much use in drivers or in userspace since they were introduced.
>
> Commit 4a733ef1bea7 ("mac80211: remove PM-QoS listener") removed the
> only user PM_QOS_NETWORK
The Makefile and Kconfig for the sun6i CSI driver are included in the main
Makefile / KConfig file. Since we're going to add a new CSI driver for an
older chip, and the Cedrus driver eventually, it makes more sense to put
those in our directory.
Signed-off-by: Maxime Ripard
---
drivers/media/pla
The CSI controller embedded in the A20 can be supported by our new driver.
Let's add it to our DT.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun7i-a20.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20.dtsi b/arch/arm/boot/dts/sun7i-a20.dts
Hi,
Here is a series introducing the support for the A10 (and SoCs of the same
generation) CMOS Sensor Interface (called CSI, not to be confused with
MIPI-CSI, which isn't support by that IP).
That interface is pretty straightforward, but the driver has a few issues
that I wanted to bring up:
Hi Arnd,
On 10/07/2019 14:01, Arnd Bergmann wrote:
> On 32-bit x86 when building with clang-9, the loop gets turned back into
> an inefficient division that causes a link error:
>
> kernel/time/vsyscall.o: In function `update_vsyscall':
> vsyscall.c:(.text+0xe3): undefined reference to `__udivdi3
Le jeu. 11 juil. 2019 à 13:51, William Breathitt Gray
a écrit :
>
> On Tue, May 07, 2019 at 11:12:24AM +0200, Benjamin Gaignard wrote:
> > Quadrature feature is now hosted on it own framework.
> > Remove quadrature related code from stm32-trigger driver to avoid
> > code duplication and simplify t
On Wed, Jul 10, 2019 at 04:27:09PM -0400, Steven Rostedt wrote:
[ added stable folks ]
On Sun, 7 Jul 2019 11:17:09 -0700
Linus Torvalds wrote:
On Sun, Jul 7, 2019 at 8:11 AM Andy Lutomirski wrote:
>
> FWIW, I'm leaning toward suggesting that we apply the trivial tracing
> fix and backport *
On Thu, Jul 11, 2019 at 2:03 AM Andrii Nakryiko
wrote:
>
> On Mon, Jul 8, 2019 at 3:43 PM Krzesimir Nowak wrote:
> >
> > The bpf_prog_test_run_xattr function gives more options to set up a
> > test run of a BPF program than the bpf_prog_test_run function.
> >
> > We will need this extra flexibili
On Thu, Jul 11, 2019 at 1:57 AM Andrii Nakryiko
wrote:
>
> On Mon, Jul 8, 2019 at 3:43 PM Krzesimir Nowak wrote:
> >
> > Commit 8184d44c9a57 ("selftests/bpf: skip verifier tests for
> > unsupported program types") added a check for an unsupported program
> > type. The function doing it changes er
On Thu, Jul 11, 2019 at 1:52 AM Andrii Nakryiko
wrote:
>
> On Mon, Jul 8, 2019 at 3:42 PM Krzesimir Nowak wrote:
> >
> > Save errno right after bpf_prog_test_run returns, so we later check
> > the error code actually set by bpf_prog_test_run, not by some libcap
> > function.
> >
> > Changes since
On 7/10/19 4:17 PM, Alexander Duyck wrote:
> On Wed, Jul 10, 2019 at 12:53 PM Nitesh Narayan Lal wrote:
>> Enables QEMU to perform madvise free on the memory range reported
>> by the vm.
>>
>> Signed-off-by: Nitesh Narayan Lal
>> ---
>> hw/virtio/trace-events| 1 +
>>
On Thu, Jul 11, 2019 at 01:17:17PM +0200, Dietmar Eggemann wrote:
> On 7/9/19 3:42 PM, Peter Zijlstra wrote:
> >>> That is, we only do those callbacks from:
> >>>
> >>> schedule_tail()
> >>> __schedule()
> >>> rt_mutex_setprio()
> >>> __sched_setscheduler()
> >>>
> >>> and the above looks
With commit b6664ba42f14 ("s390, kexec_file: drop arch_kexec_mem_walk()"),
we introduced the KEXEC_BUF_MEM_UNKNOWN macro. If kexec_buf.mem is set
to this value, kexec_locate_mem_hole() will try to allocate free memory.
While other arch(s) like s390 and x86_64 already use this macro to
initialize k
On 11/07/19 03:25, Eric Hankland wrote:
> - Add a VM ioctl that can control which events the guest can monitor.
... and finally:
- the patch whitespace is damaged
- the filter is leaked when the VM is destroyed
- kmalloc(GFP_KERNEL_ACCOUNT) is preferrable to vmalloc because it
accounts memory t
The one paravirt read_cr2() implementation (Xen) is actually quite
trivial and doesn't need to clobber anything other than the return
register. By making read_cr2() CALLEE_SAVE we avoid all the PUSH/POP
nonsense and allow more convenient use from assembly.
Reviewed-by: Juergen Gross
Signed-off-by
On Thu, Jul 11, 2019 at 08:00:49AM +, Bernard Metzler wrote:
> That listen will not sleep. The socket is just marked
> listening.
Eh? siw_listen_address() calls siw_cep_alloc() which does:
struct siw_cep *cep = kzalloc(sizeof(*cep), GFP_KERNEL);
Which is sleeping. Many other cases
By adding one more option to SAVE_ALL we can make use of it in
common_exception and simplify things. This saves duplication later
where page_fault will no longer use common_exception.
Reviewed-by: Steven Rostedt (VMware)
Reviewed-by: Andy Lutomirski
Signed-off-by: Peter Zijlstra (Intel)
---
ar
Since INT3/#BP no longer runs on an IST, this workaround is no longer
required.
Tested by running lockdep+ftrace as described in the initial commit:
5963e317b1e9 ("ftrace/x86: Do not change stacks in DEBUG when calling
lockdep")
Reviewed-by: Steven Rostedt (VMware)
Signed-off-by: Peter Zijls
Hi,
Here's the latest (and hopefully final) set of tracing vs CR2 patches.
They are basically the same as v2, with only minor edits and tags collected
from the last review.
Please consider.
Commit 2700fefdb2d9 ("x86_64: Add gap to int3 to allow for call
emulation") forgot to update the comment, do so now.
Acked-by: Andy Lutomirski
Reviewed-by: Steven Rostedt (VMware)
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/entry/entry_64.S | 17 +++--
1 file changed, 11 i
Despire the current efforts to read CR2 before tracing happens there
still exist a number of possible holes:
idtentry page_fault do_page_fault has_error_code=1
call error_entry
TRACE_IRQS_OFF
call trace_hardirqs_off*
#PF // modifies CR2
CA
The bind/unbind_guest_msi() callbacks check the domain
is NESTED and redirect to the dma-iommu implementation.
Signed-off-by: Eric Auger
---
v6 -> v7:
- remove device handle argument
---
drivers/iommu/arm-smmu-v3.c | 43 +
1 file changed, 43 insertions(+)
d
In nested mode we enforce the rule that all devices belonging
to the same iommu_domain share the same msi_domain.
Indeed if there were several physical MSI doorbells being used
within a single iommu_domain, it becomes really difficult to
resolve the nested stage mapping translating into the correc
There's a bunch of duplication in idtentry, namely the
.Lfrom_usermode_switch_stack is a paranoid=0 copy of the normal flow.
Make this explicit by creating a idtentry_part helper macro.
Acked-by: Andy Lutomirski
Reviewed-by: Steven Rostedt (VMware)
Signed-off-by: Peter Zijlstra (Intel)
---
ar
When a stage 1 related fault event is read from the event queue,
let's propagate it to potential external fault listeners, ie. users
who registered a fault handler.
Signed-off-by: Eric Auger
---
v8 -> v9:
- adapt to the removal of IOMMU_FAULT_UNRECOV_PERM_VALID:
only look at IOMMU_FAULT_UNRECO
On Tue, May 07, 2019 at 11:12:24AM +0200, Benjamin Gaignard wrote:
> Quadrature feature is now hosted on it own framework.
> Remove quadrature related code from stm32-trigger driver to avoid
> code duplication and simplify the ABI.
>
> Signed-off-by: Benjamin Gaignard
What is the status of this
On 7/10/19 4:45 PM, Dave Hansen wrote:
> On 7/10/19 12:51 PM, Nitesh Narayan Lal wrote:
>> +struct zone_free_area {
>> +unsigned long *bitmap;
>> +unsigned long base_pfn;
>> +unsigned long end_pfn;
>> +atomic_t free_pages;
>> +unsigned long nbits;
>> +} free_area[MAX_NR_ZONES]
It's more straightforward to use for statement here.
Signed-off-by: Axel Lin
---
drivers/regulator/da9062-regulator.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/regulator/da9062-regulator.c
b/drivers/regulator/da9062-regulator.c
index 2ffc64622451..5ea8d58d2
Hi,
When booting 5.2.0 on my Dell XPS13 9343, I'm seeing various messages
and traces related to the DesignWare DMA Controller / Intel SST loader.
They seem to differ across different boots:
Boot #1:
jul 08 17:40:05 sylvesterg kernel: sst-acpi INT3438:00: DesignWare DMA
Controller, 8 channel
On Thu, Jul 11, 2019 at 12:06 AM Saravana Kannan wrote:
>
> On Wed, Jul 10, 2019 at 3:19 AM Rafael J. Wysocki wrote:
> >
> > From: Rafael J. Wysocki
> >
> > If device_link_add() is called for a consumer/supplier pair with an
> > existing device link between them and the existing link's type is
>
On 7/10/19 4:19 PM, Dave Hansen wrote:
> On 7/10/19 12:51 PM, Nitesh Narayan Lal wrote:
>> This patch series proposes an efficient mechanism for reporting free memory
>> from a guest to its hypervisor. It especially enables guests with no page
>> cache
>> (e.g., nvdimm, virtio-pmem) or with smal
On Thu, Jul 11, 2019 at 1:45 AM Andrii Nakryiko
wrote:
>
> On Mon, Jul 8, 2019 at 3:42 PM Krzesimir Nowak wrote:
> >
> > This prints a message when the error is about program type being not
> > supported by the test runner or because of permissions problem. This
> > is to see if the program we ex
The "ti,lp87565" compatible string is still in of_lp87565_match_table,
but current code will return -EINVAL because lp87565->dev_type is unknown.
This was working in earlier kernel versions, so fix it.
Fixes: 7ee63bd74750 ("regulator: lp87565: Add 4-phase lp87561 regulator
support")
Signed-off-by
On Tue, Jul 09, 2019 at 02:59:42PM +0200, Fabien Lahoudere wrote:
> From: Gwendal Grignou
>
> EC returns a counter when there is an event on camera vsync.
> This patch comes from chromeos kernel 4.4
>
> Signed-off-by: Gwendal Grignou
> Signed-off-by: Fabien Lahoudere
>
> CROS EC sync sensor w
On Thu, Jul 11, 2019 at 12:34:27PM +0200, Thomas Gleixner wrote:
> On Thu, 11 Jul 2019, Will Deacon wrote:
> > On Wed, Jul 10, 2019 at 03:01:19PM +0100, Vincenzo Frascino wrote:
> > > Prior to the introduction of Unified vDSO support and compat layer for
> > > vDSO on arm64, AT_SYSINFO_EHDR was not
On 7/10/19 7:40 PM, Alexander Duyck wrote:
> On Wed, Jul 10, 2019 at 12:52 PM Nitesh Narayan Lal wrote:
>
> The results up here were redundant with what is below so I am just
> dropping them. I would suggest only including one set of results in
> any future cover page as it is confusing to dupli
On 11/07/19 03:25, Eric Hankland wrote:
>
> +/* for KVM_CAP_PMU_EVENT_FILTER */
> +struct kvm_pmu_event_filter {
> + __u32 type;
> + __u32 nevents;
> + __u64 events[0];
> +};
> +
> +#define KVM_PMU_EVENT_WHITELIST 0
> +#define KVM_PMU_EVENT_BLACKLIST 1
> +
"type" is a bit vague,
The base value in do_div() called by hpet_time_div() is truncated from
unsigned long to uint32_t, resulting in a divide-by-zero exception.
UBSAN: Undefined behaviour in ../drivers/char/hpet.c:572:2
division by zero
CPU: 1 PID: 23682 Comm: syz-executor.3 Not tainted 4.4.184.x86_64+ #4
Hardware name
On 7/9/19 3:42 PM, Peter Zijlstra wrote:
> On Tue, Jul 09, 2019 at 03:24:36PM +0200, luca abeni wrote:
>> Hi Peter,
>>
>> On Mon, 8 Jul 2019 15:55:36 +0200
>> Peter Zijlstra wrote:
>>
>>> On Mon, May 06, 2019 at 06:48:33AM +0200, Luca Abeni wrote:
@@ -1223,8 +1250,17 @@ static void update_cur
On 7/11/19 4:49 AM, Cornelia Huck wrote:
> On Wed, 10 Jul 2019 15:53:03 -0400
> Nitesh Narayan Lal wrote:
>
>
> $SUBJECT: s/baloon/balloon/
>
>> Enables QEMU to perform madvise free on the memory range reported
>> by the vm.
> [No comments on the actual functionality; just some stuff I noticed.]
-Original Message-
From: Rob Herring
Sent: 2019年7月11日 4:26
To: Leo Li
Cc: Biwen Li ; Alessandro Zummo ;
Alexandre Belloni ; open list:REAL TIME CLOCK
(RTC) SUBSYSTEM ; lkml
; Xiaobo Xie ; Jiafei Pan
; Ran Wang
Subject: [EXT] Re: [v2,2/2] Documentation: dt: binding: rtc: add binding
- Remove 'sdm845' from names, and use 'plat' instead.
- Move SCT_ENTRY macro to header file.
- Create a new config structure to asssign to of-match-data.
Signed-off-by: Vivek Gautam
---
drivers/soc/qcom/llcc-plat.c | 77 --
include/linux/soc/qcom/llcc-qc
To avoid adding files for each future supported SoCs rename
the file to a generic name - llcc-plat, so that llcc configuration
tables for other SoCs can be added in the same driver.
Signed-off-by: Vivek Gautam
---
drivers/soc/qcom/Kconfig| 10 +-
drivers/soc/qcom/
Hi Alistair,
On 10/07/2019 23:27, Alistair Francis wrote:
On Thu, Feb 28, 2019 at 2:42 PM Robin Murphy wrote:
On 2019-02-28 10:33 pm, Alistair Francis wrote:
This reverts commit 6778be4e520959659b27a441c06a84c9cb009085.
Reverting the commit fixes these error messages and an non-functioning
From: Vitor Soares
Date: Thu, Jul 11, 2019 at 11:12:34
> Hi Lorenzo,
>
> From: Lorenzo Bianconi
> Date: Wed, Jul 10, 2019 at 20:44:05
>
> > > For today the st_lsm6dsx driver support LSM6DSO and LSM6DSR sensor only in
> > > spi and i2c mode.
> > >
> > > The LSM6DSO and LSM6DSR are also i3c cap
From: Shengjiu Wang
There is chip errata ERR008000, the reference doc is
(https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf),
The issue is "While using ESAI transmit or receive and
an underrun/overrun happens, channel swap may occur.
The only recovery mechanism is to reset the ESAI."
This issue e
From: Shengjiu Wang
Extract the operation to be functions, to improve the
readability.
In this patch, fsl_esai_hw_init, fsl_esai_register_restore,
fsl_esai_trigger_start and fsl_esai_trigger_stop are
extracted.
Signed-off-by: Shengjiu Wang
Acked-by: Nicolin Chen
---
sound/soc/fsl/fsl_esai.c
From: Shengjiu Wang
recover the channel swap after xrun
Shengjiu Wang (2):
ASoC: fsl_esai: Wrap some operations to be functions
ASoC: fsl_esai: recover the channel swap after xrun
sound/soc/fsl/fsl_esai.c | 266 ---
1 file changed, 193 insertions(+), 73
Like the ThinkPad T560 case, now we can use RMI on T580 to have a more
responsive touchpad.
Signed-off-by: Kai-Heng Feng
---
drivers/input/mouse/synaptics.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
index b8ec301025b7..e
On Wed, Jul 10, 2019 at 05:34:07PM +0200, Frederic Weisbecker wrote:
> On Wed, Jul 10, 2019 at 04:04:21PM +0200, Peter Zijlstra wrote:
> > On Tue, Jul 09, 2019 at 03:48:19PM +0200, Frederic Weisbecker wrote:
> > >
> > > Syzbot has found a breakpoint overcommit issue:
> > >
> > > https://lore.kern
On Thu, 11 Jul 2019, Will Deacon wrote:
> On Wed, Jul 10, 2019 at 03:01:19PM +0100, Vincenzo Frascino wrote:
> > Prior to the introduction of Unified vDSO support and compat layer for
> > vDSO on arm64, AT_SYSINFO_EHDR was not defined for compat tasks.
> > In the current implementation, AT_SYSINFO
Enable NXP i2c controller to boot with ACPI
Signed-off-by: Meenakshi Aggarwal
Signed-off-by: Udit Kumar
Signed-off-by: Chuanhua Han
---
drivers/acpi/acpi_apd.c | 6 ++
drivers/i2c/busses/i2c-imx.c | 15 +++
2 files changed, 21 insertions(+)
diff --git a/drivers/acpi/acpi
On Tue, Jun 25, 2019 at 10:54 AM Oleksandr Suvorov
wrote:
>
> To enable "zero cross detect" for ADC/HP, change
> HP_ZCD_EN/ADC_ZCD_EN bits only instead of writing the whole
> CHIP_ANA_CTRL register.
>
> Signed-off-by: Oleksandr Suvorov
> ---
>
> sound/soc/codecs/sgtl5000.c | 6 +++---
> 1 file c
On Tue, Jun 25, 2019 at 10:55 AM Oleksandr Suvorov
wrote:
>
> Prepare to use SND_SOC_DAPM_PRE_POST_PMU definition to
> reduce coming code size and make it more readable.
>
> Signed-off-by: Oleksandr Suvorov
> ---
>
> include/sound/soc-dapm.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --g
On Thu, Jul 11, 2019 at 09:27:30AM +, Philippe CORNU wrote:
> Hi Daniel,
>
>
> On 7/10/19 5:27 PM, Daniel Vetter wrote:
> > On Fri, Jul 05, 2019 at 12:41:03PM +, Philippe CORNU wrote:
> >> Hi Olivier,
> >> and many thanks for your patch.
> >> Good to have the audio graph card support, loo
Hi Oleksandr,
On Tue, Jun 25, 2019 at 10:56 AM Oleksandr Suvorov
wrote:
>
> If VDDA != VDDIO and any of them is greater than 3.1V, charge pump
> source can be assigned automatically.
minor: Could also you please add a reference link to the commit message,
where this behavior is defined?
>
> Sign
On Tue, Jun 25, 2019 at 10:49 AM Oleksandr Suvorov
wrote:
>
> This control mute/unmute the ADC input of SGTL5000
> using its CHIP_ANA_CTRL register.
>
> Signed-off-by: Oleksandr Suvorov
> ---
>
> sound/soc/codecs/sgtl5000.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/sound/soc/codec
On Tue, Jun 25, 2019 at 10:55 AM Oleksandr Suvorov
wrote:
>
> SGTL5000_SMALL_POP is a bit mask, not a value. Usage of
> correct definition makes device probing code more clear.
>
> Signed-off-by: Oleksandr Suvorov
> ---
>
> sound/soc/codecs/sgtl5000.c | 2 +-
> sound/soc/codecs/sgtl5000.h | 2 +-
On Thu, Jul 11, 2019 at 12:19 PM Oliver Graute wrote:
>
> On 11/07/19, Abel Vesa wrote:
> > On 19-06-19 09:39:52, Oliver Graute wrote:
> > > From: Oliver Graute
> > >
> > > added header defines for imx8qm clock
> > >
> > > Signed-off-by: Oliver Graute
> >
> > Again, this seems to be taken from s
Hi Lorenzo,
From: Lorenzo Bianconi
Date: Wed, Jul 10, 2019 at 20:44:05
> > For today the st_lsm6dsx driver support LSM6DSO and LSM6DSR sensor only in
> > spi and i2c mode.
> >
> > The LSM6DSO and LSM6DSR are also i3c capable so lets give i3c support to
> > them.
>
> Hi Vitor,
>
> just few com
On Wed, 2019-07-10 at 21:24 +0300, Andrey Ryabinin wrote:
>
> On 7/9/19 5:53 AM, Walter Wu wrote:
> > On Mon, 2019-07-08 at 19:33 +0300, Andrey Ryabinin wrote:
> >>
> >> On 7/5/19 4:34 PM, Dmitry Vyukov wrote:
> >>> On Mon, Jul 1, 2019 at 11:56 AM Walter Wu
> >>> wrote:
>
> >>>
> >>> Sorry for
The phy framework now allows runtime configurations, but only limited
to mipi now, and it's not reasonable to introduce user specified
configurations into the union phy_configure_opts structure. An simple
way is to replace with a void *.
We have already got some phy drivers which introduce private
On 07/05/2019 11:00 AM, Anshuman Khandual wrote:
> Architectures like parisc enable CONFIG_KROBES without having a definition
> for kprobe_fault_handler() which results in a build failure. Arch needs to
> provide kprobe_fault_handler() as it is platform specific and cannot have
> a generic worki
Santosh Sivaraj's on July 9, 2019 10:15 pm:
> If we take a UE on one of the instructions with a fixup entry, set nip
> to continue execution at the fixup entry. Stop processing the event
> further or print it.
So... what happens if we take a machine check while we happen to be
executing some other
Hi Phil,
On Thu, Jul 11, 2019 at 11:24 AM Phil Reid wrote:
> On 10/07/2019 18:21, Geert Uytterhoeven wrote:
> > On Wed, Jul 10, 2019 at 4:00 AM Phil Reid wrote:
> >> On 6/07/2019 00:05, Geert Uytterhoeven wrote:
> >>> GPIO controllers are exported to userspace using /dev/gpiochip*
> >>> characte
Santosh Sivaraj's on July 9, 2019 10:15 pm:
> From: Balbir Singh
>
> The pmem infrastructure uses memcpy_mcsafe in the pmem layer so as to
> convert machine check exceptions into a return value on failure in case
> a machine check exception is encountered during the memcpy. The return
> value is
Santosh Sivaraj's on July 9, 2019 10:15 pm:
> In real mode, the search_exception tables cannot be called because
> it also searches the module exception tables if entry is not found
> in the kernel exception tables.
This is a patch for generic kernel code, it may not go through
powerpc tree and so
Hi all,
Please do not add v5.4 material to your linux-next included branches
until after v5.3-rc1 has been released.
Changes since 20190710:
The block tree gained build failures due to an interaction with the
f2fs and xfs trees for which I applied merge fix patches.
Non-merge commits (relative
On Wed, Jul 10, 2019 at 09:15:49PM +0200, Sebastian Andrzej Siewior wrote:
> On 2019-07-10 17:50:54 [+0100], Will Deacon wrote:
> > On Wed, Jul 03, 2019 at 11:21:26AM +0200, Sebastian Andrzej Siewior wrote:
> > > An uninitialized/ zeroed mutex will go unnoticed because there is no
> > > check for i
On Wed, Jul 10, 2019 at 03:01:19PM +0100, Vincenzo Frascino wrote:
> Prior to the introduction of Unified vDSO support and compat layer for
> vDSO on arm64, AT_SYSINFO_EHDR was not defined for compat tasks.
> In the current implementation, AT_SYSINFO_EHDR is defined even if the
> compat vdso layer
Hi,
On Tue, Jul 09, 2019 at 10:14:24AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Fri, 28 Jun 2019 13:55:11 +1000 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the battery tree got a conflict in:
> >
> > Documentation/power/power_supply_class.txt
> >
> > between commit
Santosh Sivaraj's on July 9, 2019 10:15 pm:
> From: Balbir Singh
>
> The current code would fail on huge pages addresses, since the shift
> would be incorrect. Use the correct page shift value returned by
> __find_linux_pte() to get the correct pfn. The code is more generic
> and can handle both
From: Paolo Pisati
Signed-off-by: Paolo Pisati
---
tools/testing/selftests/bpf/verifier/array_access.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/bpf/verifier/array_access.c
b/tools/testing/selftests/bpf/verifier/array_access.c
index bcb83196e45
From: Paolo Pisati
After applying patch 0001, all checksum implementations i could test (x86-64,
arm64 and
arm), now agree on the return value.
Patch 0002 fix the expected return value for test #13: i did the calculation
manually,
and it correspond.
Unfortunately, after applying patch 0001, o
From: Paolo Pisati
With this change, bpf_csum_diff behave homogeneously among different
checksum calculation code / csum_partial() (tested on x86-64, arm64 and
arm).
Signed-off-by: Paolo Pisati
---
net/core/filter.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/core/f
On 7/8/2019 11:30 AM, Viresh Kumar wrote:
The cpufreq drivers don't need to do runtime PM operations on the
virtual devices returned by dev_pm_domain_attach_by_name() and so the
virtual devices weren't shared with the callers of
dev_pm_opp_attach_genpd() earlier.
But the IO device drivers woul
On Wed, Jul 10, 2019 at 04:37:41PM -0700, Xing, Cedric wrote:
> On 7/10/2019 4:15 PM, Jarkko Sakkinen wrote:
> > On Thu, Jul 11, 2019 at 01:46:28AM +0300, Jarkko Sakkinen wrote:
> > > On Wed, Jul 10, 2019 at 11:08:37AM -0700, Xing, Cedric wrote:
> > > > > With these conclusions I think the current
On Wed, Jul 10, 2019 at 03:54:20PM -0700, Xing, Cedric wrote:
> On 7/10/2019 3:46 PM, Jarkko Sakkinen wrote:
> > On Wed, Jul 10, 2019 at 11:08:37AM -0700, Xing, Cedric wrote:
> > > > With these conclusions I think the current vDSO API is sufficient for
> > > > Linux.
> > >
> > > The new vDSO API i
> In my experience, when you start looking at these of_node_put things,
> all sorts of strange things appear...
How much will this situation influence the achievement of further improvements
also for your software?
Regards,
Markus
On Thu, Jul 11, 2019 at 10:12:35AM +0300, Shenhar, Talel wrote:
>
> On 7/10/2019 7:45 PM, Jonathan Chocron wrote:
> > Document Amazon's Annapurna Labs PCIe host bridge.
>
> That is the way! (best to keep same wordings (Amazon's)
Guys,
as a heads-up, the original posting, for whatever reason, di
From: Paolo Pisati
After applying patch 0001, all checksum implementations i could test (x86-64,
arm64 and
arm), now agree on the return value.
Patch 0002 fix the expected return value for test #13: i did the calculation
manually,
and it correspond.
Unfortunately, after applying patch 0001, o
From: Paolo Pisati
Signed-off-by: Paolo Pisati
---
tools/testing/selftests/bpf/verifier/array_access.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/bpf/verifier/array_access.c
b/tools/testing/selftests/bpf/verifier/array_access.c
index bcb83196e45
From: Paolo Pisati
With this change, bpf_csum_diff behave homogeneously among different
checksum calculation code / csum_partial() (tested on x86-64, arm64 and
arm).
Signed-off-by: Paolo Pisati
---
net/core/filter.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/core/f
On 11/07/2019 04:13, Dmitry Osipenko wrote:
> Remove the old drivers to replace them cleanly with a new one later on.
>
> Signed-off-by: Dmitry Osipenko
> ---
> arch/arm/mach-tegra/Makefile | 13 --
> arch/arm/mach-tegra/cpuidle-tegra114.c | 89 ---
> arch/arm/mach-tegra/cp
On 10/07/2019 18:21, Geert Uytterhoeven wrote:
Hi Phil,
On Wed, Jul 10, 2019 at 4:00 AM Phil Reid wrote:
On 6/07/2019 00:05, Geert Uytterhoeven wrote:
GPIO controllers are exported to userspace using /dev/gpiochip*
character devices. Access control to these devices is provided by
standard UN
Greetings to you and your family.
My name is Mr. Kone Compaore, the director general with the bank,
Africa Develop bank (ADB) Ouagadougou, Burkina Faso, in West Africa. I
am contacting you to seek our honesty and sincere cooperation in
confidential manner to transfer the sum of 10.5 (Ten million f
On 11/07/19, Abel Vesa wrote:
> On 19-06-19 09:39:52, Oliver Graute wrote:
> > From: Oliver Graute
> >
> > added header defines for imx8qm clock
> >
> > Signed-off-by: Oliver Graute
>
> Again, this seems to be taken from some vendor tree, so please keep the
> original author.
yes the header d
The Xilinx MIPI CSI-2 Rx Subsystem soft IP is used to capture images
from MIPI CSI-2 camera sensors and output AXI4-Stream video data ready
for image processing. Please refer to PG232 for details.
The CSI2 Rx controller filters out all packets except for the packets
with data type fixed in hardwar
+++ Zhiqiang Liu [11/07/19 14:03 +0800]:
On 2019/7/10 0:10, Jessica Yu wrote:
+++ Zhiqiang Liu [03/07/19 10:09 +0800]:
From: Zhiqiang Liu V2:
- remove incorrect Fixes tag
- fix error handling of sysfs_create_link as suggested by Jessica Yu
Signed-off-by: Zhiqiang Liu
Suggested-by: Jessica Y
Add bindings documentation for Xilinx MIPI CSI-2 Rx Subsystem.
The Xilinx MIPI CSI-2 Rx Subsystem consists of a CSI-2 Rx controller, a
DPHY in Rx mode, an optional I2C controller and a Video Format Bridge.
Signed-off-by: Vishal Sagar
Reviewed-by: Hyun Kwon
Reviewed-by: Rob Herring
Reviewed-by:
Xilinx MIPI CSI-2 Receiver Subsystem
The Xilinx MIPI CSI-2 Receiver Subsystem Soft IP consists of a DPHY which
gets the data, an optional I2C, a CSI-2 Receiver which parses the data and
converts it into AXIS data.
This stream output maybe connected to a Xilinx
Hi Sakari,
Thanks for reviewing.
> -Original Message-
> From: Sakari Ailus [mailto:sakari.ai...@iki.fi]
> Sent: Tuesday, June 18, 2019 8:50 PM
> To: Vishal Sagar
> Cc: Hyun Kwon ; laurent.pinch...@ideasonboard.com;
> mche...@kernel.org; robh...@kernel.org; mark.rutl...@arm.com; Michal
>
501 - 600 of 646 matches
Mail list logo
