Hi Neil,
Am Freitag, den 20.05.2016, 14:21 +0200 schrieb Neil Armstrong:
> Use the brand new devm_reset_controller_register() API to get rid of
> the platform driver remove callback.
>
> Signed-off-by: Neil Armstrong
> ---
> drivers/reset/reset-oxnas.c | 12
On 05/20/2016 03:02 PM, Philipp Zabel wrote:
> Hi Neil,
>
> Am Freitag, den 20.05.2016, 14:21 +0200 schrieb Neil Armstrong:
>> Use the brand new devm_reset_controller_register() API to get rid of
>> the platform driver remove callback.
>>
>> Signed-off-by: Neil Armstrong
Hi Neil,
Am Freitag, den 20.05.2016, 14:21 +0200 schrieb Neil Armstrong:
> Use the brand new devm_reset_controller_register() API to get rid of
> the platform driver remove callback.
>
> Signed-off-by: Neil Armstrong
> ---
> drivers/reset/reset-oxnas.c | 12 +---
> 1 file changed, 1
On 05/20/2016 03:02 PM, Philipp Zabel wrote:
> Hi Neil,
>
> Am Freitag, den 20.05.2016, 14:21 +0200 schrieb Neil Armstrong:
>> Use the brand new devm_reset_controller_register() API to get rid of
>> the platform driver remove callback.
>>
>> Signed-off-by: Neil Armstrong
>> ---
>>
On Fri, May 20, 2016 at 03:03:25PM +0200, Heiko Carstens wrote:
> On Fri, May 20, 2016 at 05:52:16PM +0530, Muhammad Falak R Wani wrote:
> > Use memdup_user to duplicate a memory region from user-space to
> > kernel-space, instead of open coding using kmalloc & copy_from_user.
> >
> >
On Fri, May 20, 2016 at 03:03:25PM +0200, Heiko Carstens wrote:
> On Fri, May 20, 2016 at 05:52:16PM +0530, Muhammad Falak R Wani wrote:
> > Use memdup_user to duplicate a memory region from user-space to
> > kernel-space, instead of open coding using kmalloc & copy_from_user.
> >
> >
From: Leif Lindholm
We have multiple "earlycon" early_param handlers - merge the DT one into
the main earlycon one. It's a cleanup that also will be useful
to defer setting up DT console until ACPI/DT decision is made.
Rename the exported function to avoid clashing
SBBR mentions SPCR as a mandatory ACPI table. So enable it for ARM64
Earlycon should be set up as early as possible. ACPI boot tables are
mapped in arch/arm64/kernel/acpi.c:acpi_boot_table_init() that
is called from setup_arch() and that's where we parse SPCR.
So it has to be opted-in per-arch.
arch. When
ACPI_SPCR_TABLE is defined initialization of DT earlycon is deferred until the
DT/ACPI decision is done.
Implement console_match() for pl011.
Based on the work by Leif Lindholm [3]
Thanks to Peter Hurley for explaining how this should work.
Should be applied to next-20160520
Tested on QEMU and Thun
From: Leif Lindholm
We have multiple "earlycon" early_param handlers - merge the DT one into
the main earlycon one. It's a cleanup that also will be useful
to defer setting up DT console until ACPI/DT decision is made.
Rename the exported function to avoid clashing with the function from
SBBR mentions SPCR as a mandatory ACPI table. So enable it for ARM64
Earlycon should be set up as early as possible. ACPI boot tables are
mapped in arch/arm64/kernel/acpi.c:acpi_boot_table_init() that
is called from setup_arch() and that's where we parse SPCR.
So it has to be opted-in per-arch.
arch. When
ACPI_SPCR_TABLE is defined initialization of DT earlycon is deferred until the
DT/ACPI decision is done.
Implement console_match() for pl011.
Based on the work by Leif Lindholm [3]
Thanks to Peter Hurley for explaining how this should work.
Should be applied to next-20160520
Tested on QEMU and Thun
On Thu 19-05-16 15:11:23, David Rientjes wrote:
> If page migration fails due to -ENOMEM, nr_failed should still be
> incremented for proper statistics.
>
> This was encountered recently when all page migration vmstats showed 0,
> and inferred that migrate_pages() was never called, although in
On Thu 19-05-16 15:11:23, David Rientjes wrote:
> If page migration fails due to -ENOMEM, nr_failed should still be
> incremented for proper statistics.
>
> This was encountered recently when all page migration vmstats showed 0,
> and inferred that migrate_pages() was never called, although in
This patch adds function pl011_console_match() that implements
method match of struct console. It allows to match consoles against
data specified in a string, for example taken from command line or
compiled by ACPI SPCR table handler.
Signed-off-by: Aleksey Makarov
'ARM Server Base Boot Requiremets' [1] mentions SPCR (Serial Port
Console Redirection Table) [2] as a mandatory ACPI table that
specifies the configuration of serial console.
Defer initialization of DT earlycon until ACPI/DT decision is made.
Parse the ACPI SPCR table, setup earlycon if
在 2016/5/20 20:57, Caesar Wang 写道:
于 2016年05月20日 20:35, Shawn Lin 写道:
在 2016/5/20 7:56, Caesar Wang 写道:
That's seem the incorrect string to match the spi driver.
Will it break the backward compatibility for some dtb if not
falling back to "rockchip,rockchip-spi" ?
The rk3036 shouldn't
This patch adds function pl011_console_match() that implements
method match of struct console. It allows to match consoles against
data specified in a string, for example taken from command line or
compiled by ACPI SPCR table handler.
Signed-off-by: Aleksey Makarov
Reviewed-by: Peter Hurley
'ARM Server Base Boot Requiremets' [1] mentions SPCR (Serial Port
Console Redirection Table) [2] as a mandatory ACPI table that
specifies the configuration of serial console.
Defer initialization of DT earlycon until ACPI/DT decision is made.
Parse the ACPI SPCR table, setup earlycon if
在 2016/5/20 20:57, Caesar Wang 写道:
于 2016年05月20日 20:35, Shawn Lin 写道:
在 2016/5/20 7:56, Caesar Wang 写道:
That's seem the incorrect string to match the spi driver.
Will it break the backward compatibility for some dtb if not
falling back to "rockchip,rockchip-spi" ?
The rk3036 shouldn't
d_type check requires successful creation of workdir as iterates
through work dir and expects work dir to be present in it. If that's
not the case, this check will always return d_type not supported even
if underlying filesystem might be supporting it.
So don't do this check if work dir creation
Hi,
On 05/19/2016 05:10 PM, Peter Zijlstra wrote:
> On Wed, May 18, 2016 at 11:11:51PM +0200, Rafael J. Wysocki wrote:
>> On Wed, May 18, 2016 at 2:53 PM, Shilpasri G Bhat
>> wrote:
>>> This patch adds driver callback for fast_switch and below observations
>>> on
d_type check requires successful creation of workdir as iterates
through work dir and expects work dir to be present in it. If that's
not the case, this check will always return d_type not supported even
if underlying filesystem might be supporting it.
So don't do this check if work dir creation
Hi,
On 05/19/2016 05:10 PM, Peter Zijlstra wrote:
> On Wed, May 18, 2016 at 11:11:51PM +0200, Rafael J. Wysocki wrote:
>> On Wed, May 18, 2016 at 2:53 PM, Shilpasri G Bhat
>> wrote:
>>> This patch adds driver callback for fast_switch and below observations
>>> on schedutil governor are done with
Am Freitag, 20. Mai 2016, 20:35:53 schrieb Shawn Lin:
> 在 2016/5/20 7:56, Caesar Wang 写道:
> > That's seem the incorrect string to match the spi driver.
>
> Will it break the backward compatibility for some dtb if not
> falling back to "rockchip,rockchip-spi" ?
in what dtb did you see
Am Freitag, 20. Mai 2016, 20:35:53 schrieb Shawn Lin:
> 在 2016/5/20 7:56, Caesar Wang 写道:
> > That's seem the incorrect string to match the spi driver.
>
> Will it break the backward compatibility for some dtb if not
> falling back to "rockchip,rockchip-spi" ?
in what dtb did you see
On Wed, May 18, 2016 at 4:59 PM, Dmitry Torokhov
wrote:
> On Wed, May 18, 2016 at 11:44:04AM -0500, Rob Herring wrote:
>> On Mon, May 16, 2016 at 01:54:53PM -0700, Grant Grundler wrote:
>> > From: Daniel Hung-yu Wu
>> >
>> > Add binding for Atmel
On Wed, May 18, 2016 at 4:59 PM, Dmitry Torokhov
wrote:
> On Wed, May 18, 2016 at 11:44:04AM -0500, Rob Herring wrote:
>> On Mon, May 16, 2016 at 01:54:53PM -0700, Grant Grundler wrote:
>> > From: Daniel Hung-yu Wu
>> >
>> > Add binding for Atmel Capacitive Touch Button device.
>> >
>> >
于 2016年05月20日 20:35, Shawn Lin 写道:
在 2016/5/20 7:56, Caesar Wang 写道:
That's seem the incorrect string to match the spi driver.
Will it break the backward compatibility for some dtb if not
falling back to "rockchip,rockchip-spi" ?
The rk3036 shouldn't work if you read the
于 2016年05月20日 20:35, Shawn Lin 写道:
在 2016/5/20 7:56, Caesar Wang 写道:
That's seem the incorrect string to match the spi driver.
Will it break the backward compatibility for some dtb if not
falling back to "rockchip,rockchip-spi" ?
The rk3036 shouldn't work if you read the
在 2016/5/18 22:41, Caesar Wang 写道:
The 2nd additional region is the GIC virtual cpu interface register
base and size.
As the gic400 of rk3368 says, the cpu interface register map as below
:
-0x GICC_CTRL
.
.
.
-0x00fc GICC_IIDR
-0x1000 GICC_IDR
Obviously, the region size should be
在 2016/5/18 22:41, Caesar Wang 写道:
The 2nd additional region is the GIC virtual cpu interface register
base and size.
As the gic400 of rk3368 says, the cpu interface register map as below
:
-0x GICC_CTRL
.
.
.
-0x00fc GICC_IIDR
-0x1000 GICC_IDR
Obviously, the region size should be
On Fri, May 20, 2016 at 05:51:02PM +0530, Muhammad Falak R Wani wrote:
> Use memdup_user to duplicate a memory region from user-space to
> kernel-space, instead of open coding using kmalloc & copy_from_user.
>
> Signed-off-by: Muhammad Falak R Wani
Acked-by: Richard
On Fri, May 20, 2016 at 05:51:02PM +0530, Muhammad Falak R Wani wrote:
> Use memdup_user to duplicate a memory region from user-space to
> kernel-space, instead of open coding using kmalloc & copy_from_user.
>
> Signed-off-by: Muhammad Falak R Wani
Acked-by: Richard Cochran
On Fri, May 20, 2016 at 02:24:14PM +0200, Arnd Bergmann wrote:
> On Thursday 19 May 2016 14:08:43 Andy Gross wrote:
> > I'd rather do something like what we did for the GSBI. It needed to
> > change some phy related bits in the TCSR as well. We defined the TCSR
> > as a syscon, with binding
On Fri, May 20, 2016 at 02:24:14PM +0200, Arnd Bergmann wrote:
> On Thursday 19 May 2016 14:08:43 Andy Gross wrote:
> > I'd rather do something like what we did for the GSBI. It needed to
> > change some phy related bits in the TCSR as well. We defined the TCSR
> > as a syscon, with binding
On Mon, May 9, 2016 at 9:17 AM, Vitaly Wool wrote:
> This patch introduces z3fold, a special purpose allocator for storing
> compressed pages. It is designed to store up to three compressed pages per
> physical page. It is a ZBUD derivative which allows for higher
On Mon, May 9, 2016 at 9:17 AM, Vitaly Wool wrote:
> This patch introduces z3fold, a special purpose allocator for storing
> compressed pages. It is designed to store up to three compressed pages per
> physical page. It is a ZBUD derivative which allows for higher compression
> ratio keeping the
On Mon, 2016-05-16 at 05:29 +, Chuah, Kim Tatt wrote:
> > On Fri, 2016-05-13 at 18:15 +0800, kbuild test robot wrote:
> > Peter, what happened to your DMA series in the linux-next? Did I
> > miss any
> > discussion related?
> >
> Hi Andy,
> The error occurs when CONFIG_8250_MID is set to
On Mon, 2016-05-16 at 05:29 +, Chuah, Kim Tatt wrote:
> > On Fri, 2016-05-13 at 18:15 +0800, kbuild test robot wrote:
> > Peter, what happened to your DMA series in the linux-next? Did I
> > miss any
> > discussion related?
> >
> Hi Andy,
> The error occurs when CONFIG_8250_MID is set to
Hi Anju,
Please see my comments below,
On Thu, 19 May 2016 20:40:39 +0530
Anju T wrote:
> ppc_get_optinsn_slot() and ppc_free_optinsn_slot() are
> geared towards the allocation and freeing of memory from
> the area reserved for detour buffer.
>
> Signed-off-by: Anju
Hi Anju,
Please see my comments below,
On Thu, 19 May 2016 20:40:39 +0530
Anju T wrote:
> ppc_get_optinsn_slot() and ppc_free_optinsn_slot() are
> geared towards the allocation and freeing of memory from
> the area reserved for detour buffer.
>
> Signed-off-by: Anju T
> ---
>
Hi Dave,
Are you okay with taking this into net-next?
I no longer take away the ability to do connect(), but now it does nothing
more than specify a default address and mark the socket as being client
only. As before, the default address is overridden if sendmsg() is given
an address.
The
Hi Dave,
Are you okay with taking this into net-next?
I no longer take away the ability to do connect(), but now it does nothing
more than specify a default address and mark the socket as being client
only. As before, the default address is overridden if sendmsg() is given
an address.
The
在 2016/5/20 7:56, Caesar Wang 写道:
That's seem the incorrect string to match the spi driver.
Will it break the backward compatibility for some dtb if not
falling back to "rockchip,rockchip-spi" ?
Fixes commit f629fcfab2cd
("ARM: dts: rockchip: support the spi for rk3036")
Signed-off-by:
在 2016/5/20 7:56, Caesar Wang 写道:
That's seem the incorrect string to match the spi driver.
Will it break the backward compatibility for some dtb if not
falling back to "rockchip,rockchip-spi" ?
Fixes commit f629fcfab2cd
("ARM: dts: rockchip: support the spi for rk3036")
Signed-off-by:
Because the HDLCD driver acts as a component master it can end
up enabling the runtime PM functionality before the encoders
are initialised. This can cause crashes if the component slave
never probes (missing module) or if the PM operations kick in
before the probe finishes.
Move the enabling of
Because the HDLCD driver acts as a component master it can end
up enabling the runtime PM functionality before the encoders
are initialised. This can cause crashes if the component slave
never probes (missing module) or if the PM operations kick in
before the probe finishes.
Move the enabling of
Muhammad Falak R Wani, on Fri 20 May 2016 17:53:28 +0530, wrote:
> Use memdup_user to duplicate a memory region from user-space to
> kernel-space, instead of open coding using kmalloc & copy_from_user.
>
> Signed-off-by: Muhammad Falak R Wani
Reviewed-by: Samuel Thibault
Muhammad Falak R Wani, on Fri 20 May 2016 17:53:28 +0530, wrote:
> Use memdup_user to duplicate a memory region from user-space to
> kernel-space, instead of open coding using kmalloc & copy_from_user.
>
> Signed-off-by: Muhammad Falak R Wani
Reviewed-by: Samuel Thibault
> ---
>
On Friday 20 May 2016 14:21:37 Neil Armstrong wrote:
> Use the brand new devm_reset_controller_register() API to get rid of
> the platform driver remove callback.
>
> Signed-off-by: Neil Armstrong
> ---
> drivers/reset/reset-oxnas.c | 12 +---
> 1 file changed,
On Friday 20 May 2016 14:21:37 Neil Armstrong wrote:
> Use the brand new devm_reset_controller_register() API to get rid of
> the platform driver remove callback.
>
> Signed-off-by: Neil Armstrong
> ---
> drivers/reset/reset-oxnas.c | 12 +---
> 1 file changed, 1 insertion(+), 11
On 20/05/16 14:20, Neil Armstrong wrote:
> On 05/20/2016 12:04 PM, Carlo Caione wrote:
> > On 20/05/16 11:10, Neil Armstrong wrote:
> >> On 05/20/2016 11:04 AM, Carlo Caione wrote:
> >>> On 20/05/16 10:27, Neil Armstrong wrote:
> This patch adds the platform driver for the Amlogic Meson GXBB
On 20/05/16 14:20, Neil Armstrong wrote:
> On 05/20/2016 12:04 PM, Carlo Caione wrote:
> > On 20/05/16 11:10, Neil Armstrong wrote:
> >> On 05/20/2016 11:04 AM, Carlo Caione wrote:
> >>> On 20/05/16 10:27, Neil Armstrong wrote:
> This patch adds the platform driver for the Amlogic Meson GXBB
On 05/20/2016 02:22 PM, Carlo Caione wrote:
> On 20/05/16 14:19, Neil Armstrong wrote:
>
> [...]
> Missing #include ?
>
> Thanks,
>
Shouldn't we wait until the reset bindings are actually used in the dtsi ?
I'm quite sure kevin will post it with the Ethernet nodes.
On 05/20/2016 02:22 PM, Carlo Caione wrote:
> On 20/05/16 14:19, Neil Armstrong wrote:
>
> [...]
> Missing #include ?
>
> Thanks,
>
Shouldn't we wait until the reset bindings are actually used in the dtsi ?
I'm quite sure kevin will post it with the Ethernet nodes.
On Thursday 19 May 2016 14:08:43 Andy Gross wrote:
> > + * - Tim
> > + */
> > +int qcom_tcsr_phy_sel(u32 val)
> > +{
> > + void __iomem *phy_select;
> > + int ret;
> > +
> > + phy_select = ioremap(USB2_PHY_SEL, 4);
> > +
> > + if (!phy_select) {
> > +
On Thursday 19 May 2016 14:08:43 Andy Gross wrote:
> > + * - Tim
> > + */
> > +int qcom_tcsr_phy_sel(u32 val)
> > +{
> > + void __iomem *phy_select;
> > + int ret;
> > +
> > + phy_select = ioremap(USB2_PHY_SEL, 4);
> > +
> > + if (!phy_select) {
> > +
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/tty/vt/keyboard.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/tty/vt/keyboard.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git
On 20/05/16 14:19, Neil Armstrong wrote:
[...]
> >>> Missing #include ?
> >>>
> >>> Thanks,
> >>>
> >>
> >> Shouldn't we wait until the reset bindings are actually used in the dtsi ?
> >> I'm quite sure kevin will post it with the Ethernet nodes.
> >
> > Why? The header file is related to the
On 20/05/16 14:19, Neil Armstrong wrote:
[...]
> >>> Missing #include ?
> >>>
> >>> Thanks,
> >>>
> >>
> >> Shouldn't we wait until the reset bindings are actually used in the dtsi ?
> >> I'm quite sure kevin will post it with the Ethernet nodes.
> >
> > Why? The header file is related to the
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/s390/char/keyboard.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/s390/char/keyboard.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git
Use the brand new devm_reset_controller_register() API to get rid of
the platform driver remove callback.
Signed-off-by: Neil Armstrong
---
drivers/reset/reset-oxnas.c | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
Hi Philip,
This patch is based on
Use the brand new devm_reset_controller_register() API to get rid of
the platform driver remove callback.
Signed-off-by: Neil Armstrong
---
drivers/reset/reset-oxnas.c | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
Hi Philip,
This patch is based on your reset/next tree
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/ptp/ptp_chardev.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/ptp/ptp_chardev.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/net/wan/cosa.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff
On 05/20/2016 12:04 PM, Carlo Caione wrote:
> On 20/05/16 11:10, Neil Armstrong wrote:
>> On 05/20/2016 11:04 AM, Carlo Caione wrote:
>>> On 20/05/16 10:27, Neil Armstrong wrote:
This patch adds the platform driver for the Amlogic Meson GXBB Reset
Controller.
Signed-off-by:
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/net/wan/cosa.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git
On 05/20/2016 12:04 PM, Carlo Caione wrote:
> On 20/05/16 11:10, Neil Armstrong wrote:
>> On 05/20/2016 11:04 AM, Carlo Caione wrote:
>>> On 20/05/16 10:27, Neil Armstrong wrote:
This patch adds the platform driver for the Amlogic Meson GXBB Reset
Controller.
Signed-off-by:
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/misc/vmw_vmci/vmci_host.c | 14 --
1 file changed, 4 insertions(+), 10
On 05/20/2016 11:10 AM, Carlo Caione wrote:
> On 20/05/16 10:53, Neil Armstrong wrote:
>> On 05/20/2016 10:47 AM, Carlo Caione wrote:
>>> On 20/05/16 10:27, Neil Armstrong wrote:
Update DTSI file to add the reset controller node.
Signed-off-by: Neil Armstrong
Use memdup_user to duplicate a memory region from user-space to
kernel-space, instead of open coding using kmalloc & copy_from_user.
Signed-off-by: Muhammad Falak R Wani
---
drivers/misc/vmw_vmci/vmci_host.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git
On 05/20/2016 11:10 AM, Carlo Caione wrote:
> On 20/05/16 10:53, Neil Armstrong wrote:
>> On 05/20/2016 10:47 AM, Carlo Caione wrote:
>>> On 20/05/16 10:27, Neil Armstrong wrote:
Update DTSI file to add the reset controller node.
Signed-off-by: Neil Armstrong
---
On 05/20/2016 11:08 AM, Carlo Caione wrote:
> On 20/05/16 10:51, Neil Armstrong wrote:
>> On 05/20/2016 10:46 AM, Carlo Caione wrote:
>>> On 20/05/16 10:27, Neil Armstrong wrote:
Add DT bindings for the Meson GXBB SoC Reset Controller documentation and
the
associated include file.
On 05/20/2016 11:08 AM, Carlo Caione wrote:
> On 20/05/16 10:51, Neil Armstrong wrote:
>> On 05/20/2016 10:46 AM, Carlo Caione wrote:
>>> On 20/05/16 10:27, Neil Armstrong wrote:
Add DT bindings for the Meson GXBB SoC Reset Controller documentation and
the
associated include file.
Hi Philipp,
On 05/20/2016 11:27 AM, Philipp Zabel wrote:
> Hi Neil,
>
> Am Freitag, den 20.05.2016, 10:27 +0200 schrieb Neil Armstrong:
>> +config MESON_GXBB_RESET
>> +tristate "Amlogic Meson GXBB Reset Driver"
>> +depends on (ARCH_MESON && RESET_CONTROLLER)
>
> With the "reset: fix
Hi Philipp,
On 05/20/2016 11:27 AM, Philipp Zabel wrote:
> Hi Neil,
>
> Am Freitag, den 20.05.2016, 10:27 +0200 schrieb Neil Armstrong:
>> +config MESON_GXBB_RESET
>> +tristate "Amlogic Meson GXBB Reset Driver"
>> +depends on (ARCH_MESON && RESET_CONTROLLER)
>
> With the "reset: fix
On Thursday, May 19, 2016 08:11:34 PM Grygorii Strashko wrote:
> On 05/19/2016 04:38 PM, Rafael J. Wysocki wrote:
> > On Fri, May 13, 2016 at 8:03 PM, Grygorii Strashko
> > wrote:
> >> The PM runtime will be left disabled for the device if its .suspend_late()
> >>
On Thursday, May 19, 2016 08:11:34 PM Grygorii Strashko wrote:
> On 05/19/2016 04:38 PM, Rafael J. Wysocki wrote:
> > On Fri, May 13, 2016 at 8:03 PM, Grygorii Strashko
> > wrote:
> >> The PM runtime will be left disabled for the device if its .suspend_late()
> >> callback fails and async suspend
The function tegra_pmc_readl() returns the u32 type data and hence
change the data type of variable where this data is stored to u32
type.
Signed-off-by: Laxman Dewangan
Reviewed-by: Jon Hunter
---
Changes from V1:
-This is new in series as per
The function tegra_pmc_readl() returns the u32 type data and hence
change the data type of variable where this data is stored to u32
type.
Signed-off-by: Laxman Dewangan
Reviewed-by: Jon Hunter
---
Changes from V1:
-This is new in series as per discussion on V1 series to use u32 for
The IO pins of Tegra SoCs are grouped for common control of IO interface
like setting voltage signal levels and power state of the interface. The
group is generally referred as IO pads. The power state and voltage control
of IO pins can be done at IO pads level.
Tegra124 onwards IO pads support
The IO pins of Tegra SoCs are grouped for common control of IO interface
like setting voltage signal levels and power state of the interface. The
group is generally referred as IO pads. The power state and voltage control
of IO pins can be done at IO pads level.
Tegra124 onwards IO pads support
Use BIT macro for register field definition and make constant as U
when using in shift operator like (3 << 30) to (3U << 30)
Signed-off-by: Laxman Dewangan
Acked-by: Jon Hunter
---
Changes from V1:
- Remove the indenting of line which is not for BIT
The IO pins of Tegra SoCs are grouped for common control of IO
interface like setting voltage signal levels and power state of
the interface. The group is generally referred as IO pads. The
power state and voltage control of IO pins can be done at IO pads
level.
Tegra generation SoC supports the
Use BIT macro for register field definition and make constant as U
when using in shift operator like (3 << 30) to (3U << 30)
Signed-off-by: Laxman Dewangan
Acked-by: Jon Hunter
---
Changes from V1:
- Remove the indenting of line which is not for BIT macro usage.
Changes from V2:
- None
The IO pins of Tegra SoCs are grouped for common control of IO
interface like setting voltage signal levels and power state of
the interface. The group is generally referred as IO pads. The
power state and voltage control of IO pins can be done at IO pads
level.
Tegra generation SoC supports the
Hello Fabio,
Am 20.05.2016 um 13:40 schrieb Fabio Estevam:
Hi Heiko,
On Fri, May 20, 2016 at 8:15 AM, Heiko Schocher wrote:
commit 503fe87bd0a8 ("gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading")
breaks the aristainetos2 board with the "lg,lg4573" panel.
This reverts the
Hello Fabio,
Am 20.05.2016 um 13:40 schrieb Fabio Estevam:
Hi Heiko,
On Fri, May 20, 2016 at 8:15 AM, Heiko Schocher wrote:
commit 503fe87bd0a8 ("gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading")
breaks the aristainetos2 board with the "lg,lg4573" panel.
This reverts the above commit.
On Friday, May 20, 2016 07:52:47 AM Viresh Kumar wrote:
> On 20-05-16, 03:41, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Loops over online CPUs in cpufreq_stats_init() and cpufreq_stats_exit()
> > should be carried out with CPU offline/online locked
On Friday, May 20, 2016 07:52:47 AM Viresh Kumar wrote:
> On 20-05-16, 03:41, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Loops over online CPUs in cpufreq_stats_init() and cpufreq_stats_exit()
> > should be carried out with CPU offline/online locked or races are
> > possible
When the DMA configuration fails, there is a log reporting that we can't
use DMA and indicating the error number. When booting the kernel, it is
annoying to see this error number. Moreover, people can think something
is going wrong. It is not the case, it means that DMA can't be used but
it
When the DMA configuration fails, there is a log reporting that we can't
use DMA and indicating the error number. When booting the kernel, it is
annoying to see this error number. Moreover, people can think something
is going wrong. It is not the case, it means that DMA can't be used but
it
On Thursday 19 May 2016 11:02:56 Rob Herring wrote:
> I happen have a script... (I run it every time people complain about DT).
>
> Here's the diffstat of mach-* and plat-* since merging DT support:
>
> v3.0: 833 files changed, 10945 insertions(+), 37476 deletions(-)
> v3.1: 955 files changed,
On Thursday 19 May 2016 11:02:56 Rob Herring wrote:
> I happen have a script... (I run it every time people complain about DT).
>
> Here's the diffstat of mach-* and plat-* since merging DT support:
>
> v3.0: 833 files changed, 10945 insertions(+), 37476 deletions(-)
> v3.1: 955 files changed,
On 19 May 2016 at 11:08, Jiri Slaby wrote:
> From: Kangjie Lu
>
> 3.12-stable review patch. If anyone has any objections, please let me know.
>
> ===
>
> [ Upstream commit 5f8e44741f9f216e33736ea4ec65ca9ac03036e6 ]
>
> The stack object “map” has
On 19 May 2016 at 11:08, Jiri Slaby wrote:
> From: Kangjie Lu
>
> 3.12-stable review patch. If anyone has any objections, please let me know.
>
> ===
>
> [ Upstream commit 5f8e44741f9f216e33736ea4ec65ca9ac03036e6 ]
>
> The stack object “map” has a total size of 32 bytes. Its last 4
801 - 900 of 1358 matches
Mail list logo