On Wed, Feb 27, 2019 at 10:31:48AM +0200, Oded Gabbay wrote:
> On Wed, Feb 27, 2019 at 9:05 AM Yue Haibing wrote:
> >
> > From: YueHaibing
> >
> > Fixes the following sparse warnings:
> >
> > drivers/misc/habanalabs/goya/goya.c:1233:5: warning: symbol
> > 'goya_init_cpu_queues' was not declared.
On 26/02/2019 17:10, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
The AP interruptions are assigned on a queue basis and
the GISA structure is handled on a VM basis, so that
we need to add a structure we can retrieve from both side
holding the information we need to handle PQAP/A
On 19-02-26 13:34:52, Leonard Crestez wrote:
> On Tue, 2019-02-26 at 10:53 +, Abel Vesa wrote:
> > Add generic i.MX8 SoC driver along with the i.MX8MQ SoC specific code.
> > For now, only i.MX8MQ revision B1 is supported. For any other, i.MX8MQ
> > revision it will print 'unknown'.
> >
> > +
On Tue 2019-02-26 17:26:57, John Ogness wrote:
> On 2019-02-26, Petr Mladek wrote:
> > The warning about dropped messages gets lost when the current
> > message is above console_loglevel and suppressed.
>
> Here you are reporting a bug. (More on this below.)
Yes.
> > The suppressed messages all
On 21. 02. 19 12:03, Michal Simek wrote:
> On 21. 02. 19 11:24, Paul Kocialkowski wrote:
>> Hi,
>>
>> On Wed, 2019-02-20 at 07:58 +0100, Michal Simek wrote:
>>> Hi,
>>>
>>> On 19. 02. 19 18:25, Andrew Lunn wrote:
> Thanks for the suggestion! So I had a closer look at that driver to try
> an
On (02/27/19 09:12), John Ogness wrote:
> >>
> >> My only objection to this is that the "messages dropped" only comes if a
> >> non-supressed message comes. So information about dropped information
> >> may never get printed unless some task prints something non-supressed.
> >>
> >> Imagine a sit
On Tue, 26 Feb 2019 at 21:25, Nicolin Chen wrote:
>
> This reverts commit d222e42e88168fd67e6d131984b86477af1fc256.
>
> The original change breaks omap dss:
> omapdss_dispc 58001000.dispc:
> dispc_errata_i734_wa_init: dma_alloc_writecombine failed
>
> Let's revert it first and then fin
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
This patch enables CONFIG_IMX_SC_THERMAL as module.
Signed-off-by: Anson Huang
---
No changes.
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 2d9c390..52d503e 100644
--- a/arch/arm64/configs/d
Add i.MX8QXP CPU thermal zone support.
Signed-off-by: Anson Huang
---
Changes since V9:
- change #thermal-sensor-cells value in to 1, since there are other
thermal sensors inside system controller, it is just because there
are still
some issue, so system controller do
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
Best Regards!
Anson Huang
> -Original Message-
> From: Aisheng Dong
> Sent: 2019年2月26日 20:01
> To: Anson Huang ; Eduardo Valentin
>
> Cc: robh...@kernel.org; mark.rutl...@arm.com; shawn...@kernel.org;
> s.ha...@pengutronix.de; ker...@pengutronix.de; feste...@gmail.com;
> catalin.mari...
Üdvözlöm!
Bár 2019 januárjától szinte minden béren kívüli juttatás jövedelemként fog
adózni, a vállalatok több mint 55%-a meg kívánja tartani a dolgozói juttatások
nettó összegét.
Juttatási kártyáink szinte az összes jelenleg használt béren kívüli juttatást
lefedik, korlátlan felhasználással
From: Andy Shevchenko
Sometimes the user needs to split each entry on the mapped scatter list
due to DMA length constrains. This helper returns a number of entities
assuming that each of them is not bigger than supplied maximum length.
Signed-off-by: Andy Shevchenko
Signed-off-by: Alexandru Ard
Andrew Morton writes:
> [patch 1/4]: OK. I guess. Was this worth consuming our last PF_ flag?
That was done based on request from Andrea and it also helps in avoiding
allocating pages from CMA region where we know we are anyway going to
migrate them out. So yes, this helps.
> [patch 2/4]: un
Hello,
> From: Julia Lawall, Sent: Wednesday, February 27, 2019 5:25 PM
>
> On Wed, 27 Feb 2019, Yoshihiro Shimoda wrote:
>
> > This patch fixes memory leak at error paths of the probe function.
> > In for_each_child_of_node, if the loop returns, the driver should
> > call of_put_node() before r
On 2019-02-27, Petr Mladek wrote:
>> Imagine a situation where I am expecting a message to come, but don't
>> see it because it was dropped. But if no more non-supressed messages
>> come, I see neither the expected message nor the dropped message.
>
> Good point! There is a simple fix for this. We
On Tue 2019-02-26 16:22:01, John Ogness wrote:
> On 2019-02-26, Petr Mladek wrote:
> >> When new consoles register, they currently print how many messages
> >> they have missed. However, many (or all) of those messages may still
> >> be in the ring buffer. Add functionality to print as much of the
Hi Andrew, Paul,
On Wed, Feb 27, 2019 at 2:15 PM Michal Simek wrote:
>
> On 21. 02. 19 12:03, Michal Simek wrote:
> > On 21. 02. 19 11:24, Paul Kocialkowski wrote:
> >> Hi,
> >>
> >> On Wed, 2019-02-20 at 07:58 +0100, Michal Simek wrote:
> >>> Hi,
> >>>
> >>> On 19. 02. 19 18:25, Andrew Lunn wrot
On 27/02/2019 08:00, Bjorn Andersson wrote:
> SDM845 sports two PCIe controller/phy pairs; one GEN2 and one GEN3. Add
> the nodes for the GEN2 pair.
>
> Signed-off-by: Bjorn Andersson
> ---
>
> Changes since v1:
> - "reg" is spelled without a 't'
>
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 103
On Tue, Feb 26, 2019 at 09:29:40AM -0800, Guenter Roeck wrote:
> On Mon, Feb 25, 2019 at 10:09:33PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.20.13 release.
> > There are 183 patches in this series, all will be posted as a response
> > to this one.
On Mon, 25 Feb 2019 at 11:49, Ludovic BARRE wrote:
>
> hi Russell & Ulf
>
> On 2/21/19 3:03 PM, Russell King - ARM Linux admin wrote:
> > On Thu, Feb 21, 2019 at 02:38:36PM +0100, Ludovic BARRE wrote:
> >> hi Russell & Ulf
> >>
> >> On 2/21/19 11:30 AM, Russell King - ARM Linux admin wrote:
> >>>
On Wed, Feb 27, 2019 at 10:06 AM Marc Gonzalez wrote:
>
> On 27/02/2019 08:00, Bjorn Andersson wrote:
>
> > SDM845 sports two PCIe controller/phy pairs; one GEN2 and one GEN3. Add
> > the nodes for the GEN2 pair.
> >
> > Signed-off-by: Bjorn Andersson
> > ---
> >
> > Changes since v1:
> > - "reg"
On Wed, 27 Feb 2019 09:09:09 +0100
Pierre Morel wrote:
> On 26/02/2019 16:47, Tony Krowiak wrote:
> > On 2/26/19 6:47 AM, Pierre Morel wrote:
> >> On 25/02/2019 19:36, Tony Krowiak wrote:
> >>> On 2/22/19 10:29 AM, Pierre Morel wrote:
> We prepare the interception of the PQAP/AQIC inst
On Sun, Feb 24, 2019 at 09:04:57AM +0100, Gerhard Wiesinger wrote:
> Hello,
>
> I've 3 Banana Pi R1, one running with self compiled kernel
> 4.7.4-200.BPiR1.fc24.armv7hl and old Fedora 25 which is VERY STABLE, the 2
> others are running with Fedora 29 latest, kernel 4.20.10-200.fc29.armv7hl. I
> t
On Tue, Feb 26, 2019 at 03:41:07PM +0100, Greg Kroah-Hartman wrote:
> The dev_links_info structure has 4 bytes of padding at the end of it
> when embedded in struct device (which is the only place it lives). To
> help reduce the size of struct device pack this structure so we can take
> advantage
On Tue, Feb 26, 2019 at 12:58:12PM +0530, Jagan Teki wrote:
> Enable SUN6I SPI controller for Allwinner ARM64 SoC's.
>
> This would helpful to setup spi flash, for another booting source.
> mark it as static since it require during boot.
>
> Signed-off-by: Jagan Teki
Queued for 5.2, thanks
Max
On Tue, Feb 26, 2019 at 7:58 PM Mike Rapoport wrote:
>
> On Sun, Feb 24, 2019 at 08:34:05PM +0800, Pingfan Liu wrote:
> > There are numa machines with memory-less node. When allocating memory for
> > the memory-less node, memblock allocator falls back to 'Node 0' without
> > fully
> > utilizing t
On Tue, Feb 26, 2019 at 04:15:25PM +0200, Priit Laes wrote:
> From: Priit Laes
>
> Make sure that A20 Olimex Lime2 pin bank regulators are
> properly represented.
>
> While pin banks A, B and F are connected to 3.3V static
> regulator, pin banks E and G tied with LDO3 and LDO4 regulators
> with
When I ran Syzkaller testsuite, I got the following call trace.
UBSAN: Undefined behaviour in kernel/time/timekeeping.c:801:8
signed integer overflow:
500152103386 + 9223372036854775807 cannot be represented in type 'l
On 26/02/2019 23:44, Brian Norris wrote:
> Hi,
>
> On Tue, Feb 26, 2019 at 05:14:00PM +, Marc Zyngier wrote:
>> On 26/02/2019 16:21, Ard Biesheuvel wrote:
>>> On Mon, 25 Feb 2019 at 15:53, Marc Zyngier wrote:
It outlines one thing: If you have to interpret per-device PCI
properties
On 26/02/2019 07:59, Bjorn Andersson wrote:
> qcom_qmp_phy_init() is extended to support the additional register
> writes needed in PCS MISC and the appropriate sequences and resources
> are defined for SDM845.
>
> Signed-off-by: Bjorn Andersson
> ---
> .../devicetree/bindings/phy/qcom-qmp-phy.
On Tue, Feb 26, 2019 at 08:11:07PM +0800, Jin Yao wrote:
SNIP
> + .ordered_events = true,
> + .ordering_requires_timestamps = true,
> + },
> };
>
> static struct perf_evsel *evsel_match(struct perf_evsel *evsel,
> @@ -771,19 +788,136 @@ static void data__free(struc
On Tue, Feb 26, 2019 at 08:11:07PM +0800, Jin Yao wrote:
SNIP
> + abstime_tmp = abstime_ostr;
>
> data__for_each_file(i, d) {
> - d->session = perf_session__new(&d->data, false, &tool);
> + d->session = perf_session__new(&d->data, false, &pdiff.tool);
>
On 26/02/2019 19:14, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
Let's do this when assigning a A
On Wed, Feb 27, 2019 at 10:23:18AM +0100, Johan Hovold wrote:
> On Tue, Feb 26, 2019 at 03:41:07PM +0100, Greg Kroah-Hartman wrote:
> > The dev_links_info structure has 4 bytes of padding at the end of it
> > when embedded in struct device (which is the only place it lives). To
> > help reduce the
On 10/9/18 11:55 AM, Lee Jones wrote:
> On Thu, 27 Sep 2018, Amelie Delaunay wrote:
>
>> STMicroelectronics Multi-Function eXpander (STMFX) is a slave controller
>> using I2C for communication with the main MCU. Main features are:
>> - 16 fast GPIOs individually configurable in input/output
>> - 8
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
> We need to associate the ap_vfio_queue, which will hold the
> per queue information for interrupt with a matrix mediated device
> which hold the configuration and the way to the CRYCB.
>
> Let's do this when assigning a APID or a APQI to t
In POWER9, OCC(On-Chip-Controller) provides for hard and soft system
powercapping range. The hard powercap range is guaranteed while soft
powercap may or may not be asserted due to various power-thermal
reasons based on system configuration and workloads. This patch adds
a sysfs file to export the
This patch adds documentation of device tree bindings for the
STMicroelectronics Multi-Function eXpander (STMFX) MFD core.
Signed-off-by: Amelie Delaunay
Reviewed-by: Linus Walleij
Acked-for-MFD-by: Lee Jones
---
Documentation/devicetree/bindings/mfd/stmfx.txt | 28 +
1
This series adds support for STMicroelectronics Multi-Function eXpander
(STMFX), used on some STM32 discovery and evaluation boards.
STMFX is an STM32L152 slave controller whose firmware embeds the following
features:
- I/O expander (16 GPIOs + 8 extra if the other features are not enabled),
- res
This patch adds pinctrl/GPIO driver for STMicroelectronics
Multi-Function eXpander (STMFX) GPIO expander.
STMFX is an I2C slave controller, offering up to 24 GPIOs.
The driver relies on generic pin config interface to configure the GPIOs.
Signed-off-by: Amelie Delaunay
---
drivers/pinctrl/Kconfi
The joystick (B1) on stm32mp157c-ev1 uses gpios on STMFX gpio expander.
These gpios need a pin configuration (push-pull and bias-pull-down),
described under stmfx_pinctrl node.
Signed-off-by: Amelie Delaunay
---
arch/arm/boot/dts/stm32mp157c-ev1.dts | 44 +++
1 fi
Orange (LD2) and blue (LD4) leds on stm32746g-eval are connected on
STMFX gpio expander, offset 17 and 19.
Signed-off-by: Amelie Delaunay
Acked-by: Linus Walleij
---
arch/arm/boot/dts/stm32746g-eval.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/stm32746g-eval.d
This patch adds support for STMicroelectronics Multi-Function eXpander
(STMFX) on stm32mp157c-ev1. It is connected on i2c2.
Signed-off-by: Amelie Delaunay
---
arch/arm/boot/dts/stm32mp157c-ev1.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c
This patch adds documentation of device tree bindings for the
STMicroelectronics Multi-Function eXpander (STMFX) GPIO expander.
Signed-off-by: Amelie Delaunay
Reviewed-by: Linus Walleij
Reviewed-by: Rob Herring
---
.../devicetree/bindings/pinctrl/pinctrl-stmfx.txt | 116 +
The joystick (B3) on stm32746g-eval uses gpios on STMFX gpio expander.
These gpios need a pin configuration (push-pull and bias-pull-up),
described under stmfx_pinctrl node.
Signed-off-by: Amelie Delaunay
Acked-by: Linus Walleij
---
arch/arm/boot/dts/stm32746g-eval.dts | 43
This patch adds support for STMicroelectronics Multi-Function eXpander
(STMFX) on stm32746g-eval. It is connected on i2c1.
Signed-off-by: Amelie Delaunay
Acked-by: Linus Walleij
---
arch/arm/boot/dts/stm32746g-eval.dts | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/
STMicroelectronics Multi-Function eXpander (STMFX) is a slave controller
using I2C for communication with the main MCU. Main features are:
- 16 fast GPIOs individually configurable in input/output
- 8 alternate GPIOs individually configurable in input/output when other
STMFX functions are not used
On Mon, Feb 25, 2019 at 08:14:55PM +0100, Hans de Goede wrote:
> Hi,
>
> On 25-02-19 16:48, Heikki Krogerus wrote:
> > On Fri, Feb 22, 2019 at 05:31:32PM +0100, Hans de Goede wrote:
> > > Hi,
> > >
> > > On 2/19/19 12:59 PM, Heikki Krogerus wrote:
> > > > Hi guys,
> > > >
> > > > The software no
there is a similar helper in net/netfilter/nf_tables_api.c,
this maybe become a common request someday.
and avoid to call div_64 at some condition
Signed-off-by: Li RongQing
---
include/linux/jiffies.h | 1 +
kernel/time/time.c | 10 ++
2 files changed, 11 insertions(+)
diff --gi
I am an engineer in the software team at SUNIX Inc.,maintain SUNIX
Multi-I/O Board Device driver,we plan to submit our drivers to the
kernel,therefore,i want to modify 8250's files for resolve
driver conflict issue.
---
parport/parport_pc.c | 17 +---
parport/parport_serial.c | 179
On Wed, Feb 27, 2019 at 10:31:04AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Feb 27, 2019 at 10:23:18AM +0100, Johan Hovold wrote:
> > On Tue, Feb 26, 2019 at 03:41:07PM +0100, Greg Kroah-Hartman wrote:
> > > The dev_links_info structure has 4 bytes of padding at the end of it
> > > when embedded
On Tue, 26 Feb 2019 at 16:10, Avri Altman wrote:
>
> SD spec v5.1 adds discard support. The flows and commands matches those
> in eMMC, Which leaves to set the appropriate discard arg in CMD38 if
> DISCARD_SUPPORT (b313) is set in the SD_STATUS register.
>
> We set this arg on card init: not in mm
Hi,
On 26/02/19 6:36 PM, Ming Lei wrote:
> On Tue, Feb 26, 2019 at 05:04:40PM +0530, Faiz Abbas wrote:
>> Hi,
>>
>> On 26/02/19 3:36 PM, Ming Lei wrote:
>>> On Tue, Feb 26, 2019 at 2:47 PM Faiz Abbas wrote:
Hi Ming Lei,
On 26/02/19 7:11 AM, Ming Lei wrote:
> On Mon, Feb 25
On Fri, 22 Feb 2019 16:29:57 +0100
Pierre Morel wrote:
> To be able to use the VFIO interface to facilitate the
> mediated device memory pining/unpining we need to register
s/pining/pinning/ (unless it's pining for the fjords :)
> a notifier for IOMMU.
>
> Signed-off-by: Pierre Morel
> ---
>
For platforms, which use a PHYS_OFFSET != 0, symbol _end also
contains that offset. So when calling memblock_reserve() for
reserving kernel the size argument needs to be adjusted.
Fixes: bcec54bf3118 ("mips: switch to NO_BOOTMEM")
Acked-by: Mike Rapoport
Signed-off-by: Thomas Bogendoerfer
---
a
On Mon, 25 Feb 2019 at 22:22, Stephen Rothwell wrote:
>
> Hi Ulf,
>
> After merging the mmc-fixes tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/mmc/host/tmio_mmc_core.c: In function 'tmio_mmc_start_data':
> drivers/mmc/host/tmio_mmc_core.c:706:34: error: 'SZ_
On Wed, 27 Feb 2019 08:32:43 +0200
Mike Rapoport wrote:
> The changelog mentions initrd, but the patch changes only the kernel
> reservation. Can you please update the changelog to match the code?
sure, changed and sent.
Thomas.
--
SUSE Linux GmbH
GF: Felix Imendörffer, Jane Smithard, Graham
On Wed, Feb 27, 2019 at 10:51 AM Alexandru Ardelean
wrote:
>
> From: Andy Shevchenko
>
> Sometimes the user needs to split each entry on the mapped scatter list
> due to DMA length constrains. This helper returns a number of entities
> assuming that each of them is not bigger than supplied maximu
On Tue 2019-02-12 15:29:58, John Ogness wrote:
> Implement a non-sleeping NMI-safe write_atomic console function in
> order to support emergency printk messages.
It uses console_atomic_lock() added in 18th patch. That one uses
prb_lock() added by 2nd patch.
Now, prb_lock() allows recursion on the
+Cc Vinod
On Wed, Feb 27, 2019 at 11:45 AM Andy Shevchenko
wrote:
>
> On Wed, Feb 27, 2019 at 10:51 AM Alexandru Ardelean
> wrote:
> >
> > From: Andy Shevchenko
> >
> > Sometimes the user needs to split each entry on the mapped scatter list
> > due to DMA length constrains. This helper returns
On 26/02/19 11:46 PM, Sergei Shtylyov wrote:
> On 02/19/2019 09:36 AM, Vignesh R (by way of Boris Brezillon
> ) wrote:
>
>> Cypress HyperBus is Low Signal Count, High Performance Double Data Rate Bus
>> interface between a host system master and one or more slave interfaces.
>> HyperBus is use
On 2019-02-12 18:14:02 [+0100], Frederic Weisbecker wrote:
> --- /dev/null
> +++ b/include/linux/softirq_vector.h
> @@ -0,0 +1,10 @@
could you please add a spdx header/identifier here?
> +SOFTIRQ_VECTOR(HI)
> +SOFTIRQ_VECTOR(TIMER)
> +SOFTIRQ_VECTOR(NET_TX)
> +SOFTIRQ_VECTOR(NET_RX)
> +SOFTIRQ_VEC
On 26/02/2019 19:23, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
We register the AP PQAP instruction hook during the open
of the mediated device. And unregister it on release.
In the AP PQAP instruction hook, if we receive a demand to
enable IRQs,
- we retrieve the vfio_ap_queu
On Wed, Feb 27, 2019 at 10:40:21AM +0100, Johan Hovold wrote:
> On Wed, Feb 27, 2019 at 10:31:04AM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Feb 27, 2019 at 10:23:18AM +0100, Johan Hovold wrote:
> > > On Tue, Feb 26, 2019 at 03:41:07PM +0100, Greg Kroah-Hartman wrote:
> > > > The dev_links_info
On Wed, Feb 27, 2019 at 12:50 AM Louis Taylor wrote:
>
> When building with -Wformat, clang warns:
>
> drivers/hid/hid-quirks.c:1075:27: warning: format specifies type
> 'unsigned short' but the argument has type '__u32' (aka 'unsigned int')
> [-Wformat]
> bl_entry->driver_data,
On Tue, Feb 26, 2019 at 4:17 PM Theodore Y. Ts'o wrote:
>
> TL;DR: This doesn't appear to be ext4 specific, and seems to involve
> an unholy combination of the perf_event_open(2) and sendfile(2) system
> calls.
>
> On Mon, Feb 25, 2019 at 10:50:05PM -0800, syzbot wrote:
> > syzbot found the follow
On 26/02/2019 19:27, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
When the device is remove, we must make sure to
clear the interruption and reset the AP device.
We also need to clear the CRYCB of the guest.
Signed-off-by: Pierre Morel
---
drivers/s390/crypto/vfio_ap_drv.c
On Wed, 27 Feb 2019 15:22:19 +0530
Vignesh Raghavendra wrote:
> On 26/02/19 11:46 PM, Sergei Shtylyov wrote:
> > On 02/19/2019 09:36 AM, Vignesh R (by way of Boris Brezillon
> > ) wrote:
> >
> >> Cypress HyperBus is Low Signal Count, High Performance Double Data Rate Bus
> >> interface betwee
+ Lorenzo
Hi Brian,
On 26/02/2019 23:28, Brian Norris wrote:
> + others
>
> Hi Marc,
>
> Thanks for the series. I have a few bits of history to add to this, and
> some comments.
>
> On Sun, Feb 24, 2019 at 02:04:22PM +, Marc Zyngier wrote:
>> For quite some time, I wondered why the PCI mwi
Hi Ezequiel,
On Fri, Feb 22, 2019 at 01:59:33PM -0300, Ezequiel Garcia wrote:
> On Fri, 2019-02-22 at 16:46 +0900, Tomasz Figa wrote:
> > > diff --git a/include/uapi/linux/videodev2.h
> > > b/include/uapi/linux/videodev2.h
> > > index 9a920f071ff9..6443ae53597f 100644
> > > --- a/include/uapi/lin
On 2019-02-27, Petr Mladek wrote:
> I mean that your patch does the reply on a very hidden location.
Right. I understand that and I agree.
> Regarding the per-console kthread. It would make sense if
> we stop handling all consoles synchronously. For example,
> when we push messages to fast conso
Commit 5ad7346b4ae2 ("cpufreq: kryo: Add module remove and exit") made
it possible to build the kyro cpufreq driver as a module, but it failed
to release all the resources, i.e. OPP tables, when the module is
unloaded.
This patch fixes it by releasing the OPP tables, by calling
dev_pm_opp_put_supp
I am an engineer in the software team at SUNIX Inc.,
maintain SUNIX Multi-I/O Board Device driver,we plan to submit drivers to
the kernel,therefore,i want to modify file for resolve driver conflict issue.
---
tty/serial/8250/8250_pci.c | 163 -
1 file changed, 1
i.MX7ULP has a MMDC module to control DDR, it reuses
i.MX6Q's MMDC module, add support for it.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx7ulp.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/imx7ulp.dtsi b/arch/arm/boot/dts/imx7ulp.dtsi
index fca6e50..fc
Freescale MMDC (Multi Mode DDR Controller) driver is supported
since i.MX6Q, but not yet documented, this patch adds binding
doc for MMDC module driver.
Signed-off-by: Anson Huang
---
.../bindings/memory-controllers/fsl/mmdc.txt | 27 ++
1 file changed, 27 insertions(+)
I am an engineer in the software team at SUNIX Inc.,maintain SUNIX
Multi-I/O Board Device driver,we plan to submit our drivers to the
kernel,therefore,i want to modify files for resolve
driver conflict issue.
---
parport/parport_pc.c | 17 +---
parport/parport_serial.c | 179 ---
On 27/02/19 3:29 PM, Boris Brezillon wrote:
> On Wed, 27 Feb 2019 15:22:19 +0530
> Vignesh Raghavendra wrote:
>
>> On 26/02/19 11:46 PM, Sergei Shtylyov wrote:
>>> On 02/19/2019 09:36 AM, Vignesh R (by way of Boris Brezillon
>>> ) wrote:
>>>
>
[...]
+ */
+
+struct hb_device
This patch fixes the below sparse warnings by either making the functions
static or by adding a declaration in the relevant header file.
In addition, the patch removes goya_mmap completely as it doesn't add any
additional benefit.
Fixes the following sparse warnings:
drivers/misc/habanalabs/haba
On 27/02/2019 10:13, Cornelia Huck wrote:
On Wed, 27 Feb 2019 09:09:09 +0100
Pierre Morel wrote:
On 26/02/2019 16:47, Tony Krowiak wrote:
On 2/26/19 6:47 AM, Pierre Morel wrote:
On 25/02/2019 19:36, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
We prepare the interception of
Hi all,
This is a collection of x86/percpu changes that I had pending and got reminded
of by Linus' comment yesterday about __this_cpu_xchg().
This tidies up the x86/percpu primitives and fixes a bunch of 'fallout'.
Built and boot tested with CONFIG_DEBUG_PREEMPT=y.
---
arch/x86/include/asm/ir
Nadav reported that since this_cpu_read() became asm-volatile, many
smp_processor_id() users generated worse code due to the extra
constraints.
However since smp_processor_id() is reading a stable value, we can use
__this_cpu_read().
Reported-by: Nadav Amit
Signed-off-by: Peter Zijlstra (Intel)
Almost all of this is ran with IRQs disabled and therefore doesn't
need the extra constraints on the this_cpu_*() ops, use __this_cpu_*()
to alleviate this.
Reported-by: Nadav Amit
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/mm/tlb.c | 62 +++
Nadav reported that code-gen changed because of the this_cpu_*()
constraints, avoid this for select_idle_cpu() because that runs with
preemption (and IRQs) disabled anyway.
Reported-by: Nadav Amit
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/fair.c |5 +++--
1 file changed, 3 inse
On Wed, 27 Feb 2019 at 11:02, Marc Zyngier wrote:
>
> + Lorenzo
>
> Hi Brian,
>
> On 26/02/2019 23:28, Brian Norris wrote:
> > + others
> >
> > Hi Marc,
> >
> > Thanks for the series. I have a few bits of history to add to this, and
> > some comments.
> >
> > On Sun, Feb 24, 2019 at 02:04:22PM +00
Nadav reported that since the this_cpu_*() ops got asm-volatile
constraints on, code generation suffered for do_IRQ(), but since this
is all with IRQs disabled we can use __this_cpu_*().
Reported-by: Nadav Amit
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/irq_regs.h |4 ++-
Nadav Amit reported that commit:
b59167ac7baf ("x86/percpu: Fix this_cpu_read()")
added a bunch of constraints to all sorts of code; and while some of
that was correct and desired, some of that seems superfluous.
The thing is, the this_cpu_*() operations are defined IRQ-safe, this
means the va
On Wed, Feb 27, 2019 at 10:39 AM Greg Kroah-Hartman
wrote:
>
> On Wed, Feb 27, 2019 at 10:31:48AM +0200, Oded Gabbay wrote:
> > On Wed, Feb 27, 2019 at 9:05 AM Yue Haibing wrote:
> > >
> > > From: YueHaibing
> > >
> > > Fixes the following sparse warnings:
> > >
> > > drivers/misc/habanalabs/goy
On Tue, Feb 26, 2019 at 11:02:50AM -0800, Linus Torvalds wrote:
> On Tue, Feb 26, 2019 at 10:33 AM Peter Zijlstra wrote:
> >
> > Arguably we could fix that for __this_cpu_xchg(), which isn't IRQ-safe.
>
> Yeah, I guess x86 _should_ really do __this_cpu_xchg() as just a
> read-write pair.
See the
On 2019/02/21 21:31, Tetsuo Handa wrote:
> On 2019/02/21 20:09, Greg Kroah-Hartman wrote:
This is the correct fix (in spirit, we may argue about whether it is
valid to call the flag "state_add_uevent_sent" now or we should or
collapse both it and "state_add_uevent_sent" into
"ne
On 27/02/2019 10:32, Cornelia Huck wrote:
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
Let's do this w
On 27/02/2019 10:42, Cornelia Huck wrote:
On Fri, 22 Feb 2019 16:29:57 +0100
Pierre Morel wrote:
To be able to use the VFIO interface to facilitate the
mediated device memory pining/unpining we need to register
s/pining/pinning/ (unless it's pining for the fjords :)
a notifier for IOMMU.
> This message is in regard to a bug I have open on bugs.launchpad.net, 1813372,
> linked below. This issue, originally identified in an Ubuntu kernel, has been
> duplicated in the most current mainline kernel, 5.0-rc8, and is in regard to
> problems attaining a wireless connection at 802.11ac spe
And because it's one of _those_ days, I forgot to include one patch...
---
Subject: x86/percpu: Optimize raw_cpu_xchg()
From: Peter Zijlstra
Date: Wed Feb 27 11:09:56 CET 2019
Since raw_cpu_xchg() doesn't need to be IRQ-safe, like
this_cpu_xchg(), we can use a simple load-store instead of the
On 2019-02-27, Petr Mladek wrote:
>> Implement a non-sleeping NMI-safe write_atomic console function in
>> order to support emergency printk messages.
>
> It uses console_atomic_lock() added in 18th patch. That one uses
> prb_lock() added by 2nd patch.
>
> Now, prb_lock() allows recursion on the s
On Wed, Feb 27, 2019 at 11:43:22AM +0530, Ketan Patil wrote:
> The original code assigns the value from rtime to utime variable,
> and then jumps to the update label. And the value of utime is then
> updated, so the earlier value of utime is not used. Hence remove
> that unnecessary assignment stat
Hi Gustavo,
Sorry for the delay.
On 27/02/19 03:53, Gustavo A. R. Silva wrote:
> Hi all,
>
> Friendly ping:
>
> Who can ack or review this, please?
>
> Thanks
> --
> Gustavo
>
> On 2/11/19 4:14 PM, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cas
Hi Stephen
On Tue, 2019-02-26 at 09:55 -0800, Stephen Boyd wrote:
> Quoting matthias@kernel.org (2019-02-14 08:32:42)
> > From: Jasper Mattsson
> >
> > Currently, DRAM-related clocks are not marked with CLK_IS_CRITICAL
> > for MT6797. This causes memory corruption when the system is
> > boot
On Wed, Feb 27, 2019 at 06:06:22PM +0800, Morris Ku wrote:
> I am an engineer in the software team at SUNIX Inc.,
> maintain SUNIX Multi-I/O Board Device driver,we plan to submit drivers to
> the kernel,therefore,i want to modify file for resolve driver conflict issue.
> ---
> tty/serial/8250/8250
301 - 400 of 898 matches
Mail list logo
