On Fri, Jan 25, 2019 at 3:17 PM Heikki Krogerus
wrote:
>
> Driver for fusb302 does not support alternate modes, so the
> connection is not really needed for now. Removing that
> connection description allows us to improve the USB Type-C
> mux API.
>
Acked-by: Andy Shevchenko
supposed to go via U
Add support for Texas Instruments ADS7866, ADS7867 and ADS7868
8/10/12 bit Single channel ADC.
Datasheet: http://www.ti.com/lit/ds/symlink/ads7868.pdf
Cc: Alexandru Ardelean
Signed-off-by: Ricardo Ribalda Delgado
---
v3: Changes by Alexandru Ardelean
- Modify Kconfig to clarify that the chip
Bindings for dac7612.
Cc: devicet...@vger.kernel.org
Signed-off-by: Ricardo Ribalda Delgado
---
.../bindings/iio/dac/ti,dac7612.txt | 29 +++
MAINTAINERS | 1 +
2 files changed, 30 insertions(+)
create mode 100644 Documentation/device
It is a driver for Texas Instruments Dual, 12-Bit Serial Input
Digital-to-Analog Converter.
Datasheet of this chip:
http://www.ti.com/lit/ds/sbas106/sbas106.pdf
Signed-off-by: Ricardo Ribalda Delgado
---
v3: Changes by Jonathan Cameron
- Include OF compatible strings
- Rename RESOLUTION define
Hi Randy,
Boris Brezillon wrote on Mon, 28 Jan 2019
10:43:38 +0100:
> On Sun, 27 Jan 2019 18:21:42 -0800
> Randy Dunlap wrote:
>
> > From: Randy Dunlap
> >
> > Fix kernel-doc warnings in drivers/mtd/nand/raw:
With the prefix changed to "mtd: rawnand:"
Acked-by: Miquel Raynal
Thanks,
Miq
Hi Pavel, Rafael,
Do you have some other hints I could follow in order to solve the
scenario I tried to cover with these patches, if these are not
a proper fit for the current code?
Thank you,
Claudiu Beznea
On 08.01.2019 12:56, Claudiu Beznea - M18063 wrote:
> From: Claudiu Beznea
>
> Hi,
>
On Fri, Jan 25, 2019 at 3:18 PM Heikki Krogerus
wrote:
>
> We can replace the second parameter that is passed to the
> typec_mux_get() function with alt mode description
> structure, and simply pass NULL with accessory modes.
>
> With accessory modes there is no need for additional
> identificatio
Cleanup comments to avoid lines over 80 characters
and follow kernel style for block comments.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/os_dep/mlme_linux.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8188eu/os_dep/
Replace tabs with spaces in declarations to cleanup whitespace.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/os_dep/mlme_linux.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8188eu/os_dep/mlme_linux.c
b/drivers/staging/rtl8188eu/
Instead of first asign 'wrqu.data.length = p - buff' use 'p - buff'
directly in min_t() in the subsequent asignment. Clears a line over
80 characters checkpatch warning.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/os_dep/mlme_linux.c | 3 +--
1 file changed, 1 insertion(+), 2 de
Move the declaration of 'psec_priv' out of the else path and use it
in the if path as well to improve readability. Also clears line over
80 characters checkpatch warnings.
Suggested-by: Joe Perches
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/os_dep/mlme_linux.c | 29 ++-
On Wed, Jan 23, 2019 at 12:48:11PM +0100, Anders Roxell wrote:
> When CONFIG_PROC_FS isn't set the variable cn isn't used.
>
> net/ipv4/netfilter/ipt_CLUSTERIP.c: In function ‘clusterip_net_exit’:
> net/ipv4/netfilter/ipt_CLUSTERIP.c:849:24: warning: unused variable ‘cn’
> [-Wunused-variable]
>
Change '&array[0]' to just 'array' in rtw_reset_securitypriv().
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/os_dep/mlme_linux.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8188eu/os_dep/mlme_linux.c
b/drivers/staging/rtl8188eu/os_d
The local variables backup_index, backup_counter and backup_time
in rtw_reset_securitypriv() are all asigned before their uses, so
initialization to zero is not necessary.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8188eu/os_dep/mlme_linux.c | 6 +++---
1 file changed, 3 insertions(+)
On Fri, Jan 25, 2019 at 3:17 PM Heikki Krogerus
wrote:
>
> When the connections are defined in firmware, struct
> device_connection will have the fwnode member pointing to
> the device node (struct fwnode_handle) of the requested
> device, and the endpoint will not be used at all in that
> case.
On 01/25/19 at 03:08pm, Borislav Petkov wrote:
> On Fri, Jan 25, 2019 at 09:45:18PM +0800, Dave Young wrote:
> > AFAIK, some people prefer to explictly reserve crash memory at high
> > region even if it is possible to reserve at low area. May because
> > <4G memory is limited on large server, they
On Mon, 21 Jan 2019 15:33:29 +,
Julien Thierry wrote:
>
> Interrupts masked by ICC_PMR_EL1 will not be signaled to the CPU. This
> means that hypervisor will not receive masked interrupts while running a
> guest.
>
> Avoid this by making sure ICC_PMR_EL1 is unmasked when we enter a guest.
>
On Fri, Jan 25, 2019 at 3:17 PM Heikki Krogerus
wrote:
>
> If connections between devices are described in OF graph or
> ACPI device graph, we can find them by using the
> fwnode_graph_*() functions.
> +typedef void *(*devcon_match_t)(struct device_connection *con, int ep,
> +
On Mon, 21 Jan 2019 15:33:30 +,
Julien Thierry wrote:
>
> Currently, irqflags are saved before calling runtime services and
> checked for mismatch on return.
>
> Provide a pair of overridable macros to save and restore (if needed) the
> state that need to be preserved on return from a runtim
v2 changes:
- Address Boris's comments.
---
I recently encountered a crash in cper_estatus_check() when called by
bert_init(). Patches follow to fix the problem. Note that I cannot fully
test the patches since the hardware error record on that machine has
been cleared.
The crash log:
[ 125.666
From: Manfred Schlaegl
There is no clipping on the x or y axis for logos larger that the framebuffer
size. Therefore: a logo bigger than screen size leads to invalid memory access:
[1.254664] Backtrace:
[1.254728] [] (cfb_imageblit) from []
(fb_show_logo+0x620/0x684)
[1.254763] r10
Check that the length recorded in the generic error status block is
within the region before checking the contents of the region itself.
Otherwise it may result in an out-of-bounds access if the system
firmware has generated a status block with an invalid length (larger
than the mapped region). Als
On 1/23/19 11:54 AM, Borislav Petkov wrote:
On Tue, Jan 22, 2019 at 04:09:12PM +, Ross Lagerwall wrote:
When checking a generic status block, we iterate over all the generic
data blocks. The loop condition only checks that the start of the
generic data block is valid (within estatus->data_le
When checking a generic status block, we iterate over all the generic
data blocks. The loop condition only checks that the start of the
generic data block is valid (within estatus->data_length) but not the
whole block. Because the size of data blocks (excluding error data) may
vary depending on the
Hi Stephen,
Stephen Boyd wrote on Fri, 25 Jan 2019 13:28:28
-0800:
> Quoting Miquel Raynal (2019-01-04 07:54:06)
> > Hi Stephen,
> >
> > Stephen Boyd wrote on Tue, 11 Dec 2018 09:12:55
> > -0800:
> >
> > > Sorry, I'm not reviewing the whole patch right now, just this one little
> > > bit be
On 1/14/19 9:44 AM, Ravi Bangoria wrote:
> Powerpc hw does not have inbuilt latency filter (--ldlat) for mem-load
> event and, perf_mem_events by default includes ldlat=30 which is
> causing failure on powerpc. Refactor code to support perf mem/c2c on
> powerpc.
>
> This patch depends on kernel
Am Mittwoch, 16. Januar 2019, 12:06:54 CET schrieb Stephan Müller:
Hi Herbert,
> Changes v2:
> * Incorporation of all comments from Eric Biggers
>
> Stephan Mueller (6):
> crypto: add template handling for RNGs
> crypto: kdf - SP800-108 Key Derivation Function
> crypto: kdf - add known ans
Below is the list of build error/warning regressions/improvements in
v5.0-rc4[1] compared to v4.20[2].
Summarized:
- build errors: +2/-4
- build warnings: +111/-14840
JFYI, when comparing v5.0-rc4[1] to v5.0-rc3[3], the summaries are:
- build errors: +0/-0
- build warnings: +57/-64
Note
On Fri, 25 Jan 2019 11:02:03 -0600
Josh Poimboeuf wrote:
> On Fri, Jan 25, 2019 at 10:36:57AM -0600, Josh Poimboeuf wrote:
> > How about this patch? It's just a revert of 73d5e2b47264 and
> > bc2d8d262cba, plus the 1-line vmx_vm_init() change. If it looks ok to
> > you, I can clean it up and su
On Mon, Jan 28, 2019 at 05:43:01PM +0800, Nicolas Boichat wrote:
> L1 tables are allocated with __get_dma_pages, and therefore already
> ignored by kmemleak.
>
> Without this, the kernel would print this error message on boot,
> when the first L1 table is allocated:
>
> [2.810533] kmemleak: T
Am Montag, 19. November 2018, 16:14:14 CET schrieb Damian Kos:
> This is basically the same fix as in
> commit fa68d4f8476b ("drm/rockchip: fix for mailbox read size")
> but for cdn_dp_mailbox_validate_receive function.
>
> See patchwork.kernel.org/patch/10671981/ for details.
>
> Signed-off-by:
On Mon, Jan 28, 2019 at 05:58:09PM +0800, Dave Young wrote:
> Another reason is in case ,high we will need automatically reserve a
> region in low area for swiotlb. So for example one use
> crashkernel=256M,high, actual reserved memory is 256M above 4G and
> another 256M under 4G for swiotlb. No
On Sat, Jan 19, 2019 at 10:50:24PM +0100, Luc Van Oostenryck wrote:
> nft_counter_rest() has its first argument declared as
> struct nft_counter_percpu_priv __percpu *priv
> but this structure is not percpu (it only countains
> a member 'counter' which is, correctly, a pointer to a
> percpu s
Hi Dinh,
Masahiro Yamada wrote on Wed, 16 Jan
2019 10:27:11 +0900:
> (+CC Dinh Nguyen)
>
> On Tue, Jan 15, 2019 at 5:22 PM Miquel Raynal
> wrote:
> >
> > Hi Masahiro,
> >
> > Masahiro Yamada wrote on Tue, 15 Jan
> > 2019 17:11:34 +0900:
> >
> > > Commit 6f1fe97bec34 ("mtd: rawnand: denali_
From: Martin Kepplinger
This adds support for explicitly switching the mmc's power on and off
which is needed for example for WL1837 wifi controllers. ip link set wlan0 down
doesn't turn off the VMMC regulator which leads to hangs when loading firmware.
Tested on i.MX28.
Signed-off-by: Martin K
On Thu, 24 Jan 2019 at 19:41, Adrian Hunter wrote:
>
> On 11/01/19 1:08 PM, Faiz Abbas wrote:
> > From: Chunyan Zhang
> >
> > Some standard SD host controllers can support both external dma
> > controllers as well as ADMA/SDMA in which the SD host controller
> > acts as DMA master. TI's omap cont
Hi Martin,
On Mon, 28 Jan 2019 11:20:22 +0100
Martin Kepplinger wrote:
> From: Martin Kepplinger
>
> This adds support for explicitly switching the mmc's power on and off
> which is needed for example for WL1837 wifi controllers. ip link set wlan0
> down
> doesn't turn off the VMMC regulator
On Fri, Jan 25, 2019 at 9:46 AM Mike Rapoport wrote:
>
> Hi,
>
> This starts the 6-9 review :)
>
> These were more difficult to review because small pieces of code are
> interleaved with
> large sequences of register writes. Probably making these register data
> rather than code can help.
>
> On
On Mon, 21 Jan 2019 15:33:32 +,
Julien Thierry wrote:
>
> The addition of PMR should not bypass the semantics of daifflags.
>
> When DA_F are set, I bit is also set as no interrupts (even of higher
> priority) is allowed.
>
> When DA_F are cleared, I bit is cleared and interrupt enabling/di
Den 28.01.2019 09.10, skrev Gerd Hoffmann:
>>> The cursor must be set again after creating the primary surface.
>>> Also drop the error message.
>
>>> if (!bo->is_primary) {
>>> - if (!same_shadow)
>>> + if (!same_shadow) {
>>> qxl_io_create_primary(q
On Sun, Jan 27, 2019 at 10:50:54PM +0800, Chen-Yu Tsai wrote:
> gpiod_get_value() gives out a warning if access to the underlying gpiochip
> requires sleeping, which is common for I2C based chips:
>
> WARNING: CPU: 0 PID: 77 at drivers/gpio/gpiolib.c:2500
> gpiod_get_value+0xd0/0x100
> Mo
Den 28.01.2019 09.59, skrev Gerd Hoffmann:
> On Fri, Jan 25, 2019 at 06:25:27PM +0100, Noralf Trønnes wrote:
>>
>>
>> Den 18.01.2019 13.20, skrev Gerd Hoffmann:
>>> Switch qxl over to the new generic fbdev emulation.
>>>
>>> Signed-off-by: Gerd Hoffmann
>>> ---
>>> drivers/gpu/drm/qxl/qxl_disp
Hi,
On 28/01/19 3:50 PM, Chunyan Zhang wrote:
> On Thu, 24 Jan 2019 at 19:41, Adrian Hunter wrote:
>>
>> On 11/01/19 1:08 PM, Faiz Abbas wrote:
>>> From: Chunyan Zhang
>>>
>>> Some standard SD host controllers can support both external dma
>>> controllers as well as ADMA/SDMA in which the SD hos
Hi,
On 28-01-19 10:45, Andy Shevchenko wrote:
On Fri, Jan 25, 2019 at 3:17 PM Heikki Krogerus
wrote:
Driver for fusb302 does not support alternate modes, so the
connection is not really needed for now. Removing that
connection description allows us to improve the USB Type-C
mux API.
Acked-
On Fri, Jan 25, 2019 at 9:51 AM Mike Rapoport wrote:
>
> On Wed, Jan 23, 2019 at 02:00:49AM +0200, Oded Gabbay wrote:
> > This patch adds the H/W queues module and the code to initialize Goya's
> > various compute and DMA engines and their queues.
> >
> > Goya has 5 DMA channels, 8 TPC engines and
On (01/28/19 10:18), Vlastimil Babka wrote:
> On 1/28/19 9:57 AM, Sergey Senozhatsky wrote:
> > Hello,
> >
> > next-20190125
> >
> > kcompactd0 is spinning on something, burning CPUs in the meantime:
>
> Hi, could you check/add this to the earlier thread? Thanks.
>
> https://lore.kernel.org/lkm
On Mon, Jan 28, 2019 at 12:39:30AM +0800, Chen-Yu Tsai wrote:
> The GIC device node was placed out of order in the initial device tree
> submission. Move it so the nodes are correctly sorted by base address
> again.
>
> Fixes: e54be32d0273 ("arm64: allwinner: h6: add the basical Allwinner H6 DTSI
On Sun, Jan 27, 2019 at 10:48:35PM +0800, Chen-Yu Tsai wrote:
> The panel backlight and enable GPIO comments were incorrectly placed
> in the input port, while it should have been in the panel node itself.
>
> Move them to the correct position.
>
> Signed-off-by: Chen-Yu Tsai
Applied, thanks!
M
On Sun, Jan 27, 2019 at 10:48:34PM +0800, Chen-Yu Tsai wrote:
> Now that we support the GPIOs on the AXP209, we can control the LCD
> backlight with them.
>
> Signed-off-by: Chen-Yu Tsai
Applied, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
On Sun, Jan 27, 2019 at 10:48:36PM +0800, Chen-Yu Tsai wrote:
> Now that we support the AXP209 GPIOs, we can toggle the LCD panel enable
> line. Add the GPIO phandle to the panel.
>
> Signed-off-by: Chen-Yu Tsai
Applied, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engine
Hi Zhou,
On Mon, Jan 28, 2019 at 10:23 AM Zhou Yanjie wrote:
> Add support for probing the 8250_ingenic driver on the
> X1000 Soc from Ingenic.
>
> Signed-off-by: Zhou Yanjie
Thanks for your patch!
> --- a/drivers/tty/serial/8250/8250_ingenic.c
> +++ b/drivers/tty/serial/8250/8250_ingenic.c
>
On 25.01.2019 02:33, Ronald Tschalär wrote:
> commit d6abe6df706c (drm/bridge: sil_sii8620: do not have a dependency
> of RC_CORE) changed the driver to select both RC_CORE and INPUT.
> However, this causes problems with other drivers, in particular an input
> driver that depends on MFD_INTEL_LPSS_
On Sun, Jan 27, 2019 at 10:48:37PM +0800, Chen-Yu Tsai wrote:
> The A13 Q8 tablet, following the A13 reference tablet design, has the
> system's fixed 3.3V rail feed the VCC supply of the LCD panel.
> Additional voltage rails used by the panel are generated using a
> regulator fed from the unregula
On Sun, Jan 27, 2019 at 10:48:38PM +0800, Chen-Yu Tsai wrote:
> The compatible string for the LCD panel used for the Q8 tablets are just
> a placeholder that was shown to be compatible with the actual panels
> found on these devices. The real panels do not have any identifiable
> markings and vary
Hi Andrey,
On Thu, 2019-01-24 at 16:21 -0800, Andrey Smirnov wrote:
> > Thank you, applied all three to reset/next with a small whitespace
> > alignment fix.
> >
>
> Thanks again for applying this stuff. If that's not too much to ask,
> would you mind creating an immutable branch, so I could sta
On (01/28/19 10:16), Jan Kara wrote:
> On Sun 27-01-19 16:36:34, valdis.kletni...@vt.edu wrote:
> > On Sun, 27 Jan 2019 17:00:27 +0100, Pavel Machek said:
> > > > > I've noticed this as well on earlier kernels (next-20181224 to
> > > > > 20190115)
> > > > > Some more info:
> > > > > 1) echo 3 > /p
On Mon, 21 Jan 2019 15:33:33 +,
Julien Thierry wrote:
>
> In preparation for the application of alternatives at different points
> during the boot process, provide the possibility to check whether
> alternatives for a feature of interest was already applied instead of
> having a global boolea
On Mon, Jan 28, 2019 at 02:28:44PM +0530, Jagan Teki wrote:
> CSI block in Allwinner A64 has similar features as like in H3,
> but the default CSI_SCLK rate cannot work properly to drive the
> connected sensor interface.
>
> The tested mod cock rate is 300 MHz and BSP vfe media driver is also
> us
On 1/28/19 2:38 AM, masonccy...@mxic.com.tw wrote:
> Hi Marek,
Hi,
>> "Marek Vasut"
>> >> >> > +module_platform_driver(rpc_spi_driver);
>> >> >>
>> >> >> RPC is not a SPI controller, it's a SPI and HF controller.
>> >> >>
>> >> >> Also, how difficult will it be to add the HF support ?
>> >> >
>>
On Mon, Jan 28, 2019 at 02:28:45PM +0530, Jagan Teki wrote:
> Add dts node details for Allwinner A64 CSI controller.
>
> A64 CSI has similar features as like in H3, but the CSI_SCLK
> need to update it to 300MHz than default clock rate.
>
> Signed-off-by: Jagan Teki
> Acked-by: Maxime Ripard
A
On Mon, Jan 28, 2019 at 10:16:27AM +0100, Jan Kara wrote:
> On Sun 27-01-19 16:36:34, valdis.kletni...@vt.edu wrote:
> > On Sun, 27 Jan 2019 17:00:27 +0100, Pavel Machek said:
> > > > > I've noticed this as well on earlier kernels (next-20181224 to
> > > > > 20190115)
> > > > > Some more info:
> >
On Sun, Jan 27, 2019 at 10:50:54PM +0800, Chen-Yu Tsai wrote:
> gpiod_get_value() gives out a warning if access to the underlying gpiochip
> requires sleeping, which is common for I2C based chips:
>
> WARNING: CPU: 0 PID: 77 at drivers/gpio/gpiolib.c:2500
> gpiod_get_value+0xd0/0x100
> Mo
I'll be moving on to different things in the storage stack and Hannes
agreed to take over FCoE.
Cc: Hannes Reinecke
Signed-off-by: Johannes Thumshirn
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9f64f8d3740e..49b829794699 10
On Mon, Jan 14, 2019 at 09:44:02AM +0530, Ravi Bangoria wrote:
SNIP
> diff --git a/tools/perf/arch/x86/util/mem-events.c
> b/tools/perf/arch/x86/util/mem-events.c
> new file mode 100644
> index 000..5b4dcfe
> --- /dev/null
> +++ b/tools/perf/arch/x86/util/mem-events.c
> @@ -0,0 +1,25 @@
> +/
On Thu, Jan 24, 2019 at 03:14:41PM -0800, Dave Hansen wrote:
> v3 spurred a bunch of really good discussion. Thanks to everybody
> that made comments and suggestions!
>
> I would still love some Acks on this from the folks on cc, even if it
> is on just the patch touching your area.
>
> Note: th
Setting MSR_RI applies to head_32 and head_8xx, but not to
head_40x. So in order to refactor EXCEPTION_PROLOG for 40x too,
this patch adds a macro for setting MSR_RI.
In the meantime, this gives the opportunity to make it
simpler on the 8xx as writing in SPRN_EID sets MSR_RI.
Signed-off-by: Chris
Add START_EXCEPTION() in head_32.h for preparing the use
of head_32.h in head_40x.S
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_32.h | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/head_32.h b/arch/powerpc/kernel/head_32.h
index 643
This serie refactors exception entry macros for 40x, 6xx and 8xx
This serie will benefit to the implementation of CONFIG_VMAP, and also
to Ben's serie on MSR_EE.
First patch of this serie is a part of the CONFIG_THREAD_INFO_IN_TASK serie.
This avoids a conflict between the two series.
Christophe
As preparation for using head_32.h for head_40x.S, move
LOAD_MSR_KERNEL() there and use it to load r10 with MSR_KERNEL value.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/entry_32.S | 9 +
arch/powerpc/kernel/head_32.h | 11 ++-
2 files changed, 11 insertions(+), 9 d
This patch renames THREAD_INFO to TASK_STACK, because it is in fact
the offset of the pointer to the stack in task_struct so this pointer
will not be impacted by the move of THREAD_INFO.
Signed-off-by: Christophe Leroy
Reviewed-by: Nicholas Piggin
---
arch/powerpc/kernel/asm-offsets.c| 2 +-
Unlike said in the comment, r1 is not reused by the critical
exception handler, as it uses a dedicated critirq_ctx stack.
Decrementing r1 early is then unneeded.
Should the above be valid, the code is crap buggy anyway as
r1 gets some intermediate values that would jeopardise the
whole process (fo
EXCEPTION_PROLOG is similar in head_8xx.S and head_32.S
This patch creates head_32.h and moves EXCEPTION_PROLOG macro
into it.
It also moves EXCEPTION() and EXC_XFER_() macros which are also
similar. For that, the 8xx needs to define a dummy DO_KVM asm macro.
Signed-off-by: Christophe Leroy
Refactor exception entry macros by using the ones defined in head_32.h
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_40x.S | 94 --
1 file changed, 8 insertions(+), 86 deletions(-)
diff --git a/arch/powerpc/kernel/head_40x.S b/arch/powerpc/
This patch adds STACK_FRAME_REGS_MARKER in the stack at exception entry
in order to see interrupts in call traces as below:
[0.013964] Call Trace:
[0.014014] [c0745db0] [c007a9d4] tick_periodic.constprop.5+0xd8/0x104
(unreliable)
[0.014086] [c0745dc0] [c007aa20] tick_handle_periodic+0
Add CLR_MSR_WE() macro to allow 40x to clear
that bit from the register containing msr value.
This is the only difference between common EXCEPTION_PROLOG
and 40x one. This patch will allow 40x to use the common one.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_32.h | 5 +
1
This patch splits NORMAL_EXCEPTION_PROLOG in the same way as in
head_8xx.S and head_32.S and renames it EXCEPTION_PROLOG() as well
to match head_32.h
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_40x.S | 26 --
1 file changed, 16 insertions(+), 10 deletions
This patch adds EXC_XFER_TEMPLATE_CRITICAL() for handling
transfer to critical exception handler. This will allow
to move the normal exception to using the standard
EXC_XFER_TEMPLATE() defined in head_32.h
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_40x.S | 21 +++---
On Fri, Jan 25, 2019 at 9:51 AM Mike Rapoport wrote:
>
> On Wed, Jan 23, 2019 at 02:00:50AM +0200, Oded Gabbay wrote:
> > This patch adds support for receiving events from Goya's control CPU and
> > for receiving MSI-X interrupts from Goya's DMA engines and CPU.
> >
> > Goya's PCI controller suppo
Hi Adrian,
On 24/01/19 5:38 PM, Adrian Hunter wrote:
> On 11/01/19 1:08 PM, Faiz Abbas wrote:
>> Some controllers might prematurely issue a data timeout during an erase
>> command. Add a quirk to disable the interrupt when an erase command is
>> issued.
>
> I might have already asked this, but wo
On Mon, 21 Jan 2019 15:33:34 +,
Julien Thierry wrote:
>
> From: Daniel Thompson
>
> Currently alternatives are applied very late in the boot process (and
> a long time after we enable scheduling). Some alternative sequences,
> such as those that alter the way CPU context is stored, must be
Hi Hyun,
Thanks for the review.
> -Original Message-
> From: Hyun Kwon [mailto:hyun.k...@xilinx.com]
> Sent: Saturday, January 26, 2019 7:45 AM
> To: Vishal Sagar
> Cc: Hyun Kwon ; laurent.pinch...@ideasonboard.com;
> mche...@kernel.org; robh...@kernel.org; mark.rutl...@arm.com; Michal
On 01/28, Benjamin Tissoires wrote:
>
> Oleg, can you provide some feedback before I push this?
Looks good to me, feel free to add
Reviewed-by: Oleg Nesterov
> > + set_current_state(TASK_RUNNING);
I still think that
__set_current_state(TASK_RUNNING);
will lo
Hi Hyun,
Thanks for the review.
> -Original Message-
> From: Hyun Kwon [mailto:hyun.k...@xilinx.com]
> Sent: Saturday, January 26, 2019 7:45 AM
> To: Vishal Sagar
> Cc: Hyun Kwon ; laurent.pinch...@ideasonboard.com;
> mche...@kernel.org; robh...@kernel.org; mark.rutl...@arm.com; Michal
>
On Mon, 21 Jan 2019 15:33:35 +,
Julien Thierry wrote:
>
> The code to detect whether Linux has access to group0 interrupts can
> prove useful in other parts of the driver.
>
> Provide a separate function to do this.
>
> Signed-off-by: Julien Thierry
> Cc: Thomas Gleixner
> Cc: Jason Coope
On Mon, 21 Jan 2019 15:33:36 +,
Julien Thierry wrote:
>
> Once the boot CPU has been prepared or a new secondary CPU has been
> brought up, use ICC_PMR_EL1 to mask interrupts on that CPU and clear
> PSR.I bit.
>
> Since ICC_PMR_EL1 is initialized at CPU bringup, avoid overwriting
> it in the
On Mon, 21 Jan 2019 15:33:37 +,
Julien Thierry wrote:
>
> Implement architecture specific primitive allowing the GICv3 driver to
> use priorities to mask interrupts.
>
> Signed-off-by: Julien Thierry
> Suggested-by: Daniel Thompson
> Cc: Marc Zyngier
> Cc: Catalin Marinas
> Cc: Will Deac
On Fri, Jan 25, 2019 at 9:54 AM Mike Rapoport wrote:
>
> On Wed, Jan 23, 2019 at 02:00:51AM +0200, Oded Gabbay wrote:
> > This patch add the sysfs and hwmon entries that are exposed by the driver.
> >
> > Goya has several sensors, from various categories such as temperature,
> > voltage, current,
On Tue, Jan 22, 2019 at 08:45:12PM +0300, Alexey Budankov wrote:
SNIP
> The patch set has been validated on BT benchmark from NAS Parallel
> Benchmarks [2] running on dual socket, 44 cores, 88 hw threads Broadwell
> system with kernels v4.4-21-generic (Ubuntu 16.04) and v4.20.0-rc5
> (tip perf
Hi Thierry,
On Fri, 2019-01-25 at 11:15 +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> When requesting a reset control for exclusive use that's already in use,
> an -EBUSY error code is returned. Users can react accordingly when they
> receive that error code, so there is no need to lou
Hi Ard,
On Thu, Jan 24, 2019 at 1:25 PM Ard Biesheuvel
wrote:
>
> On Thu, 24 Jan 2019 at 07:58, Vivek Gautam
> wrote:
> >
> > On Mon, Jan 21, 2019 at 7:55 PM Ard Biesheuvel
> > wrote:
> > >
> > > On Mon, 21 Jan 2019 at 14:56, Robin Murphy wrote:
> > > >
> > > > On 21/01/2019 13:36, Ard Bieshe
From: Manfred Schlaegl
commit 3fb72f1e6e61 ("ipconfig wait for carrier") added a
"wait for carrier" policy, with a fixed worst case maximum wait
of two minutes.
This makes the wait for carrier timeout configurable (0 - 240 seconds).
The informative timeout messages introduced with
commit 5e404c
On Mon, 28 Jan 2019 at 11:20, Martin Kepplinger wrote:
>
> From: Martin Kepplinger
>
> This adds support for explicitly switching the mmc's power on and off
> which is needed for example for WL1837 wifi controllers. ip link set wlan0
> down
> doesn't turn off the VMMC regulator which leads to ha
From: Borislav Petkov
... so that they can get CCed on platform patches.
Signed-off-by: Borislav Petkov
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: x...@kernel.org
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index cef2104d5f2c..825cad5e0
On Sun, 2019-01-27 at 08:17 +, David Binderman wrote:
> Hello there,
>
> drivers/media/platform/imx-pxp.c:683:24: warning: duplicated ‘if’ condition
> [-Wd
> uplicated-cond]
>
> Source code is
>
>} else if (ycbcr_enc == V4L2_YCBCR_ENC_709) {
> if (qua
On 1/28/19 12:06 PM, Johannes Thumshirn wrote:
I'll be moving on to different things in the storage stack and Hannes
agreed to take over FCoE.
Cc: Hannes Reinecke
Signed-off-by: Johannes Thumshirn
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINER
+ Adrian (the SDHCI maintainer)
On Mon, 14 Jan 2019 at 20:17, Alamy Liu wrote:
>
> Prevent to use fixed value (NUM_SLOTS) after it had been determined
> and saved in a variable (cq_host->num_slots).
>
> Signed-off-by: Alamy Liu
> ---
> drivers/mmc/host/cqhci.c | 2 +-
> 1 file changed, 1 insert
On Mon, 21 Jan 2019 15:33:38 +,
Julien Thierry wrote:
>
> The values non secure EL1 needs to use for PMR and RPR registers depends on
> the value of SCR_EL3.FIQ.
>
> The values non secure EL1 sees from the distributor and redistributor
> depend on whether security is enabled for the GIC or n
On Sat, 26 Jan 2019, Sam Ravnborg wrote:
> The use of drmP.h is discouraged and removal of it from
> drm_modeset_helper.h caused i915 to fail to build.
>
> This patch introduce the necessary fixes to prepare for the
> drmP.h removal from drm_modeset_helper.h.
>
> In the files touched the lists of
Hi,
> > If the above explains things better to you I should probably replace the
> > commit message with that.
>
> This is actually my first review of a driver that I'm not familiar with.
> I'm not quite sure how much in depth understanding that is required to
> put my ack on it.
Usually I try
On Fri 25-01-19 19:15:49, Michal Hocko wrote:
> On Fri 25-01-19 18:33:15, Michal Hocko wrote:
> > On Fri 25-01-19 17:39:38, Michal Hocko wrote:
> > > On Fri 25-01-19 11:16:30, robert shteynfeld wrote:
> > > > Attached is the dmesg from patched kernel.
> > >
> > > Your Node1 physical memory range p
101 - 200 of 2154 matches
Mail list logo
