Looks good,
Reviewed-by: Johannes Thumshirn
--
Johannes ThumshirnSUSE Labs
jthumsh...@suse.de+49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG
Looks good,
Reviewed-by: Johannes Thumshirn
--
Johannes ThumshirnSUSE Labs
jthumsh...@suse.de+49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG
On (11/24/18 23:28), Tetsuo Handa wrote:
> Since /sys/module/printk/parameters/time can change from N to Y between
> "msg_print_text() called print_prefix() with buf == NULL" and
> "msg_print_text() again calls print_prefix() with buf != NULL", it is not
> safe for print_time() to unconditionally
On 五, 2018-11-23 at 00:17 +0530, Amit Kucheria wrote:
> On Fri, Oct 26, 2018 at 2:21 PM Amit Kucheria rg> wrote:
> >
> >
> > Hi Rui,
> >
> > On Thu, Oct 4, 2018 at 1:22 PM Amit Kucheria > org> wrote:
> > >
> > >
> > > Move the various drivers for Intel platforms into their own
> > > subdir.
On (11/24/18 23:28), Tetsuo Handa wrote:
> Since /sys/module/printk/parameters/time can change from N to Y between
> "msg_print_text() called print_prefix() with buf == NULL" and
> "msg_print_text() again calls print_prefix() with buf != NULL", it is not
> safe for print_time() to unconditionally
On 五, 2018-11-23 at 00:17 +0530, Amit Kucheria wrote:
> On Fri, Oct 26, 2018 at 2:21 PM Amit Kucheria rg> wrote:
> >
> >
> > Hi Rui,
> >
> > On Thu, Oct 4, 2018 at 1:22 PM Amit Kucheria > org> wrote:
> > >
> > >
> > > Move the various drivers for Intel platforms into their own
> > > subdir.
On Mon, Nov 26, 2018 at 11:06:29AM +1100, Stephen Rothwell wrote:
> Introduced by commit
>
> cf8cddd38bab3 ("btrfs: don't abuse REQ_OP_* flags for btrfs_map_block")
>
> exposed by my new use of -Wimplicit-fallthrough
>
> I am not sure why this has only turned up now (as opposed to earlier
>
On Mon, Nov 26, 2018 at 11:06:29AM +1100, Stephen Rothwell wrote:
> Introduced by commit
>
> cf8cddd38bab3 ("btrfs: don't abuse REQ_OP_* flags for btrfs_map_block")
>
> exposed by my new use of -Wimplicit-fallthrough
>
> I am not sure why this has only turned up now (as opposed to earlier
>
On Sun, Nov 25, 2018 at 07:33:54PM +0100, Thomas Gleixner wrote:
> + prctl - Indirect branch speculation is enabled,
> + but mitigation can be enabled via prctl
s/can be/is only/ or "must be".
Thanks,
Dominik
On Sun, Nov 25, 2018 at 07:33:54PM +0100, Thomas Gleixner wrote:
> + prctl - Indirect branch speculation is enabled,
> + but mitigation can be enabled via prctl
s/can be/is only/ or "must be".
Thanks,
Dominik
Use the vendor specific resource mechanism to get the
INTC mapping details from firmware.
pru-software-support-package [1] has been historically using
version 0 for this. However, the data structure is not scaleable
and is not self sufficient.
1) it hard codes number of channel to host mappings
From: Suman Anna
The Programmable Real-Time Unit Subsystem (PRUSS) consists of
dual 32-bit RISC cores (Programmable Real-Time Units, or PRUs)
for program execution. This patch adds a remoteproc platform
driver for managing the individual PRU RISC cores life cycle.
The PRU remoteproc driver uses
From: Tero Kristo
PRU interrupt mapping can now be parsed from devicetree also, from
ti,pru-interrupt-map property. This is an alternative configuration
method in addition to the legacy resource table config. If both are
provided, the config in DT takes precedence.
Signed-off-by: Tero Kristo
From: Suman Anna
The Programmable Real-Time Unit Subsystem (PRUSS) consists of
dual 32-bit RISC cores (Programmable Real-Time Units, or PRUs)
for program execution. This patch adds a remoteproc platform
driver for managing the individual PRU RISC cores life cycle.
The PRU remoteproc driver uses
From: Tero Kristo
PRU interrupt mapping can now be parsed from devicetree also, from
ti,pru-interrupt-map property. This is an alternative configuration
method in addition to the legacy resource table config. If both are
provided, the config in DT takes precedence.
Signed-off-by: Tero Kristo
Use the vendor specific resource mechanism to get the
INTC mapping details from firmware.
pru-software-support-package [1] has been historically using
version 0 for this. However, the data structure is not scaleable
and is not self sufficient.
1) it hard codes number of channel to host mappings
From: Tero Kristo
Add documentation for the Texas Instruments PRU application nodes.
These are used to configure specific user applications for PRU instances.
Signed-off-by: Tero Kristo
[s-a...@ti.com: some binding updates]
Signed-off-by: Suman Anna
Signed-off-by: Roger Quadros
---
From: Tero Kristo
Add two new APIs, pru_rproc_get() and pru_rproc_put(), to the PRU
driver to allow client drivers to acquire and release the remoteproc
device associated with a PRU core. The PRU cores are treated as
resources with only one client owning it at a time.
The pru_rproc_get()
From: Suman Anna
The remoteproc framework handles a fixed set of resource table entries
today. To make it scalable across multiple platforms, it makes sense
for the framework to provide a way for the device specific implementation
to define and handle vendor specific resource types. These
From: Suman Anna
The PRUSS CFG module is represented as a syscon node and is currently
managed by the PRUSS platform driver. Add easy accessor functions to set
GPI mode, MII_RT event enable/disable and XFR (XIN XOUT) enable/disable
to enable the PRUSS Ethernet usecase. These functions reuse the
From: Suman Anna
The PRU remoteproc driver has been enhanced to support the optional
rpmsg stack using the virtio-ring based communication transport
between MPU and a PRU core. This provides support to any firmware
images supporting the virtio devices.
The virtio-ring signalling support is
From: Tero Kristo
Client device node property firmware-name is now used to configure
firmware for the PRU instances. The default firmware is also
restored once releasing the PRU resource.
Signed-off-by: Tero Kristo
Reviewed-by: Roger Quadros
Signed-off-by: Suman Anna
---
From: Tero Kristo
Client device node property ti,pruss-gp-mux-sel can now be used to
configure the GPMUX config value for PRU.
Signed-off-by: Tero Kristo
[s-a...@ti.com: simplify the pru id usage]
Signed-off-by: Suman Anna
---
drivers/remoteproc/pru_rproc.c | 28
From: Suman Anna
Update the PRUSS DT bindings to add the properties required to support the
optional virtio rpmsg stack using the virtio-ring based communication
transport between MPU and a PRU core.
Signed-off-by: Suman Anna
---
.../devicetree/bindings/soc/ti/ti,pruss.txt| 39
Some firmwares expect the OS drivers to configure the CTABLE
entries publishing dynamically allocated memory regions. For
example, the PRU Ethernet firmwares use the C28 and C30 entries
for retrieving the Shared RAM and System SRAM (OCMC) areas
allocated by the PRU Ethernet client driver.
Provide
From: Suman Anna
The remoteproc core creates certain standard debugfs entries,
that does not give a whole lot of useful information for the
PRUs. The PRU remoteproc driver is enhanced to add additional
debugfs entries for PRU. These will be auto-cleaned up when
the parent rproc debug directory
From: Suman Anna
The remoteproc framework handles a fixed set of resource table entries
today. To make it scalable across multiple platforms, it makes sense
for the framework to provide a way for the device specific implementation
to define and handle vendor specific resource types. These
From: Suman Anna
The PRUSS CFG module is represented as a syscon node and is currently
managed by the PRUSS platform driver. Add easy accessor functions to set
GPI mode, MII_RT event enable/disable and XFR (XIN XOUT) enable/disable
to enable the PRUSS Ethernet usecase. These functions reuse the
From: Suman Anna
The PRU remoteproc driver has been enhanced to support the optional
rpmsg stack using the virtio-ring based communication transport
between MPU and a PRU core. This provides support to any firmware
images supporting the virtio devices.
The virtio-ring signalling support is
From: Tero Kristo
Client device node property firmware-name is now used to configure
firmware for the PRU instances. The default firmware is also
restored once releasing the PRU resource.
Signed-off-by: Tero Kristo
Reviewed-by: Roger Quadros
Signed-off-by: Suman Anna
---
From: Tero Kristo
Client device node property ti,pruss-gp-mux-sel can now be used to
configure the GPMUX config value for PRU.
Signed-off-by: Tero Kristo
[s-a...@ti.com: simplify the pru id usage]
Signed-off-by: Suman Anna
---
drivers/remoteproc/pru_rproc.c | 28
From: Suman Anna
Update the PRUSS DT bindings to add the properties required to support the
optional virtio rpmsg stack using the virtio-ring based communication
transport between MPU and a PRU core.
Signed-off-by: Suman Anna
---
.../devicetree/bindings/soc/ti/ti,pruss.txt| 39
Some firmwares expect the OS drivers to configure the CTABLE
entries publishing dynamically allocated memory regions. For
example, the PRU Ethernet firmwares use the C28 and C30 entries
for retrieving the Shared RAM and System SRAM (OCMC) areas
allocated by the PRU Ethernet client driver.
Provide
From: Suman Anna
The remoteproc core creates certain standard debugfs entries,
that does not give a whole lot of useful information for the
PRUs. The PRU remoteproc driver is enhanced to add additional
debugfs entries for PRU. These will be auto-cleaned up when
the parent rproc debug directory
From: Tero Kristo
Add documentation for the Texas Instruments PRU application nodes.
These are used to configure specific user applications for PRU instances.
Signed-off-by: Tero Kristo
[s-a...@ti.com: some binding updates]
Signed-off-by: Suman Anna
Signed-off-by: Roger Quadros
---
From: Tero Kristo
Add two new APIs, pru_rproc_get() and pru_rproc_put(), to the PRU
driver to allow client drivers to acquire and release the remoteproc
device associated with a PRU core. The PRU cores are treated as
resources with only one client owning it at a time.
The pru_rproc_get()
From: Suman Anna
Export an API pru_rproc_get_id() to allow other PRUSS platform
drivers to clients to retrieve the PRU id from a remoteproc handle
associated with a PRU. The new function takes in a struct rproc
pointer as argument.
Signed-off-by: Suman Anna
---
drivers/remoteproc/pru_rproc.c
From: Suman Anna
Export an API pru_rproc_get_id() to allow other PRUSS platform
drivers to clients to retrieve the PRU id from a remoteproc handle
associated with a PRU. The new function takes in a struct rproc
pointer as argument.
Signed-off-by: Suman Anna
---
drivers/remoteproc/pru_rproc.c
Hi,
This is the second part of the series [1] and depends on it.
It adds remoteproc support for the PRU processor cores
present in the PRU-ICSS subsystem on TI SoCs.
The PRU remoteproc driver uses the standard remoteproc core ELF
loader. However, the PRUs do not have a unified address space,
Hi,
This is the second part of the series [1] and depends on it.
It adds remoteproc support for the PRU processor cores
present in the PRU-ICSS subsystem on TI SoCs.
The PRU remoteproc driver uses the standard remoteproc core ELF
loader. However, the PRUs do not have a unified address space,
From: Suman Anna
A new API, rproc_set_firmware() is added to allow the remoteproc platform
drivers and remoteproc client drivers to be able to configure a custom
firmware name that is different from the default name used during
remoteproc registration. This function is being introduced to
From: Suman Anna
The rproc_da_to_va() API is currently used to perform any device
to kernel address translations to meet the different needs of the
remoteproc core/platform drivers (eg: loading). The function also
invokes the da_to_va ops, if present, to allow the remoteproc
platform drivers to
From: Suman Anna
A new API, rproc_set_firmware() is added to allow the remoteproc platform
drivers and remoteproc client drivers to be able to configure a custom
firmware name that is different from the default name used during
remoteproc registration. This function is being introduced to
From: Suman Anna
The rproc_da_to_va() API is currently used to perform any device
to kernel address translations to meet the different needs of the
remoteproc core/platform drivers (eg: loading). The function also
invokes the da_to_va ops, if present, to allow the remoteproc
platform drivers to
Hi,
On 23/11/18 18:24, Tony Lindgren wrote:
> Hi,
>
> * Roger Quadros [181122 11:39]:
>> From: Suman Anna
>> +Example:
>> +
>> +1. /* AM33xx PRU-ICSS */
>> +pruss_soc_bus: pruss_soc_bus@4a326004 {
>> +compatible = "ti,am3356-pruss-soc-bus";
>> +ti,hwmods =
Hi,
On 2018년 11월 23일 18:44, Anand Moon wrote:
> From: Marian Mihailescu
>
> A specific clock rate table is added for VPLL so it is possible
> to set frequency of the VPLL output clock that used by the g3d clock.
>
> Cc: Andrzej Hajda
> Cc: Chanwoo Choi
> Signed-off-by: Marian Mihailescu
>
Hi,
On 23/11/18 18:24, Tony Lindgren wrote:
> Hi,
>
> * Roger Quadros [181122 11:39]:
>> From: Suman Anna
>> +Example:
>> +
>> +1. /* AM33xx PRU-ICSS */
>> +pruss_soc_bus: pruss_soc_bus@4a326004 {
>> +compatible = "ti,am3356-pruss-soc-bus";
>> +ti,hwmods =
Hi,
On 2018년 11월 23일 18:44, Anand Moon wrote:
> From: Marian Mihailescu
>
> A specific clock rate table is added for VPLL so it is possible
> to set frequency of the VPLL output clock that used by the g3d clock.
>
> Cc: Andrzej Hajda
> Cc: Chanwoo Choi
> Signed-off-by: Marian Mihailescu
>
kernel/dma/Kconfig globally defines HAS_DMA as follows:
config HAS_DMA
bool
depends on !NO_DMA
default y
Signed-off-by: Masahiro Yamada
---
arch/nios2/Kconfig | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/nios2/Kconfig b/arch/nios2/Kconfig
index
kernel/dma/Kconfig globally defines HAS_DMA as follows:
config HAS_DMA
bool
depends on !NO_DMA
default y
Signed-off-by: Masahiro Yamada
---
arch/nios2/Kconfig | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/nios2/Kconfig b/arch/nios2/Kconfig
index
On 11/26/18 3:01 AM, Matthew Wilcox wrote:
> On Mon, Nov 26, 2018 at 07:58:23AM +0800, Yang Yang wrote:
>> When si_mem_available() calculates 'available', it takes SWAP
>> into account. But if CONFIG_SWAP is N or SWAP is off(some embedded system
>> would like to do that), there is no need to
On 11/26/18 3:01 AM, Matthew Wilcox wrote:
> On Mon, Nov 26, 2018 at 07:58:23AM +0800, Yang Yang wrote:
>> When si_mem_available() calculates 'available', it takes SWAP
>> into account. But if CONFIG_SWAP is N or SWAP is off(some embedded system
>> would like to do that), there is no need to
On Wed, 21 Nov 2018 20:27:16 -0500
Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> The static inline function task_curr_ret_stack() is unused, remove it.
This looks able to be applied without this series. I think we should
apply this to for-next branch?
Reviewed-by: Masami
On Wed, 21 Nov 2018 20:27:16 -0500
Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> The static inline function task_curr_ret_stack() is unused, remove it.
This looks able to be applied without this series. I think we should
apply this to for-next branch?
Reviewed-by: Masami
Hi Anand,
CLK_DOUT_ACLK_G3D is the clock for GPU h/w and it requires the
buck4_reg("vdd_g3d").
bus_wcore uses the buck3_reg("vdd_int"). bus_wcore and bus_g3d don't share the
same voltage line. It is wrong to make 'bus_g3d' as the child of 'bus_wcore'
because of using the different regulator.
Hi Anand,
CLK_DOUT_ACLK_G3D is the clock for GPU h/w and it requires the
buck4_reg("vdd_g3d").
bus_wcore uses the buck3_reg("vdd_int"). bus_wcore and bus_g3d don't share the
same voltage line. It is wrong to make 'bus_g3d' as the child of 'bus_wcore'
because of using the different regulator.
On Fri, 2018-11-23 at 22:23 -0200, Matheus Tavares wrote:
> Move ad2s90 resolver driver out of staging to the main tree.
>
Acked-by: Alexandru Ardelean
> Signed-off-by: Matheus Tavares
> Signed-off-by: Victor Colombo
> ---
> Changes in v3:
> - none
>
> Changes in v2:
> - Disabled git move
On Fri, 2018-11-23 at 22:23 -0200, Matheus Tavares wrote:
> Move ad2s90 resolver driver out of staging to the main tree.
>
Acked-by: Alexandru Ardelean
> Signed-off-by: Matheus Tavares
> Signed-off-by: Victor Colombo
> ---
> Changes in v3:
> - none
>
> Changes in v2:
> - Disabled git move
On Thu, 22 Nov 2018 22:11:33 -0800
Joel Fernandes wrote:
> On Wed, Nov 21, 2018 at 08:27:14PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (VMware)"
> >
> > To make the function graph infrastructure more managable, the code needs to
> > be in its own file (fgraph.c). Move the code
On Thu, 22 Nov 2018 22:11:33 -0800
Joel Fernandes wrote:
> On Wed, Nov 21, 2018 at 08:27:14PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (VMware)"
> >
> > To make the function graph infrastructure more managable, the code needs to
> > be in its own file (fgraph.c). Move the code
A Kconfig property can have an optional if-expression, which describes
its visibility. The property is visible when the if-expression part is
evaluated to 'y' or 'm'.
The 'select' and 'imply' properties are internally converted to reverse
dependencies, but they are wrongly converted if they have
A Kconfig property can have an optional if-expression, which describes
its visibility. The property is visible when the if-expression part is
evaluated to 'y' or 'm'.
The 'select' and 'imply' properties are internally converted to reverse
dependencies, but they are wrongly converted if they have
Add a test-case for the fixed reverse dependency handling.
Signed-off-by: Masahiro Yamada
---
.../kconfig/tests/revdep_with_tristate_if/Kconfig | 21 +
.../tests/revdep_with_tristate_if/__init__.py | 14 ++
Add a test-case for the fixed reverse dependency handling.
Signed-off-by: Masahiro Yamada
---
.../kconfig/tests/revdep_with_tristate_if/Kconfig | 21 +
.../tests/revdep_with_tristate_if/__init__.py | 14 ++
On Sun, 25 Nov 2018, Andy Lutomirski wrote:
> > On Nov 25, 2018, at 2:20 PM, Thomas Gleixner wrote:
> > On Sun, 25 Nov 2018, Andi Kleen wrote:
> >
> >>> The current check whether two tasks belong to the same context is using
> >>> the
> >>> tasks context id. While correct, it's simpler to use
On Sun, 25 Nov 2018, Andy Lutomirski wrote:
> > On Nov 25, 2018, at 2:20 PM, Thomas Gleixner wrote:
> > On Sun, 25 Nov 2018, Andi Kleen wrote:
> >
> >>> The current check whether two tasks belong to the same context is using
> >>> the
> >>> tasks context id. While correct, it's simpler to use
On Fri, Nov 23, 2018 at 04:00:08PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the pull request for 4.20 -rc below.
>
> It includes tuning parameter fix in qcom-qusb2 PHY driver, dt-bindings fix
> for phy-qcom-qmp and a fix for randconfig error in uniphier-pcie.
>
> Consider
When macb device is suspended and system is powered down, the clocks
are removed and hence macb should be closed gracefully and restored
upon resume. This patch does the same by switching off the net device,
suspending phy and performing necessary cleanup of interrupts and BDs.
Upon resume, all
On Fri, Nov 23, 2018 at 04:00:08PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the pull request for 4.20 -rc below.
>
> It includes tuning parameter fix in qcom-qusb2 PHY driver, dt-bindings fix
> for phy-qcom-qmp and a fix for randconfig error in uniphier-pcie.
>
> Consider
When macb device is suspended and system is powered down, the clocks
are removed and hence macb should be closed gracefully and restored
upon resume. This patch does the same by switching off the net device,
suspending phy and performing necessary cleanup of interrupts and BDs.
Upon resume, all
On Mon, Nov 26, 2018 at 10:37:08AM +1100, Benjamin Herrenschmidt wrote:
> Hi Greg !
>
> Here are two very minor fixes for FSI. One from Arnd is a Kconfig fixup
> and has been rusting away in my tree for a while (I had forgotten about
> it). The other one just removes a duplicate #include,
On Mon, Nov 26, 2018 at 10:37:08AM +1100, Benjamin Herrenschmidt wrote:
> Hi Greg !
>
> Here are two very minor fixes for FSI. One from Arnd is a Kconfig fixup
> and has been rusting away in my tree for a while (I had forgotten about
> it). The other one just removes a duplicate #include,
On Sun, Nov 25, 2018 at 10:47:34PM -0500, nimrud wrote:
> This patch adds an option to compile-in a high resolution and large
> Terminus (ter16x32) bitmap console font for use with HiDPI and Retina screens.
>
> The font was convereted from standard Terminus ter-i32b.psf (size 16x32)
> with the
On Sun, Nov 25, 2018 at 10:47:34PM -0500, nimrud wrote:
> This patch adds an option to compile-in a high resolution and large
> Terminus (ter16x32) bitmap console font for use with HiDPI and Retina screens.
>
> The font was convereted from standard Terminus ter-i32b.psf (size 16x32)
> with the
On Sun, Nov 25, 2018 at 10:47:34PM -0500, nimrud wrote:
> This patch adds an option to compile-in a high resolution and large
> Terminus (ter16x32) bitmap console font for use with HiDPI and Retina screens.
>
> The font was convereted from standard Terminus ter-i32b.psf (size 16x32)
> with the
On Sun, Nov 25, 2018 at 10:47:34PM -0500, nimrud wrote:
> This patch adds an option to compile-in a high resolution and large
> Terminus (ter16x32) bitmap console font for use with HiDPI and Retina screens.
>
> The font was convereted from standard Terminus ter-i32b.psf (size 16x32)
> with the
Hi Kees,
On Sun, 25 Nov 2018 21:48:10 -0800 Kees Cook wrote:
>
> On Sun, Nov 25, 2018 at 4:52 PM Stephen Rothwell
> wrote:
> >
> > On Sun, 25 Nov 2018 18:31:40 -0600 Steve French wrote:
> >
> > >
> > > Both of those cases are intentional fallthroughs and there are
> > > existing comments
Hi Kees,
On Sun, 25 Nov 2018 21:48:10 -0800 Kees Cook wrote:
>
> On Sun, Nov 25, 2018 at 4:52 PM Stephen Rothwell
> wrote:
> >
> > On Sun, 25 Nov 2018 18:31:40 -0600 Steve French wrote:
> >
> > >
> > > Both of those cases are intentional fallthroughs and there are
> > > existing comments
On Sun, 25 Nov 2018, Andi Kleen wrote:
> On Sun, Nov 25, 2018 at 11:20:50PM +0100, Thomas Gleixner wrote:
> > On Sun, 25 Nov 2018, Andi Kleen wrote:
> >
> > > > The current check whether two tasks belong to the same context is using
> > > > the
> > > > tasks context id. While correct, it's
On Sun, 25 Nov 2018, Andi Kleen wrote:
> On Sun, Nov 25, 2018 at 11:20:50PM +0100, Thomas Gleixner wrote:
> > On Sun, 25 Nov 2018, Andi Kleen wrote:
> >
> > > > The current check whether two tasks belong to the same context is using
> > > > the
> > > > tasks context id. While correct, it's
Hi Vinod,
On Tue, 6 Nov 2018 at 13:01, Baolin Wang wrote:
>
> This patchset removes the direction usage from struct dma_slave_config,
> and add one new field to save the direction. It also fixes some issues
> for link-list transfer. Moreover this patchset adds new 2-stage transfer
> support for
Hi Vinod,
On Tue, 6 Nov 2018 at 13:01, Baolin Wang wrote:
>
> This patchset removes the direction usage from struct dma_slave_config,
> and add one new field to save the direction. It also fixes some issues
> for link-list transfer. Moreover this patchset adds new 2-stage transfer
> support for
Hi Bjorn / Sean,
Any comments?
Thanks,
Sundeep
On Mon, Nov 19, 2018 at 6:44 PM wrote:
>
> From: Subbaraya Sundeep
>
> As per the spec, bridges with EA capability work
> with fixed secondary and subordinate bus numbers.
> Hence assign bus numbers to bridges from EA if the
> capability exists.
Hi Bjorn / Sean,
Any comments?
Thanks,
Sundeep
On Mon, Nov 19, 2018 at 6:44 PM wrote:
>
> From: Subbaraya Sundeep
>
> As per the spec, bridges with EA capability work
> with fixed secondary and subordinate bus numbers.
> Hence assign bus numbers to bridges from EA if the
> capability exists.
Hi Boris and Miquel,
How about the v7 patch?
On 2018/11/17 0:40, Jianxin Pan wrote:
These two patches try to add initial NAND driver support for Amlogic Meson
SoCs, current it has been tested on GXL(p212) and AXG(s400) platform.
Changes since V6 at [7]
- use timings->tBERS_max as the
Hi Boris and Miquel,
How about the v7 patch?
On 2018/11/17 0:40, Jianxin Pan wrote:
These two patches try to add initial NAND driver support for Amlogic Meson
SoCs, current it has been tested on GXL(p212) and AXG(s400) platform.
Changes since V6 at [7]
- use timings->tBERS_max as the
Hi Pavel,
On Mon, 26 Nov 2018 at 05:48, Pavel Machek wrote:
>
> Hi!
>
> > Our charger manager can optimize the battery capacity periodically, so
> > we can save last battery capacity into registers. Then next system
> > power-on, we can read the last saved battery capacity as the initial
> >
Hi Pavel,
On Mon, 26 Nov 2018 at 05:48, Pavel Machek wrote:
>
> Hi!
>
> > Our charger manager can optimize the battery capacity periodically, so
> > we can save last battery capacity into registers. Then next system
> > power-on, we can read the last saved battery capacity as the initial
> >
Hi Pavel,
On Mon, 26 Nov 2018 at 05:45, Pavel Machek wrote:
>
> On Wed 2018-11-14 17:07:06, Baolin Wang wrote:
> > From: Yuanjiang Yu
> >
> > Add low voltage alarm support to make sure the battery capacity
> > more accurate in lower voltage stage.
> >
> > Signed-off-by: Yuanjiang Yu
> >
Hi Pavel,
On Mon, 26 Nov 2018 at 05:45, Pavel Machek wrote:
>
> On Wed 2018-11-14 17:07:06, Baolin Wang wrote:
> > From: Yuanjiang Yu
> >
> > Add low voltage alarm support to make sure the battery capacity
> > more accurate in lower voltage stage.
> >
> > Signed-off-by: Yuanjiang Yu
> >
The objcopy only emits loadable sections when creating flat kernel
Image. To have minimal possible size of flat kernel Image, we should
have all non-loadable sections after loadable sections.
Currently, execption table section (loadable section) is after BSS
section (non-loadable section) in the
The objcopy only emits loadable sections when creating flat kernel
Image. To have minimal possible size of flat kernel Image, we should
have all non-loadable sections after loadable sections.
Currently, execption table section (loadable section) is after BSS
section (non-loadable section) in the
And I forgot to actually Cc Petr and Steven...
Top-posting.
---
Hi,
Cc-ing Petr and Steven
On (11/25/18 01:13), Joe Perches wrote:
> commit 04b8eb7a4ccd ("symbol lookup: introduce
> dereference_symbol_descriptor()}"
>
> deprecated vsprintf extension %pf and %pF.
>
> There are
And I forgot to actually Cc Petr and Steven...
Top-posting.
---
Hi,
Cc-ing Petr and Steven
On (11/25/18 01:13), Joe Perches wrote:
> commit 04b8eb7a4ccd ("symbol lookup: introduce
> dereference_symbol_descriptor()}"
>
> deprecated vsprintf extension %pf and %pF.
>
> There are
On 26-11-18, 02:59, Anson Huang wrote:
> Put return value checks of calling imx6ul_opp_check_speed_grading()
> into one block to save one condition block for normal case.
>
> Signed-off-by: Anson Huang
> ---
> drivers/cpufreq/imx6q-cpufreq.c | 5 +++--
> 1 file changed, 3 insertions(+), 2
On 26-11-18, 02:59, Anson Huang wrote:
> Put return value checks of calling imx6ul_opp_check_speed_grading()
> into one block to save one condition block for normal case.
>
> Signed-off-by: Anson Huang
> ---
> drivers/cpufreq/imx6q-cpufreq.c | 5 +++--
> 1 file changed, 3 insertions(+), 2
On 26-11-18, 02:59, Anson Huang wrote:
> In voltage scale down path, the return value is NOT
> used at all, remove them to simplify the code.
>
> Signed-off-by: Anson Huang
> ---
> drivers/cpufreq/imx6q-cpufreq.c | 12 +++-
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff
On 26-11-18, 02:59, Anson Huang wrote:
> In voltage scale down path, the return value is NOT
> used at all, remove them to simplify the code.
>
> Signed-off-by: Anson Huang
> ---
> drivers/cpufreq/imx6q-cpufreq.c | 12 +++-
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff
On 23-11-18, 11:32, Daniel Lezcano wrote:
> On 23/11/2018 11:04, Viresh Kumar wrote:
> > On 22-11-18, 13:36, Daniel Lezcano wrote:
> >> In the case of asymmetric SoC with the same micro-architecture, we
> >> have a group of CPUs with smaller OPPs than the other group. One
> >> example is the
On 23-11-18, 11:32, Daniel Lezcano wrote:
> On 23/11/2018 11:04, Viresh Kumar wrote:
> > On 22-11-18, 13:36, Daniel Lezcano wrote:
> >> In the case of asymmetric SoC with the same micro-architecture, we
> >> have a group of CPUs with smaller OPPs than the other group. One
> >> example is the
1 - 100 of 574 matches
Mail list logo
