The new driver at spi/spi-fsl-qspi.c replaces the old SPI NOR driver
at mtd/fsl-quadspi.c. Switch to the new driver in the defconfigs.
Signed-off-by: Frieder Schrempf
---
arch/arm/configs/imx_v6_v7_defconfig | 2 +-
arch/arm/configs/multi_v7_defconfig | 2 +-
2 files changed, 2 insertions(+),
The new driver at spi/spi-fsl-qspi.c replaces the old SPI NOR driver
at mtd/fsl-quadspi.c. Switch to the new driver in the defconfigs.
Signed-off-by: Frieder Schrempf
---
arch/arm/configs/imx_v6_v7_defconfig | 2 +-
arch/arm/configs/multi_v7_defconfig | 2 +-
2 files changed, 2 insertions(+),
The driver was ported to the SPI framework so it can be used as
a generic SPI memory driver and not only for SPI NOR.
Reflect this transition in the MAINTAINERS file.
Signed-off-by: Frieder Schrempf
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
The driver was ported to the SPI framework so it can be used as
a generic SPI memory driver and not only for SPI NOR.
Reflect this transition in the MAINTAINERS file.
Signed-off-by: Frieder Schrempf
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
There's a new driver using the SPI memory interface of the SPI framework
at spi/spi-fsl-qspi.c, which can be used together with m25p80.c to
replace the functionality of this SPI NOR driver.
Signed-off-by: Frieder Schrempf
---
drivers/mtd/spi-nor/Kconfig |9 -
After switching to the new FSL QSPI driver the property
'fsl,qspi-has-second-chip' is not needed anymore.
The driver now uses the 'reg' property to determine the bus and
the chipselect.
Signed-off-by: Frieder Schrempf
---
arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 1 -
1 file changed, 1
There's a new driver using the SPI memory interface of the SPI framework
at spi/spi-fsl-qspi.c, which can be used together with m25p80.c to
replace the functionality of this SPI NOR driver.
Signed-off-by: Frieder Schrempf
---
drivers/mtd/spi-nor/Kconfig |9 -
After switching to the new FSL QSPI driver the property
'fsl,qspi-has-second-chip' is not needed anymore.
The driver now uses the 'reg' property to determine the bus and
the chipselect.
Signed-off-by: Frieder Schrempf
---
arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 1 -
1 file changed, 1
After switching to the new FSL QSPI driver the property
'fsl,qspi-has-second-chip' is not needed anymore.
The driver now uses the 'reg' property to determine the bus and
the chipselect.
Signed-off-by: Frieder Schrempf
---
arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts | 1 -
1 file changed, 1
The FSL QSPI driver was moved to the SPI framework and it now
acts as a SPI controller. Therefore the subnodes need to set
spi-[rx/tx]-bus-width = <4>, so quad mode is used just as before.
Also the properties 'num-cs' and 'bus-num' were never read by the
driver and can be removed.
The property
After switching to the new FSL QSPI driver the property
'fsl,qspi-has-second-chip' is not needed anymore.
The driver now uses the 'reg' property to determine the bus and
the chipselect.
Signed-off-by: Frieder Schrempf
---
arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts | 1 -
1 file changed, 1
The FSL QSPI driver was moved to the SPI framework and it now
acts as a SPI controller. Therefore the subnodes need to set
spi-[rx/tx]-bus-width = <4>, so quad mode is used just as before.
Also the properties 'num-cs' and 'bus-num' were never read by the
driver and can be removed.
The property
The FSL QSPI driver was moved to the SPI framework and it now
acts as a SPI controller. Therefore the subnodes need to set
spi-[rx/tx]-bus-width = <4>, so quad mode is used just as before.
Also the properties 'bus-num', 'fsl,spi-num-chipselects' and
'fsl,spi-flash-chipselects' were never read by
arm, ia64, sh, x86 architectures use the same version
of huge_ptep_set_access_flags, so move this generic implementation
into asm-generic/hugetlb.h.
Signed-off-by: Alexandre Ghiti
---
arch/arm/include/asm/hugetlb-3level.h | 7 ---
arch/arm64/include/asm/hugetlb.h | 1 +
The FSL QSPI driver was moved to the SPI framework and it now
acts as a SPI controller. Therefore the subnodes need to set
spi-[rx/tx]-bus-width = <4>, so quad mode is used just as before.
Also the properties 'bus-num', 'fsl,spi-num-chipselects' and
'fsl,spi-flash-chipselects' were never read by
arm, ia64, sh, x86 architectures use the same version
of huge_ptep_set_access_flags, so move this generic implementation
into asm-generic/hugetlb.h.
Signed-off-by: Alexandre Ghiti
---
arch/arm/include/asm/hugetlb-3level.h | 7 ---
arch/arm64/include/asm/hugetlb.h | 1 +
By calling spi_mem_get_name(), the driver of the (Q)SPI controller can
set a custom name for the memory device if necessary.
This is useful to keep mtdparts compatible when controller drivers are
ported from the MTD to the SPI layer.
Signed-off-by: Frieder Schrempf
---
By calling spi_mem_get_name(), the driver of the (Q)SPI controller can
set a custom name for the memory device if necessary.
This is useful to keep mtdparts compatible when controller drivers are
ported from the MTD to the SPI layer.
Signed-off-by: Frieder Schrempf
---
Move the documentation of the old SPI NOR driver to the place of the new
SPI memory interface based driver.
Signed-off-by: Frieder Schrempf
---
Changes in v2:
==
* Split the moving and editing of the dt-bindings in two patches
.../devicetree/bindings/mtd/fsl-quadspi.txt | 65
Move the documentation of the old SPI NOR driver to the place of the new
SPI memory interface based driver.
Signed-off-by: Frieder Schrempf
---
Changes in v2:
==
* Split the moving and editing of the dt-bindings in two patches
.../devicetree/bindings/mtd/fsl-quadspi.txt | 65
When porting (Q)SPI controller drivers from the MTD layer to the SPI
layer, the naming scheme for the memory devices changes. To be able
to keep compatibility with the old drivers naming scheme, a function
is added to the SPI mem interface to let controller drivers set a
custom name for the
When porting (Q)SPI controller drivers from the MTD layer to the SPI
layer, the naming scheme for the memory devices changes. To be able
to keep compatibility with the old drivers naming scheme, a function
is added to the SPI mem interface to let controller drivers set a
custom name for the
On 05.07.2018 04:52, A.s. Dong wrote:
>> -Original Message-
>> From: Stefan Agner [mailto:ste...@agner.ch]
>> Sent: Thursday, June 28, 2018 4:13 PM
>> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
>> Cc: Fabio Estevam ; Bough Chen
>> ; A.s. Dong ;
>> mich...@amarulasolutions.com;
On 05.07.2018 04:52, A.s. Dong wrote:
>> -Original Message-
>> From: Stefan Agner [mailto:ste...@agner.ch]
>> Sent: Thursday, June 28, 2018 4:13 PM
>> To: adrian.hun...@intel.com; ulf.hans...@linaro.org
>> Cc: Fabio Estevam ; Bough Chen
>> ; A.s. Dong ;
>> mich...@amarulasolutions.com;
On Thu, 05 Jul 2018, Matti Vaittinen wrote:
> Thanks for taking the time to check this =)
>
> On Thu, Jul 05, 2018 at 10:18:13AM +0100, Lee Jones wrote:
> > On Thu, 05 Jul 2018, Matti Vaittinen wrote:
> >
> > > --- a/drivers/mfd/Kconfig
> > > +++ b/drivers/mfd/Kconfig
> > > @@ -1787,6 +1787,19
On Thu, 05 Jul 2018, Matti Vaittinen wrote:
> Thanks for taking the time to check this =)
>
> On Thu, Jul 05, 2018 at 10:18:13AM +0100, Lee Jones wrote:
> > On Thu, 05 Jul 2018, Matti Vaittinen wrote:
> >
> > > --- a/drivers/mfd/Kconfig
> > > +++ b/drivers/mfd/Kconfig
> > > @@ -1787,6 +1787,19
On 4 July 2018 at 22:29, Marc Zyngier wrote:
> On Wed, 4 Jul 2018 15:34:36 +0200
> Ulf Hansson wrote:
>
>> On 4 July 2018 at 13:34, Marc Zyngier wrote:
>> > On 04/07/18 11:50, Ulf Hansson wrote:
>> >> + Marc
>> >>
>> >> On 4 July 2018 at 08:28, Stefan Mavrodiev wrote:
>> >>> When mmc host
On 4 July 2018 at 22:29, Marc Zyngier wrote:
> On Wed, 4 Jul 2018 15:34:36 +0200
> Ulf Hansson wrote:
>
>> On 4 July 2018 at 13:34, Marc Zyngier wrote:
>> > On 04/07/18 11:50, Ulf Hansson wrote:
>> >> + Marc
>> >>
>> >> On 4 July 2018 at 08:28, Stefan Mavrodiev wrote:
>> >>> When mmc host
On Thu, Jul 5, 2018 at 11:54 AM, Meelis Roos wrote:
>> > I tried 4.18.0-rc1-00023-g9ffc59d57228 and now
>> > 4.18.0-rc3-00113-gfc36def997cf on a 32-bit server and then some other
>> > 32-bit machines, and got half-failed bootup - kernel and userspace come
>> > up but some services fail to start,
On Thu, Jul 5, 2018 at 11:54 AM, Meelis Roos wrote:
>> > I tried 4.18.0-rc1-00023-g9ffc59d57228 and now
>> > 4.18.0-rc3-00113-gfc36def997cf on a 32-bit server and then some other
>> > 32-bit machines, and got half-failed bootup - kernel and userspace come
>> > up but some services fail to start,
...
> > Well, just like we have LED and LED triggers in the kernel, I think having
> > a generic way to use patterns could be nice and in this case Morse could be
> > one such pattern, but if that means it's limited to userland to configure
> > it then it sadly voids all of its benefits.
I've
...
> > Well, just like we have LED and LED triggers in the kernel, I think having
> > a generic way to use patterns could be nice and in this case Morse could be
> > one such pattern, but if that means it's limited to userland to configure
> > it then it sadly voids all of its benefits.
I've
We've faced similar issue in Bug:
https://bugs.linaro.org/show_bug.cgi?id=3903
And it turned out to be a regmap area declared wrongly (likely) for a
PMIC device, caught when trying to read "registers" file from debugfs
in that particular device. Best way to identify the issue is to check
which
We've faced similar issue in Bug:
https://bugs.linaro.org/show_bug.cgi?id=3903
And it turned out to be a regmap area declared wrongly (likely) for a
PMIC device, caught when trying to read "registers" file from debugfs
in that particular device. Best way to identify the issue is to check
which
On 2018/06/27 5:37, Tetsuo Handa wrote:
> I think that syzbot can stop deciding email recipients and leave it to those
> who
> diagnose bugs, for the ratio of sending to wrong subsystem maintainers is not
> low.
> For example, syzbot assumed that "INFO: task hung in __get_super" is a fs
> layer
On Thu, 05 Jul 2018, Matti Vaittinen wrote:
> On Thu, Jul 05, 2018 at 10:24:44AM +0100, Lee Jones wrote:
> > On Thu, 05 Jul 2018, Matti Vaittinen wrote:
> >
> > > Document devicetree bindings for ROHM BD71837 PMIC MFD.
> > >
> > > Signed-off-by: Matti Vaittinen
> > > Reviewed-by: Rob Herring
>
On 2018/06/27 5:37, Tetsuo Handa wrote:
> I think that syzbot can stop deciding email recipients and leave it to those
> who
> diagnose bugs, for the ratio of sending to wrong subsystem maintainers is not
> low.
> For example, syzbot assumed that "INFO: task hung in __get_super" is a fs
> layer
On Thu, 05 Jul 2018, Matti Vaittinen wrote:
> On Thu, Jul 05, 2018 at 10:24:44AM +0100, Lee Jones wrote:
> > On Thu, 05 Jul 2018, Matti Vaittinen wrote:
> >
> > > Document devicetree bindings for ROHM BD71837 PMIC MFD.
> > >
> > > Signed-off-by: Matti Vaittinen
> > > Reviewed-by: Rob Herring
>
On Wed, Jun 27, 2018 at 08:22:42PM +0800, Xunlei Pang wrote:
> tick-based whole utime is utime_0, tick-based whole stime
> is stime_0, scheduler time is rtime_0.
> For a long time, the process runs mainly in userspace with
> run-sleep patterns, and because two different clocks, it
> is possible
On Wed, Jun 27, 2018 at 08:22:42PM +0800, Xunlei Pang wrote:
> tick-based whole utime is utime_0, tick-based whole stime
> is stime_0, scheduler time is rtime_0.
> For a long time, the process runs mainly in userspace with
> run-sleep patterns, and because two different clocks, it
> is possible
On Thursday, July 5, 2018 11:50:11 AM CEST Takashi Iwai wrote:
> On Thu, 05 Jul 2018 11:34:59 +0200,
> Rafael J. Wysocki wrote:
> >
> > Hi,
> >
> > On Thu, Jul 5, 2018 at 9:05 AM, Takashi Iwai wrote:
> > > Hi,
> > >
> > > we've got a regression report since 4.17 about the behavior of
> > >
On Thursday, July 5, 2018 11:50:11 AM CEST Takashi Iwai wrote:
> On Thu, 05 Jul 2018 11:34:59 +0200,
> Rafael J. Wysocki wrote:
> >
> > Hi,
> >
> > On Thu, Jul 5, 2018 at 9:05 AM, Takashi Iwai wrote:
> > > Hi,
> > >
> > > we've got a regression report since 4.17 about the behavior of
> > >
And thanks again Lee!
On Thu, Jul 05, 2018 at 10:24:44AM +0100, Lee Jones wrote:
> On Thu, 05 Jul 2018, Matti Vaittinen wrote:
>
> > Document devicetree bindings for ROHM BD71837 PMIC MFD.
> >
> > Signed-off-by: Matti Vaittinen
> > Reviewed-by: Rob Herring
> > ---
> >
And thanks again Lee!
On Thu, Jul 05, 2018 at 10:24:44AM +0100, Lee Jones wrote:
> On Thu, 05 Jul 2018, Matti Vaittinen wrote:
>
> > Document devicetree bindings for ROHM BD71837 PMIC MFD.
> >
> > Signed-off-by: Matti Vaittinen
> > Reviewed-by: Rob Herring
> > ---
> >
Thanks for taking the time to check this =)
On Thu, Jul 05, 2018 at 10:18:13AM +0100, Lee Jones wrote:
> On Thu, 05 Jul 2018, Matti Vaittinen wrote:
>
> > --- a/drivers/mfd/Kconfig
> > +++ b/drivers/mfd/Kconfig
> > @@ -1787,6 +1787,19 @@ config MFD_STW481X
> > in various ST
Thanks for taking the time to check this =)
On Thu, Jul 05, 2018 at 10:18:13AM +0100, Lee Jones wrote:
> On Thu, 05 Jul 2018, Matti Vaittinen wrote:
>
> > --- a/drivers/mfd/Kconfig
> > +++ b/drivers/mfd/Kconfig
> > @@ -1787,6 +1787,19 @@ config MFD_STW481X
> > in various ST
From: Rafael J. Wysocki
I really need to look at driver core changes before they are applied
due to PM dependencies and they sometimes get lost in the LKML
traffic, so add myself as an official driver core reviewer.
Signed-off-by: Rafael J. Wysocki
---
MAINTAINERS |1 +
1 file changed, 1
From: Rafael J. Wysocki
I really need to look at driver core changes before they are applied
due to PM dependencies and they sometimes get lost in the LKML
traffic, so add myself as an official driver core reviewer.
Signed-off-by: Rafael J. Wysocki
---
MAINTAINERS |1 +
1 file changed, 1
Hello everyone, this is my first time posting to this list so please be
gentle.
I have a server, hardware spec:
HP DL360p G8
2 x Intel Xeon E5-2620 Hex-Core 2GHz processors
150GB Ram
Embedded HP Ethernet 1Gb 4-port 331FLR Adapter
Embedded
Hello everyone, this is my first time posting to this list so please be
gentle.
I have a server, hardware spec:
HP DL360p G8
2 x Intel Xeon E5-2620 Hex-Core 2GHz processors
150GB Ram
Embedded HP Ethernet 1Gb 4-port 331FLR Adapter
Embedded
Morning folks,
As the title suggest im having issues geting my kernel started, and
was hoping for some guidance.
In short i think my problems come from the MMU/Cache configuration
being bad during the transfer from my boot loader to the kernel.
Just as a quick aside i have confirmed my kernel
Morning folks,
As the title suggest im having issues geting my kernel started, and
was hoping for some guidance.
In short i think my problems come from the MMU/Cache configuration
being bad during the transfer from my boot loader to the kernel.
Just as a quick aside i have confirmed my kernel
It will cause a linking error because the jump assembly code were using j,
however it may be not enough to jump to the destination. We have to change it
with pseudo instruction b. In that way, assembler will generate a set of safe
assembly codes to make sure the destination is able to jump.
It will cause a linking error because the jump assembly code were using j,
however it may be not enough to jump to the destination. We have to change it
with pseudo instruction b. In that way, assembler will generate a set of safe
assembly codes to make sure the destination is able to jump.
On Thursday, July 5, 2018 12:00:27 PM CEST Takashi Iwai wrote:
> On Thu, 05 Jul 2018 11:58:15 +0200,
> Thomas H4nig wrote:
> >
> > Am 05.07.2018 um 11:50 schrieb Takashi Iwai:
> > > Usually X desktop environment receives an input event from the ACPI
> > > power button input device, and deals the
On Thursday, July 5, 2018 12:00:27 PM CEST Takashi Iwai wrote:
> On Thu, 05 Jul 2018 11:58:15 +0200,
> Thomas H4nig wrote:
> >
> > Am 05.07.2018 um 11:50 schrieb Takashi Iwai:
> > > Usually X desktop environment receives an input event from the ACPI
> > > power button input device, and deals the
/commits/Keerthy/ARM-OMAP2-sleep33-43xx-Make-sleep-actions-configurable/20180705-010044
base: https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
for-next
config: arm-multi_v7_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce
/commits/Keerthy/ARM-OMAP2-sleep33-43xx-Make-sleep-actions-configurable/20180705-010044
base: https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
for-next
config: arm-multi_v7_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce
As done for format and channels, add the possibility to merge
the backend rates on the frontend rates.
This useful if the backend does not support all rates supported by the
frontend, or if several backends (cpu and codecs) with different
capabilities are connected to the same frontend.
The goal of this patch is to simplify a bit dpcm runtime stream merge
by removing several local variables.
ATM, merge functions return the BE 'filter' values which should then be
filtered against the FE stream values. This create a lot of local
variable and unnecessary init of min and max.
This patchset adds the possibility to merge BE rates in the dpcm runtime
hw, like it is done for formats and channels.
This first patch is a simple rework of format and channel merge to ease
the addition of rate merge.
Jerome Brunet (2):
ASoC: dpcm: rework runtime stream merge
ASoC: dpcm:
As done for format and channels, add the possibility to merge
the backend rates on the frontend rates.
This useful if the backend does not support all rates supported by the
frontend, or if several backends (cpu and codecs) with different
capabilities are connected to the same frontend.
The goal of this patch is to simplify a bit dpcm runtime stream merge
by removing several local variables.
ATM, merge functions return the BE 'filter' values which should then be
filtered against the FE stream values. This create a lot of local
variable and unnecessary init of min and max.
This patchset adds the possibility to merge BE rates in the dpcm runtime
hw, like it is done for formats and channels.
This first patch is a simple rework of format and channel merge to ease
the addition of rate merge.
Jerome Brunet (2):
ASoC: dpcm: rework runtime stream merge
ASoC: dpcm:
On Wed, Jul 04, 2018 at 06:50:00PM +0100, Will Deacon wrote:
> On Wed, Jul 04, 2018 at 04:56:19PM +0100, Mark Rutland wrote:
> > On Wed, Jul 04, 2018 at 04:06:46PM +0100, Will Deacon wrote:
> > > On Mon, Jun 25, 2018 at 11:59:47AM +0100, Mark Rutland wrote:
> > > > Currently architectures can
On Wed, Jul 04, 2018 at 06:50:00PM +0100, Will Deacon wrote:
> On Wed, Jul 04, 2018 at 04:56:19PM +0100, Mark Rutland wrote:
> > On Wed, Jul 04, 2018 at 04:06:46PM +0100, Will Deacon wrote:
> > > On Mon, Jun 25, 2018 at 11:59:47AM +0100, Mark Rutland wrote:
> > > > Currently architectures can
Hi,
On 04/07/18 15:24, Matt Fleming wrote:
> It's possible that the CPU doing nohz idle balance hasn't had its own
> load updated for many seconds. This can lead to huge deltas between
> rq->avg_stamp and rq->clock when rebalancing, and has been seen to
> cause the following crash:
>
> divide
Hi,
On 04/07/18 15:24, Matt Fleming wrote:
> It's possible that the CPU doing nohz idle balance hasn't had its own
> load updated for many seconds. This can lead to huge deltas between
> rq->avg_stamp and rq->clock when rebalancing, and has been seen to
> cause the following crash:
>
> divide
The patch
ASoC: rsnd: cmd: Add missing newline to debug message
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: rsnd: cmd: Add missing newline to debug message
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
Am 05.07.2018 um 11:50 schrieb Takashi Iwai:
> Usually X desktop environment receives an input event from the ACPI
> power button input device, and deals the event accordingly depending
> on the setup. The power-down behavior itself should be equivalent
> with "systemctl poweroff" or such.
The
Am 05.07.2018 um 11:50 schrieb Takashi Iwai:
> Usually X desktop environment receives an input event from the ACPI
> power button input device, and deals the event accordingly depending
> on the setup. The power-down behavior itself should be equivalent
> with "systemctl poweroff" or such.
The
On Thu, 05 Jul 2018 11:58:15 +0200,
Thomas H4nig wrote:
>
> Am 05.07.2018 um 11:50 schrieb Takashi Iwai:
> > Usually X desktop environment receives an input event from the ACPI
> > power button input device, and deals the event accordingly depending
> > on the setup. The power-down behavior
On Thu, 05 Jul 2018 11:58:15 +0200,
Thomas H4nig wrote:
>
> Am 05.07.2018 um 11:50 schrieb Takashi Iwai:
> > Usually X desktop environment receives an input event from the ACPI
> > power button input device, and deals the event accordingly depending
> > on the setup. The power-down behavior
On Wed, Jul 04, 2018 at 06:41:34PM +0100, Will Deacon wrote:
> On Wed, Jul 04, 2018 at 05:37:23PM +0100, Mark Rutland wrote:
> > On Wed, Jul 04, 2018 at 04:24:22PM +0100, Will Deacon wrote:
> > > This is mostly straightforward, but the cmpxchg/cmpxchg_double cases grow
> > > an 'arch' prefix which
On Wed, Jul 04, 2018 at 06:41:34PM +0100, Will Deacon wrote:
> On Wed, Jul 04, 2018 at 05:37:23PM +0100, Mark Rutland wrote:
> > On Wed, Jul 04, 2018 at 04:24:22PM +0100, Will Deacon wrote:
> > > This is mostly straightforward, but the cmpxchg/cmpxchg_double cases grow
> > > an 'arch' prefix which
> > I tried 4.18.0-rc1-00023-g9ffc59d57228 and now
> > 4.18.0-rc3-00113-gfc36def997cf on a 32-bit server and then some other
> > 32-bit machines, and got half-failed bootup - kernel and userspace come
> > up but some services fail to start, including network and
> > systemd-journald:
> >
> >
On 05/07/18 10:52, Dan Carpenter wrote:
> On Thu, Jul 05, 2018 at 10:37:32AM +0100, Colin King wrote:
>> diff --git a/drivers/net/ethernet/sun/niu.c b/drivers/net/ethernet/sun/niu.c
>> index 88c12474a0c3..2d6b62c6d9ab 100644
>> --- a/drivers/net/ethernet/sun/niu.c
>> +++
> > I tried 4.18.0-rc1-00023-g9ffc59d57228 and now
> > 4.18.0-rc3-00113-gfc36def997cf on a 32-bit server and then some other
> > 32-bit machines, and got half-failed bootup - kernel and userspace come
> > up but some services fail to start, including network and
> > systemd-journald:
> >
> >
On 05/07/18 10:52, Dan Carpenter wrote:
> On Thu, Jul 05, 2018 at 10:37:32AM +0100, Colin King wrote:
>> diff --git a/drivers/net/ethernet/sun/niu.c b/drivers/net/ethernet/sun/niu.c
>> index 88c12474a0c3..2d6b62c6d9ab 100644
>> --- a/drivers/net/ethernet/sun/niu.c
>> +++
> divide by zero when rebalancing domains")
>> url:
>> https://github.com/0day-ci/linux/commits/Matt-Fleming/sched-fair-Avoid-divide-by-zero-when-rebalancing-domains/20180705-024633
>>
>>
>> in testcase: trinity
>> with following parameters:
>&g
> divide by zero when rebalancing domains")
>> url:
>> https://github.com/0day-ci/linux/commits/Matt-Fleming/sched-fair-Avoid-divide-by-zero-when-rebalancing-domains/20180705-024633
>>
>>
>> in testcase: trinity
>> with following parameters:
>&g
The S805X is a variant of the Amlogic Meson GXL SoC family with the
following physical limitations :
- No SDCard interface
- No GPIOCLK pins
- No USB OTG ID pin (but Gadget feature can stil be forced)
- No 5V regulator
- Reduced ADC inputs (only ADC0 and ADC1)
- GPIODV_26, GPIOAO_3, GPIOAO_4,
The S805X is a variant of the Amlogic Meson GXL SoC family with the
following physical limitations :
- No SDCard interface
- No GPIOCLK pins
- No USB OTG ID pin (but Gadget feature can stil be forced)
- No 5V regulator
- Reduced ADC inputs (only ADC0 and ADC1)
- GPIODV_26, GPIOAO_3, GPIOAO_4,
The Amlogic P241 board is the Reference Design board for the S805X
variant of the Amlogic Meson GXL SoC family.
The P241 board has the following features :
- 1GiB DDR4 Memory
- HDMI Connector with CEC
- A/V jack with Stereo Audio and CVBS
- 10/100 Ethernet
- 2x USB2.0 Type-A
- On-board WiFi SDIO
The Amlogic P241 board is the Reference Design board for the S805X
variant of the Amlogic Meson GXL SoC family.
The S805X is a variant of the Amlogic Meson GXL SoC family with the
following physical limitations :
- No SDCard interface
- No GPIOCLK pins
- No USB OTG ID pin (but Gadget feature can
The Amlogic P241 board is the Reference Design board for the S805X
variant of the Amlogic Meson GXL SoC family.
The P241 board has the following features :
- 1GiB DDR4 Memory
- HDMI Connector with CEC
- A/V jack with Stereo Audio and CVBS
- 10/100 Ethernet
- 2x USB2.0 Type-A
- On-board WiFi SDIO
The Amlogic P241 board is the Reference Design board for the S805X
variant of the Amlogic Meson GXL SoC family.
The S805X is a variant of the Amlogic Meson GXL SoC family with the
following physical limitations :
- No SDCard interface
- No GPIOCLK pins
- No USB OTG ID pin (but Gadget feature can
On Thu, 05 Jul 2018 11:34:59 +0200,
Rafael J. Wysocki wrote:
>
> Hi,
>
> On Thu, Jul 5, 2018 at 9:05 AM, Takashi Iwai wrote:
> > Hi,
> >
> > we've got a regression report since 4.17 about the behavior of
> > power-off with the power button. When a machine is powered off with
> > the power
On Thu, 05 Jul 2018 11:34:59 +0200,
Rafael J. Wysocki wrote:
>
> Hi,
>
> On Thu, Jul 5, 2018 at 9:05 AM, Takashi Iwai wrote:
> > Hi,
> >
> > we've got a regression report since 4.17 about the behavior of
> > power-off with the power button. When a machine is powered off with
> > the power
On 4 July 2018 at 17:18, Stefan Agner wrote:
> On 04.07.2018 17:07, Stefan Agner wrote:
>> If pinctrl nodes for 100/200MHz are missing, the controller should
>> not select any mode which need signal frequencies 100MHz or higher.
>> To prevent such speed modes the driver currently uses the quirk
On 4 July 2018 at 17:18, Stefan Agner wrote:
> On 04.07.2018 17:07, Stefan Agner wrote:
>> If pinctrl nodes for 100/200MHz are missing, the controller should
>> not select any mode which need signal frequencies 100MHz or higher.
>> To prevent such speed modes the driver currently uses the quirk
On Thu, Jul 05, 2018 at 08:53:50AM +0100, Quentin Perret wrote:
> Is there anything else I should do for this patch ?
Pinging me was the right thing. Have it now, much thanks!
On Thu, Jul 05, 2018 at 08:53:50AM +0100, Quentin Perret wrote:
> Is there anything else I should do for this patch ?
Pinging me was the right thing. Have it now, much thanks!
On Thu, 5 Jul 2018, Tian, Baofeng wrote:
> Resubmit again for review, this patch save register and used for RAM dump.
Please do not resubmit by replying to mail which got rejected by LKML in the
first
place. Resubmit means to send the patch new and in proper form.
> static atomic_t
On Thu, 5 Jul 2018, Tian, Baofeng wrote:
> Resubmit again for review, this patch save register and used for RAM dump.
Please do not resubmit by replying to mail which got rejected by LKML in the
first
place. Resubmit means to send the patch new and in proper form.
> static atomic_t
Hi,
On Thu, Jul 5, 2018 at 9:05 AM, Takashi Iwai wrote:
> Hi,
>
> we've got a regression report since 4.17 about the behavior of
> power-off with the power button. When a machine is powered off with
> the power button on desktop, it reboots after a few seconds instead of
> power down.
>
> The
Hi,
On Thu, Jul 5, 2018 at 9:05 AM, Takashi Iwai wrote:
> Hi,
>
> we've got a regression report since 4.17 about the behavior of
> power-off with the power button. When a machine is powered off with
> the power button on desktop, it reboots after a few seconds instead of
> power down.
>
> The
When trying to instantiate a st_accel_i2c device from an ACPI based
system, I ran into some problems:
For my device, there is no ACPI match table entry, so rather than
creating /allocating a new ACPI HID for the device, I wanted to use an
existing DT table compatible entry via creating an
When trying to instantiate a st_accel_i2c device from an ACPI based
system, I ran into some problems:
For my device, there is no ACPI match table entry, so rather than
creating /allocating a new ACPI HID for the device, I wanted to use an
existing DT table compatible entry via creating an
1101 - 1200 of 1346 matches
Mail list logo
