On Fri, Apr 26, 2019 at 08:05:51AM +, Robin Gong wrote:
> ERR009165 fixed from i.mx6ul, add it to show the errata fixed.
>
> Signed-off-by: Robin Gong
> ---
> Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devi
Mauro, I have resolved all of your comments here. Now git recognizes it as a
renaming.
Please check update version later. Many thanks!
On Sat, Apr 27, 2019 at 11:31:53AM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 26 Apr 2019 23:31:25 +0800
> Changbin Du escreveu:
>
> > This converts the plai
On 4/23/2019 10:19 AM, Vidya Sagar wrote:
Add an API to group all the tasks to be done to de-initialize host which
can then be called by any DesignWare core based driver implementations
while adding .remove() support in their respective drivers.
Signed-off-by: Vidya Sagar
Acked-by: Gustavo Pime
On 02-05-19, 11:28, Vinod Koul wrote:
> On 01-05-19, 10:57, Pierre-Louis Bossart wrote:
> > SoundWire support will be provided in Linux with the Sound Open
> > Firmware (SOF) on Intel platforms. Before we start adding the missing
> > pieces, there are a number of warnings and style issues reported
On Wed, May 01, 2019 at 10:20:44PM +0200, Andreas Färber wrote:
> + linux-actions
>
> Am 01.05.19 um 09:07 schrieb Nishad Kamdar:
> > This patch corrects the SPDX License Identifier style
> > in header files related to Clock Drivers for Actions Semi Socs.
> > For C header files Documentation/proce
On Thu, May 02, 2019 at 12:31:42PM +1000, Tobin C. Harding wrote:
> Currently we use custom logic to track kobject initialization. Recently
> a predicate function was added to the kobject API so we now no longer
> need to do this.
>
> Use kobject API to check for initialized state of kobjects ins
On 4/30/19 7:56 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
---
- update i2c info
drivers/mfd/intel-lpss-pci.c | 13 +
1 file changed, 13 insertions(+)
Rev
(+ Ingo)
On Tue, 30 Apr 2019 at 21:52, Matthew Garrett wrote:
>
> On Tue, Apr 30, 2019 at 6:07 AM Bartosz Szczepanek wrote:
> >
> > I may be a little late with this comment, but I've just tested these
> > patches on aarch64 platform (from the top of jjs/master) and got
> > kernel panic ("Unable
On 2019-05-01 14:48:44 [-0700], Kevin Hilman wrote:
> "kernelci.org bot" writes:
>
> > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> > * This automated bisection report was sent to you on the basis *
> > * that you may be involved with the breaking commit it has *
> >
On Thu, May 02, 2019 at 07:56:16AM +1000, Tobin C. Harding wrote:
> On Sat, Apr 27, 2019 at 09:28:09PM +0200, Greg Kroah-Hartman wrote:
> > On Sat, Apr 27, 2019 at 06:13:30PM +1000, Tobin C. Harding wrote:
> > > (Note at bottom on reasons for 'To' list 'Cc' list)
> > >
> > > Hi,
> > >
> > > kobje
On Thu, May 02, 2019 at 07:58:58AM +1000, Tobin C. Harding wrote:
> On Wed, May 01, 2019 at 01:10:22PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, May 01, 2019 at 09:38:03AM +1000, Tobin C. Harding wrote:
> > > Hi,
> > >
> > > Looks like I've created a bit of confusion trying to fix memleaks in
>
On Thu, May 02, 2019 at 12:31:40PM +1000, Tobin C. Harding wrote:
> kernel-doc comments have a prescribed format. This includes parenthesis
> on the function name. To be _particularly_ correct we should also
> capitalise the brief description and terminate it with a period.
Ah, I didn't know tha
On Thu, May 02, 2019 at 12:31:39PM +1000, Tobin C. Harding wrote:
> Currently the docstring for kobject_get_path() mentions 'kset'. The
> kset is not used in the function callchain starting from this function.
>
> Remove docstring reference to kset from the function kobject_get_path().
>
> Signe
On Tue, Apr 23, 2019 at 10:54:47PM +0200, Jonas Witschel wrote:
> On 2019-04-09 15:44, Jarkko Sakkinen wrote:
> > On Mon, Apr 08, 2019 at 02:01:38PM +0200, Thibaut Sautereau wrote:
> >> [...]
> >> What's the status of this patch now? It's needed in linux-5.0.y as TPM
> >> 2.0 support is currently b
On Thu, 2 May 2019 15:58:24 +0900
Tomasz Figa wrote:
> 2019年5月2日(木) 15:55 Boris Brezillon :
> >
> > On Thu, 2 May 2019 15:42:59 +0900
> > Tomasz Figa wrote:
> >
> > > 2019年5月2日(木) 15:36 Boris Brezillon :
> > > >
> > > > Hi Tomasz,
> > > >
> > > > On Thu, 2 May 2019 15:23:33 +0900
> > > > Tom
On Thu, May 02, 2019 at 12:31:38PM +1000, Tobin C. Harding wrote:
> Currently error return from kobject_init_and_add() is not followed by a
> call to kobject_put(). This means there is a memory leak.
>
> Add call to kobject_put() in error path of kobject_init_and_add().
>
> Signed-off-by: Tobin
On Thu, May 02, 2019 at 09:17:42AM +0200, Greg Kroah-Hartman wrote:
> On Thu, May 02, 2019 at 07:56:16AM +1000, Tobin C. Harding wrote:
> > On Sat, Apr 27, 2019 at 09:28:09PM +0200, Greg Kroah-Hartman wrote:
> > > On Sat, Apr 27, 2019 at 06:13:30PM +1000, Tobin C. Harding wrote:
> > > > (Note at bo
On Thu 2019-05-02 09:12:32, Greg Kroah-Hartman wrote:
> On Thu, May 02, 2019 at 12:31:42PM +1000, Tobin C. Harding wrote:
> > Currently we use custom logic to track kobject initialization. Recently
> > a predicate function was added to the kobject API so we now no longer
> > need to do this.
> >
On Sat, Apr 20, 2019 at 10:52:40AM -0400, Yangtao Li wrote:
> Orangepi 3 has HDMI type A connector.
>
> Signed-off-by: Yangtao Li
Queued for 5.3, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
signature.asc
Description: PGP signature
Hello Sebastian,
Thanks for the review. This is highly appreciated as charger subsystem
is new to me =)
On Thu, May 02, 2019 at 12:25:35AM +0200, Sebastian Reichel wrote:
> Hi,
>
> On Thu, Apr 25, 2019 at 02:16:51PM +0300, Matti Vaittinen wrote:
> > ROHM BD70528 PMIC includes battery charger blo
On Thu, May 02, 2019 at 12:31:40PM +1000, Tobin C. Harding wrote:
> kernel-doc comments have a prescribed format. This includes parenthesis
> on the function name. To be _particularly_ correct we should also
> capitalise the brief description and terminate it with a period.
Why do think capitali
On Thu, May 02, 2019 at 09:30:44AM +0200, Petr Mladek wrote:
> On Thu 2019-05-02 09:12:32, Greg Kroah-Hartman wrote:
> > On Thu, May 02, 2019 at 12:31:42PM +1000, Tobin C. Harding wrote:
> > > Currently we use custom logic to track kobject initialization. Recently
> > > a predicate function was ad
There is no need to keep sysrq_poweroff_op after initialization, so mark
it with __initdata. Mark some of the function parameters with __maybe_unused
to avoid compilation warnings.
Signed-off-by: Nikitas Angelinas
---
kernel/power/poweroff.c | 7 ---
1 file changed, 4 insertions(+), 3 deleti
On Thu, Apr 18, 2019 at 3:50 PM Pi-Hsun Shih wrote:
>
> Use offsetof to calculate offset of a field to take advantage of
> compiler built-in version when possible, and avoid UBSAN warning when
> compiling with Clang:
>
> ==
> UBSAN: U
On 30/04/2019 16:09, Pierre Morel wrote:
On 30/04/2019 15:26, Halil Pasic wrote:
On Fri, 26 Apr 2019 15:01:27 +0200
Pierre Morel wrote:
+/**
+ * vfio_ap_clrirq: Disable Interruption for a APQN
+ *
+ * @dev: the device associated with the ap_queue
+ * @q: the vfio_ap_queue holding AQIC param
On Mi, 2019-04-24 at 21:23 +0200, Eugeniu Rosca wrote:
> External E-Mail
>
>
> From: Suresh Udipi
>
> It looks like v4.18-rc1 commit [0] which upstreams mld-1.8.0
> commit [1] missed to fix the memory leak in mod_exit function.
>
> Do it now.
>
> [0] aba258b7310167 ("staging: most: cdev: fix
In order to move to clk_hw based API, imx_obtain_fixed_clock_hw
is added. The end goal here is to have all the clk providers use
the clk_hw based API.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk.c | 11 +++
drivers/clk/imx/clk.h | 3 +++
2 files changed, 14 insertions(+)
diff --gi
Switch the imx_clk_hw_pllv3 function to clk_hw based API, rename
accordingly and add a macro for clk based legacy. This allows us
to move closer to a clear split between consumer and provider clk
APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-pllv3.c | 14 +-
drivers/clk/imx/
Switch the imx_clk_fixup_divider function to clk_hw based API, rename
accordingly and add a macro for clk based legacy. This allows us to
move closer to a clear split between consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-fixup-div.c | 15 ++-
driver
This is basically a 2nd version for this RFC:
https://lkml.org/lkml/2019/3/22/1772
Changes since v1:
* Added the reason for this work in each commit message
* Added clk_hw based initialization for uart_clks in imx6sll driver
Abel Vesa (18):
clk: imx: Add imx_obtain_fixed_clock clk_hw based v
Switch all the clk_busy clock registering functions to clk_hw based API.
Keep around some clk based wrappers to be used by older imx platforms.
This allows us to move closer to a clear split of consumer and provider
clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-busy.c | 30 +
Switch the imx_clk_fixup_mux function to clk_hw based API, rename
accordingly and add a macro for clk based legacy. a macro for clk
based legacy. This allows us to move closer to a clear split between
consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-fixup-mux.c |
Switch the entire clk-imx6sl driver to clk_hw based API.
This allows us to move closer to a clear split between
consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-imx6sl.c | 404 ++-
1 file changed, 209 insertions(+), 195 dele
Switch the entire clk-imx6ul driver to clk_hw based API. This allows us
to move closer to a clear split between consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-imx6ul.c | 574 ++-
1 file changed, 290 insertions(+), 284 dele
Switch the entire clk-imx6sx driver to clk_hw based API. This allows us
to move closer to a clear split between consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-imx6sx.c | 654 ++-
1 file changed, 334 insertions(+), 320 dele
> From: Reshetova, Elena
> > Sent: 30 April 2019 18:51
> ...
> > I guess this is true, so I did a quick implementation now to estimate the
> > performance hits.
> > Here are the preliminary numbers (proper ones will take a bit more time):
> >
> > base: Simple syscall: 0.1761 microseconds
> > get_ra
Switch the entire clk-imx6sll driver to clk_hw based API.
This allows us to move closer to a clear split between
consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-imx6sll.c | 430 ++
1 file changed, 222 insertions(+), 208 del
Switch the imx_clk_gate_exclusive function to clk_hw based API, rename
accordingly and add a macro for clk based legacy. This allows us to move
closer to a clear split between consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-gate-exclusive.c | 17 +++--
Switch the clk_cpu clock registering function to clk_hw based API and add
a macro for clk based legacy. This allows us to move closer to a clear
split between consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-cpu.c | 14 +-
drivers/clk/imx/clk.h |
Switch the entire clk-imx6q driver to clk_hw based API.
Add imx6q_obtain_fixed_clk_hw helper to clean up the registration
of the clocks that are either found in device tree or are assigned
a fixed zero rate. This switch allows us to move closer to a clear
split between consumer and provider clk API
Switch the entire clk-imx7d driver to clk_hw based API. This allows us
to move closer to a clear split between consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-imx7d.c | 983 ++--
1 file changed, 499 insertions(+), 484 delet
Switch all the wrappers to clk_hw based API and rename them to indicate
that. Add macros for clk based legacy users. This allows us to move
closer to a clear split between consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk.h | 91
Switch the imx_clk_pfd function to clk_hw based API, rename accordingly
and add a macro for clk based legacy. This allows us to move closer to
a clear split between consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-pfd.c | 14 +-
drivers/clk/imx/clk.h
Switch the clk_register_gate2 function to clk_hw based API, rename
accordingly and add a macro for clk based legacy. This allows us to
move closer to a clear split between consumer and provider clk APIs.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-gate2.c | 14 +-
drivers/clk/im
The clock IMX6SX_CLK_AXI is not registered at all.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-imx6sx.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/clk/imx/clk-imx6sx.c b/drivers/clk/imx/clk-imx6sx.c
index 91558b0..4ed180c 100644
--- a/drivers/clk/imx/clk-imx6sx.c
+++ b/dri
The clock is registered later than these two re-parentings.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk-imx6q.c | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/clk/imx/clk-imx6q.c b/drivers/clk/imx/clk-imx6q.c
index 708e7c5..c7b671e 100644
--- a/drivers/clk/imx/clk-imx6q.
Enable m4 coprocessor for STM32MP157a-dk1 board.
Signed-off-by: Fabien Dessenne
---
arch/arm/boot/dts/stm32mp157a-dk1.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157a-dk1.dts
b/arch/arm/boot/dts/stm32mp157a-dk1.dts
index 26ce8de..da64ee2 100644
-
This patch introduces a new remoteproc driver to control Cortex-M4
co-processor of the STM32 family.
It provides with the following features:
- start and stop
- dedicated co-processor memory regions registration
- coredump and recovery
Signed-off-by: Fabien Dessenne
Signed-off-by: Ludovic Barre
Declare the M4 remote processor in a sub-node of the mlahb simple bus.
Signed-off-by: Fabien Dessenne
---
arch/arm/boot/dts/stm32mp157c.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi
b/arch/arm/boot/dts/stm32mp157c.dtsi
index c6
STMicrolectronics STM32MP157 MPU are based on a Dual Arm Cortex-A7 core and a
Cortex-M4.
This patchset adds the support of the stm32_rproc driver allowing to control
the M4 remote processor.
Changes since v2:
- Clarified "reg" description
- Change m4 unit adress to 3800
- Renamed "auto_boot" i
Enable m4 coprocessor for STM32MP157c-ed1 board.
Signed-off-by: Fabien Dessenne
---
arch/arm/boot/dts/stm32mp157c-ed1.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c-ed1.dts
b/arch/arm/boot/dts/stm32mp157c-ed1.dts
index acfc5cd..e5a6f40 100644
-
Add the device tree bindings document for the stm32 remoteproc devices.
Signed-off-by: Fabien Dessenne
---
.../devicetree/bindings/remoteproc/stm32-rproc.txt | 63 ++
1 file changed, 63 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/stm32-rproc
Declare reserved memories shared by the processors for STM32MP157c-ed1
board.
Signed-off-by: Fabien Dessenne
---
arch/arm/boot/dts/stm32mp157c-ed1.dts | 42 +++
1 file changed, 42 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c-ed1.dts
b/arch/arm/boot/d
Declare reserved memories shared by the processors for STM32MP157a-dk1
Signed-off-by: Fabien Dessenne
---
arch/arm/boot/dts/stm32mp157a-dk1.dts | 42 +++
1 file changed, 42 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157a-dk1.dts
b/arch/arm/boot/dts/stm3
Document the ML-AHB interconnect for stm32 SoCs.
Signed-off-by: Fabien Dessenne
---
.../devicetree/bindings/arm/stm32/mlahb.txt| 37 ++
1 file changed, 37 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/stm32/mlahb.txt
diff --git a/Documentati
From: Reshetova, Elena
> > Sent: 30 April 2019 18:51
> ...
> > +unsigned char random_get_byte(void)
> > +{
> > +struct rnd_buffer *buffer = &get_cpu_var(stack_rand_offset);
> > +unsigned char res;
> > +
> > +if (buffer->byte_counter >= RANDOM_BUFFER_SIZE) {
> > +get_random_byte
On Thu, May 02, 2019 at 09:28:08AM +0200, Greg Kroah-Hartman wrote:
> On Thu, May 02, 2019 at 09:17:42AM +0200, Greg Kroah-Hartman wrote:
> > On Thu, May 02, 2019 at 07:56:16AM +1000, Tobin C. Harding wrote:
> > > On Sat, Apr 27, 2019 at 09:28:09PM +0200, Greg Kroah-Hartman wrote:
> > > > On Sat, A
Hi Kamal,
Kamal Dasu wrote on Wed, 1 May 2019 13:46:15
-0400:
> If mtd_oops is in progress switch to polling for nand command completion
s/nand/NAND/
> interrupts and use PIO mode wihtout DMA so that the mtd_oops buffer can
> be completely written in the assinged nand partition.
What about:
Adding Jon to CC
On Thu, May 02, 2019 at 09:38:23AM +0200, Johan Hovold wrote:
> On Thu, May 02, 2019 at 12:31:40PM +1000, Tobin C. Harding wrote:
> > kernel-doc comments have a prescribed format. This includes parenthesis
> > on the function name. To be _particularly_ correct we should also
> >
On Wed, Apr 24, 2019 at 01:34:03AM +, Jethro Beekman wrote:
> On 2019-04-17 03:39, Jarkko Sakkinen wrote:
> > diff --git a/arch/x86/include/uapi/asm/sgx.h
> > b/arch/x86/include/uapi/asm/sgx.h
> > index 7bf627ac4958..3b80acde8671 100644
> > --- a/arch/x86/include/uapi/asm/sgx.h
> > +++ b/arch/
On Wed, May 01, 2019 at 09:41:08AM -0700, Linus Torvalds wrote:
> On Mon, Apr 29, 2019 at 7:52 AM Jan Glauber wrote:
> >
> > It turned out the issue we have on ThunderX2 is the file open-close sequence
> > with small read sizes. If the used files are opened read-only the
> > lockref code (enabled
On Fri, Apr 26, 2019 at 02:00:18PM -0700, Sean Christopherson wrote:
> On Thu, Apr 25, 2019 at 04:31:40PM -0700, Xing, Cedric wrote:
> > > While this may format nicely in .rst (I haven't checked), it's damn near
> > > unreadable in its raw form. Escaping '%' in kernel-doc is unresolved at
> > > th
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
samples/Makefile
between commit:
a757ed09d672 ("samples: guard sub-directories with CONFIG options")
from the kbuild tree and commit:
eb364bbe6791 ("samples: show race-free pidfd metadata access")
from the pidfd tree
On Thu, May 02, 2019 at 09:30:44AM +0200, Petr Mladek wrote:
> On Thu 2019-05-02 09:12:32, Greg Kroah-Hartman wrote:
> > On Thu, May 02, 2019 at 12:31:42PM +1000, Tobin C. Harding wrote:
> > > Currently we use custom logic to track kobject initialization. Recently
> > > a predicate function was ad
On Wed 2019-05-01 09:38:03, Tobin C. Harding wrote:
> Hi,
>
> Looks like I've created a bit of confusion trying to fix memleaks in
> calls to kobject_init_and_add(). Its spread over various patches and
> mailing lists so I'm starting a new thread and CC'ing anyone that
> commented on one of those
Hi Miquel,
> Hi Shivamurthy,
>
> Sorry for the long delay I was a bit overloaded.
>
> "Shivamurthy Shastri (sshivamurthy)" wrote
> on
> Tue, 26 Mar 2019 10:51:47 +:
>
> > Fix headers to make way for adding helper functions.
> >
> > Add onfi helper structure.
> >
> > Add helper functions in
On Wed, May 01, 2019 at 05:01:40PM +0100, Will Deacon wrote:
> Hi Jan,
>
> [+Peter and Linus, since they enjoy this stuff]
>
> On Mon, Apr 29, 2019 at 02:52:11PM +, Jan Glauber wrote:
> > I've been looking into performance issues that were reported for several
> > test-cases, for instance an
On Thu, May 02, 2019 at 06:25:39PM +1000, Tobin C. Harding wrote: > Adding Jon
to CC
>
> On Thu, May 02, 2019 at 09:38:23AM +0200, Johan Hovold wrote:
> > On Thu, May 02, 2019 at 12:31:40PM +1000, Tobin C. Harding wrote:
> > > kernel-doc comments have a prescribed format. This includes parenthes
2019年5月2日(木) 16:21 Boris Brezillon :
>
> On Thu, 2 May 2019 15:58:24 +0900
> Tomasz Figa wrote:
>
> > 2019年5月2日(木) 15:55 Boris Brezillon :
> > >
> > > On Thu, 2 May 2019 15:42:59 +0900
> > > Tomasz Figa wrote:
> > >
> > > > 2019年5月2日(木) 15:36 Boris Brezillon :
> > > > >
> > > > > Hi Tomasz,
> > >
On Thu 2019-05-02 12:31:38, Tobin C. Harding wrote:
> Currently error return from kobject_init_and_add() is not followed by a
> call to kobject_put(). This means there is a memory leak.
Strictly speaking there is no real memory leak in this case because
the structures are either static and or fre
If UHS speed modes are enabled, a compatible SD card switches down to
1.8V during enumeration. If after this a software reboot/crash takes
place and on-chip ROM tries to enumerate the SD card, the difference in
IO voltages (host @ 3.3V and card @ 1.8V) may end up damaging the card.
The fix for thi
On Thu 2019-05-02 18:31:27, Tobin C. Harding wrote:
> On Thu, May 02, 2019 at 09:30:44AM +0200, Petr Mladek wrote:
> > On Thu 2019-05-02 09:12:32, Greg Kroah-Hartman wrote:
> > > On Thu, May 02, 2019 at 12:31:42PM +1000, Tobin C. Harding wrote:
> > > > Currently we use custom logic to track kobject
Hi Rob,
On 5/1/19 12:36 AM, Rob Herring wrote:
> On Fri, Apr 19, 2019 at 03:48:07PM +0200, Lukasz Luba wrote:
>> Extend the documenation by events description with new 'event-data-type'
>> field. Add example how the event might be defined in DT.
>
> Why do we need event types in DT? We don't do t
Linus,
The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git
tags/mtd/fixes-for-5.1-rc6
for you to fetch changes up to 9a8f6
On 30/04/2019 20.22, Nick Desaulniers wrote:
> On Mon, Apr 29, 2019 at 10:32 AM Nick Desaulniers
> wrote:
>>
>> On Fri, Apr 26, 2019 at 12:06 PM Rasmus Villemoes
>> wrote:
>>>
>>> Current versions of clang does not like the %c modifier in inline
>>> assembly for targets other than x86, so any DYN
This enables to capture snapshot of controller information via device
coredump machanism, and it helps diagnose and debug issues.
The nvme device coredump is triggered before resetting the controller
caused by I/O timeout, and creates the following coredump files.
- regs: NVMe controller register
Use memory_read_from_buffer() to simplify devcd_readv().
Cc: Johannes Berg
Cc: Keith Busch
Cc: Jens Axboe
Cc: Christoph Hellwig
Cc: Sagi Grimberg
Signed-off-by: Akinobu Mita
---
drivers/base/devcoredump.c | 11 +--
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/driver
This enables to capture snapshot of controller information via device
coredump machanism.
The nvme device coredump creates the following coredump files.
- regs: NVMe controller registers, including each I/O queue doorbell
registers, in nvme-show-regs style text format.
- sq: I/O submissi
The device coredump mechanism currently allows drivers to create only a
single coredump file. If there are several binary blobs to dump, we need
to define a binary format or conver to text format in order to put them
into a single coredump file.
This provides a new function that allows drivers to
This enables the nvme driver to trigger a device coredump before resetting
the controller caused by I/O timeout.
The device coredump helps diagnose and debug issues.
Cc: Johannes Berg
Cc: Keith Busch
Cc: Jens Axboe
Cc: Christoph Hellwig
Cc: Sagi Grimberg
Signed-off-by: Akinobu Mita
---
dri
On Wed, May 01, 2019 at 11:43:00AM -0700, Sodagudi Prasad wrote:
> On 2019-05-01 02:49, Sudeep Holla wrote:
> > On Tue, Apr 30, 2019 at 05:07:31PM -0700, Sodagudi Prasad wrote:
> > > On 2019-04-30 14:44, Sodagudi Prasad wrote:
[...]
> > >
> > > It would nice if there is a config option to reboot
Rob Herring [2019-05-01 15:19:25]:
Hi Rob,
> > + struct property *pp;
...
> > + pp = kzalloc(sizeof(*pp), GFP_KERNEL);
> > + if (!pp)
> > + return NULL;
> > +
> > + pp->name = "nvmem-mac-address";
> > + pp->length = ETH_ALEN;
> > + pp->value = kmemdup(mac, ETH_ALEN, GFP_K
On Thu, May 02, 2019 at 10:34:12AM +0200, Petr Mladek wrote:
> On Wed 2019-05-01 09:38:03, Tobin C. Harding wrote:
> > Hi,
> >
> > Looks like I've created a bit of confusion trying to fix memleaks in
> > calls to kobject_init_and_add(). Its spread over various patches and
> > mailing lists so I'm
On 5/2/19 3:25 AM, Chanwoo Choi wrote:
> Hi Lukasz,
>
> On 19. 5. 1. 오전 6:19, Lukasz Luba wrote:
>> Hi Chanwoo,
>>
>> On 4/30/19 9:34 AM, Chanwoo Choi wrote:
>>> Hi Lukasz,
>>>
>>> On 19. 4. 19. 오후 10:48, Lukasz Luba wrote:
This patch adds posibility to choose what type of data should be c
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/parisc/mm/init.c
between commit:
1fb55c4cf4e6 ("parisc: Enable SPARSEMEM_VMEMMAP")
from the parisc-hd tree and commit:
2e5adbd9e97a ("initramfs: provide a generic free_initrd_mem implementation")
from the
On Thu, May 02, 2019 at 10:50:12AM +0530, Yash Shah wrote:
> On Thu, May 2, 2019 at 6:11 AM Rob Herring wrote:
> >
> > On Tue, Apr 30, 2019 at 09:50:45AM +0530, Yash Shah wrote:
> > > On Fri, Apr 26, 2019 at 3:04 PM Sudeep Holla wrote:
> > > >
> > > > On Fri, Apr 26, 2019 at 11:20:17AM +0530, Yas
Patch series introducing support for ROHM BD70528 PMIC
Resending the series as I forgot Lee from the recipient list of
the original mail.
ROHM BD70528 is a programmable Power Management IC for battery
powered 'ultra low power' systems like the pre-announced NXP
i.MX7 ULP. This patch series introd
Split the bd718x7.h to ROHM common and bd718x7 specific parts
so that we do not need to add same things in every new ROHM
PMIC header. Please note that this change requires changes also
in bd718x7 sub-device drivers for regulators and clk.
Signed-off-by: Matti Vaittinen
Acked-by: Mark Brown
Acke
ROHM BD70528MWV is an ultra-low quiescent current general
purpose single-chip power management IC for battery-powered
portable devices.
Add MFD core which enables chip access for following subdevices:
- regulators/LED drivers
- battery-charger
- gpios
- 32.768kHz cl
ROHM BD70528 is an ultra low power PMIC with similar 32K clk as
bd718x7. Only difference (from clk perspective) is register address.
Add support for controlling BD70528 clk using bd718x7 driver.
Signed-off-by: Matti Vaittinen
Acked-by: Stephen Boyd
---
Changelog v14: No changes
drivers/clk/Kco
Document bindings for regulators (3 bucks, 3 LDOs and 2 LED
drivers) and 4 GPIO pins which can be configured for I/O or
as interrupt sources withe configurable trigger levels.
Signed-off-by: Matti Vaittinen
Reviewed-by: Rob Herring
Acked-by: Linus Walleij
---
Changelog v14: No changes
.../bin
ROHM BD70528 PMIC has 4 GPIO pins. Allow them to be
controlled by GPIO framework.
IRQs are handled by regmap-irq and GPIO driver is not
aware of the irq usage.
Signed-off-by: Matti Vaittinen
Reviewed-by: Linus Walleij
---
Changelog v14: No changes
drivers/gpio/Kconfig| 11 ++
drivers
On 5/1/19 12:33 AM, Rob Herring wrote:
> On Fri, 19 Apr 2019 15:48:05 +0200, Lukasz Luba wrote:
>> This patch add support of a new feature which can be used in DT:
>> Performance Monitoring Unit with defined event data type.
>> In this patch the event data types are defined for Exynos PPMU.
>> T
Support RTC block in ROHM bd70528 power management IC. Support
getting and setting the time and date as well as arming an alarm
which can also be used to wake the PMIC from standby state.
HW supports wake interrupt only for the next 24 hours (sec, minute
and hour information only) so we limit also
ROHM BD70528 PMIC includes battery charger block. Support charger
staus queries and doing few basic settings like input current limit
and charging current.
Signed-off-by: Matti Vaittinen
Acked-by: Sebastian Reichel
---
Changelog v14:
- constify and statictze few structs
- use dev_get_regmap inst
Initial support for watchdog block included in ROHM BD70528
power management IC.
Configurations for low power states are still to be checked.
Signed-off-by: Matti Vaittinen
Acked-by: Guenter Roeck
---
Changelog v14: No changes
drivers/watchdog/Kconfig | 12 ++
drivers/watchdog/Makefile
From: Reshetova, Elena
> Sent: 02 May 2019 09:16
...
> > I'm also guessing that get_cpu_var() disables pre-emption?
>
> Yes, in my understanding:
>
> #define get_cpu_var(var) \
> (*({ \
>
In double buffer mode, during residue calculation, the DMA can
automatically switch to the next transfer. Indeed the CT bit that
gives position in the double buffer can has been updated by the
hardware, during calculation.
In this case the SxNDTR register value can not be trusted.
If a transition i
On Thu, May 2, 2019 at 2:40 PM Sudeep Holla wrote:
>
>
> Sorry if I created confusion. I just wanted a note saying all the properties
> in ePAPR/DeviceTree specification applies for this platform. That would
> help me check if the standard cacheinfo infrastruction works as is or not.
Sure, will a
On 30/04/2019 16:06, Lorenzo Pieralisi wrote:
> On Tue, Mar 12, 2019 at 06:34:55PM +0100, Marc Gonzalez wrote:
>
>> On 12/03/2019 18:18, Marc Gonzalez wrote:
>>
>>> On 12/03/2019 13:42, Stanimir Varbanov wrote:
>>>
I wonder, in case that dw_pcie_setup_rc() already has a write to
PCI_CLAS
1 - 100 of 895 matches
Mail list logo
