t was found while adding some x86 Chromebooks[1] to
> >>> KernelCI that x86_64_defconfig lacked some basic things for
> >>> anyone to be able to boot a kernel with a serial console enabled
> >>> on those.
> >>
> >> Hold on, those are laptops, righ
On Mon, Oct 12, 2020 at 04:10:45PM +0100, Guillaume Tucker wrote:
> You can get serial console on recent enough Chromebooks with a
> debug interface such as SuzyQable:
>
> https://www.sparkfun.com/products/14746
>
> It's not a USB Type-C adapter, it has a debug inter
On Mon, Oct 12, 2020 at 04:40:40PM +0200, Willy Tarreau wrote:
> Well, to be precise, they don't have *anymore*. I used to exclusively
> select laptops having a serial port given that I was using it daily with
> routers, until I had to resign when I abandonned my good old NC8000 :-/
Yah, with all
defconfig lacked some basic things for
>>> anyone to be able to boot a kernel with a serial console enabled
>>> on those.
>>
>> Hold on, those are laptops, right? How come they do have serial console?
>> Because laptops don't have serial console - that has bee
to be able to boot a kernel with a serial console enabled
> > on those.
>
> Hold on, those are laptops, right? How come they do have serial console?
> Because laptops don't have serial console - that has been the eternal
> problem with debugging kernels on laptops.
Well, to b
On Mon, Oct 12, 2020 at 11:22:10AM +0100, Guillaume Tucker wrote:
> However, it was found while adding some x86 Chromebooks[1] to
> KernelCI that x86_64_defconfig lacked some basic things for
> anyone to be able to boot a kernel with a serial console enabled
> on those.
Hold on, those
doesn't really need these configs to be
upstreamed. It's useful as Enric pointed out, but there are
already several specific config fragments being managed by the
KernelCI build system as one would expect, and we can take care
of one more if need be.
However, it was found while adding
Hi Enric,
On Sun, Oct 11, 2020 at 07:05:55PM +0200, Enric Balletbo i Serra wrote:
> For arm64 (i.e : arm64_defconfig):
> 1. Someone renames CONFIG_A to CONFIG_AB, sends a patch, and as he did a
> grep, the patch modifies all the defconfigs.
> 2. The patch is accepted and merged in linux-ne
On Sun, Oct 11, 2020 at 07:05:55PM +0200, Enric Balletbo i Serra wrote:
> For x86:
>1. You send a patch to list enabling the CONFIG_YOUR_V4L2_DEVICE=m
>2. The patch is rejected because doesn't fit the requirements (is not
> common
> enough)
Well, what if that config option enables hardwar
Hi Borislav,
On 11/10/20 17:57, Borislav Petkov wrote:
> On Sun, Oct 11, 2020 at 05:40:27PM +0200, Enric Balletbo i Serra wrote:
>> How do you quantify those things are NOT common enough? Do you have a number?
>
> I don't want to change the defconfig - you do. So quantifying is in your
> court -
On Sun, Oct 11, 2020 at 05:40:27PM +0200, Enric Balletbo i Serra wrote:
> How do you quantify those things are NOT common enough? Do you have a number?
I don't want to change the defconfig - you do. So quantifying is in your
court - not mine.
> I don't have a number, the only I can tell is that b
sets, the Intel one, is found on Intel Skylake and later. I.e Lots of
laptops need these to have support for the touchpad.
>> But, yes, the main purpose after this patch is the serial console for CI. I
>> saw
>> that there are already some configs with a specific purpose (tiny.co
E and MFD_INTEL_LPSS_PCI
> could be common enough to match within the category of needed to run
> in normal (or common) user mode(s). I can send a patch with only these
> two options.
How do you quantify those things are common enough?
> But, yes, the main purpose after this patch is
eed for normal users.
>
>
We're also probably lacking a definition of what normal users mean, because I
don't think normal users build their own kernel. I think that at least
X86_AMD_PLATFORM_DEVICE and MFD_INTEL_LPSS_PCI could be common enough to match
within the category of needed t
On 10/8/20 9:40 AM, Borislav Petkov wrote:
> On Thu, Oct 08, 2020 at 06:22:06PM +0200, Enric Balletbo i Serra wrote:
>> As part of KernelCI, we added a bunch of different x86 based Chromebooks
>> to do test booting and runtime testing. It will be useful have serial
>> support for these platforms in
On Thu, Oct 08, 2020 at 06:22:06PM +0200, Enric Balletbo i Serra wrote:
> As part of KernelCI, we added a bunch of different x86 based Chromebooks
> to do test booting and runtime testing. It will be useful have serial
> support for these platforms in the default defconfig, as this, is the
> defcon
As part of KernelCI, we added a bunch of different x86 based Chromebooks
to do test booting and runtime testing. It will be useful have serial
support for these platforms in the default defconfig, as this, is the
defconfig used by default for the different maintainer's tree.
SERIAL_8250_DW is the
I saw this booting yesterday's 5.9.0-rc6+. I have one small patch applied,
quite unlikely
to cause any problems I think. Platform is apu2, fedora-27 linux, with serial
console attached.
[0.624831] =
[0.624831] [ BUG: Invalid wait context ]
[0.6
From: Sagar Shrikant Kadam
commit 17b4efdf4e4867079012a48ca10d965fe9d68822 upstream.
An uninitialised spin lock for sifive serial console raises a bad
magic spin_lock error as reported and discussed here [1].
Initialising the spin lock resolves the issue.
The fix is tested on HiFive Unleashed
5.4.44-rt27-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
There is no need to loop for longer. The message of too much work was
removed in commit
9d7c249a1ef9b ("serial: 8250: drop the printk from serial8250_int
From: Sagar Shrikant Kadam
commit 17b4efdf4e4867079012a48ca10d965fe9d68822 upstream.
An uninitialised spin lock for sifive serial console raises a bad
magic spin_lock error as reported and discussed here [1].
Initialising the spin lock resolves the issue.
The fix is tested on HiFive Unleashed
From: Sagar Shrikant Kadam
commit 17b4efdf4e4867079012a48ca10d965fe9d68822 upstream.
An uninitialised spin lock for sifive serial console raises a bad
magic spin_lock error as reported and discussed here [1].
Initialising the spin lock resolves the issue.
The fix is tested on HiFive Unleashed
cpu_uart0: serial@1fe001e0 {
compatible = "ns16550a";
reg = <0 0x1fe001e0 0x8>;
clock-frequency = <3300>;
interrupt-parent = <&liointc>;
interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
no-loopback-test;
};
In ord
compatible = "ns16550a";
reg = <0 0x1fe001e0 0x8>;
clock-frequency = <3300>;
interrupt-parent = <&liointc>;
interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
no-loopback-test;
};
In order to support for serial console on the Lo
= <0 0x1fe001e0 0x8>;
clock-frequency = <3300>;
interrupt-parent = <&liointc>;
interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
no-loopback-test;
};
In order to support for serial console on the Loongson platform,
add CONFIG_SERIAL_OF_PLATFOR
quot;ns16550a";
>reg = <0 0x1fe001e0 0x8>;
>clock-frequency = <3300>;
>interrupt-parent = <&liointc>;
>interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
>no-loopback-test;
>};
>
>In order to support for serial
lock-frequency = <3300>;
interrupt-parent = <&liointc>;
interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
no-loopback-test;
};
In order to support for serial console on the Loongson platform,
add CONFIG_SERIAL_OF_PLATFORM=y to loongson3_defconfig.
With t
s.berkeley.edu; Atish Patra
> ; Anup Patel
> Subject: Re: [PATCH v1 1/1] tty: serial: add missing spin_lock_init for SiFive
> serial console
>
> [External Email] Do not click links or attachments unless you recognize the
> sender and know the content is safe
>
> On Tue, May
On Tue, May 12, 2020 at 04:00:23PM -0700, Palmer Dabbelt wrote:
> On Sat, 09 May 2020 03:24:12 PDT (-0700), sagar.ka...@sifive.com wrote:
> > An uninitialised spin lock for sifive serial console raises a bad
> > magic spin_lock error as reported and discussed here [1].
> >
On Sat, 09 May 2020 03:24:12 PDT (-0700), sagar.ka...@sifive.com wrote:
An uninitialised spin lock for sifive serial console raises a bad
magic spin_lock error as reported and discussed here [1].
Initialising the spin lock resolves the issue.
The fix is tested on HiFive Unleashed A00 board with
An uninitialised spin lock for sifive serial console raises a bad
magic spin_lock error as reported and discussed here [1].
Initialising the spin lock resolves the issue.
The fix is tested on HiFive Unleashed A00 board with Linux 5.7-rc4
and OpenSBI v0.7
[1]
https://lore.kernel.org/linux-riscv
[ Upstream commit 3b025f2bc98973f181d926192b0ceb6ced0f86d2 ]
Enable PRCI clock driver and serial console by default, so the default
upstream defconfig is bootable to a serial console.
Signed-off-by: Kevin Hilman
Reviewed-by: Christoph Hellwig
Signed-off-by: Paul Walmsley
Signed-off-by: Sasha
From: Kevin Hilman
[ Upstream commit 3b025f2bc98973f181d926192b0ceb6ced0f86d2 ]
Enable PRCI clock driver and serial console by default, so the default
upstream defconfig is bootable to a serial console.
Signed-off-by: Kevin Hilman
Reviewed-by: Christoph Hellwig
Signed-off-by: Paul Walmsley
On Sun, 9 Jun 2019, Christoph Hellwig wrote:
> On Sat, Jun 08, 2019 at 06:49:09PM -0700, Paul Walmsley wrote:
> > On Wed, 5 Jun 2019, Kevin Hilman wrote:
> >
> > > Enable PRCI clock driver and serial console by default, so the default
> > > upstream defconfi
On Sat, Jun 08, 2019 at 06:49:09PM -0700, Paul Walmsley wrote:
> On Wed, 5 Jun 2019, Kevin Hilman wrote:
>
> > Enable PRCI clock driver and serial console by default, so the default
> > upstream defconfig is bootable to a serial console.
> >
> > Signed-off-by: Kev
On Wed, 5 Jun 2019, Kevin Hilman wrote:
> Enable PRCI clock driver and serial console by default, so the default
> upstream defconfig is bootable to a serial console.
>
> Signed-off-by: Kevin Hilman
Thanks, queued for v5.2-rc with Christoph's Reviewed-by:.
- Paul
Palmer,
Kevin Hilman writes:
> Enable PRCI clock driver and serial console by default, so the default
> upstream defconfig is bootable to a serial console.
>
> Signed-off-by: Kevin Hilman
If possible, this would be great to have for v5.2-rc so we have a
bootable upstream defconf
On Wed, Jun 05, 2019 at 10:50:42AM -0700, Kevin Hilman wrote:
> Enable PRCI clock driver and serial console by default, so the default
> upstream defconfig is bootable to a serial console.
>
> Signed-off-by: Kevin Hilman
Looks good:
Reviewed-by: Christoph Hellwig
Enable PRCI clock driver and serial console by default, so the default
upstream defconfig is bootable to a serial console.
Signed-off-by: Kevin Hilman
---
arch/riscv/configs/defconfig | 4
1 file changed, 4 insertions(+)
diff --git a/arch/riscv/configs/defconfig b/arch/riscv/configs
4.19-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit f51ccf46217c28758b1f3b5bc0ccfc00eca658b2 upstream.
The USB-serial console implementation has never reported the actual
terminal settings used. Despite storing the
On Wed, Dec 05, 2018 at 11:36:52AM +0200, Jarkko Nikula wrote:
> On 12/4/18 6:31 PM, Johan Hovold wrote:
> > On Tue, Dec 04, 2018 at 05:15:18PM +0100, Greg Kroah-Hartman wrote:
> >> On Tue, Dec 04, 2018 at 05:00:36PM +0100, Johan Hovold wrote:
> >>> The USB-serial co
If the device used as a serial console gets un/re-binded, then
register_console() will call imx_uart_setup_console() again.
Drop __init so that imx_uart_setup_console() can be safely called
at runtime.
Signed-off-by: Stefan Agner
---
This addresses a kernel panic seen when unbinding/rebinding
3.16.60-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kyle Roeschley
commit 1e23aace21515a8f7615a1de016c0ea8d4e0cc6e upstream.
Added the USB VID and PID for the USB serial console on some National
Instruments devices.
Signed-off-by: Kyle
* Andreas Kemnade [180925 05:32]:
> Hi Tony,
>
> On Mon, 24 Sep 2018 15:03:45 -0700
> Tony Lindgren wrote:
>
> > * Andreas Kemnade [180923 08:12]:
> > > This enables the possibility to have more aggressive runtime pm
> > > by providing p
Hi Tony,
On Mon, 24 Sep 2018 15:03:45 -0700
Tony Lindgren wrote:
> * Andreas Kemnade [180923 08:12]:
> > This enables the possibility to have more aggressive runtime pm
> > by providing proper wakeup irq for the serial console.
>
> Thanks applying to omap-for-v4.20/dt.
* Andreas Kemnade [180923 08:12]:
> This enables the possibility to have more aggressive runtime pm
> by providing proper wakeup irq for the serial console.
Thanks applying to omap-for-v4.20/dt.
FYI, you can now grep wake /proc/interrupts and see the
wakeirq counts increase when they t
This enables the possibility to have more aggressive runtime pm
by providing proper wakeup irq for the serial console.
Signed-off-by: Andreas Kemnade
---
arch/arm/boot/dts/omap3-gta04.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi
b/arch/arm/boot
Hi,
On Tue, Jun 12, 2018 at 10:09 AM, Karthikeyan Ramasubramanian
wrote:
> From: Rajendra Nayak
>
> Add the qup uart node and geni se instance needed to
> support the serial console on the MTP.
>
> Signed-off-by: Rajendra Nayak
> Signed-off-by: Karthikeyan Ramasubramanian
From: Rajendra Nayak
Add the qup uart node and geni se instance needed to
support the serial console on the MTP.
Signed-off-by: Rajendra Nayak
Signed-off-by: Karthikeyan Ramasubramanian
---
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 41 +
arch/arm64/boot/dts
On Thu, May 17, 2018 at 11:04:28AM +0200, Greg Kroah-Hartman wrote:
> On Wed, May 16, 2018 at 01:15:48AM +0100, Ben Hutchings wrote:
> > On Wed, 2018-04-11 at 20:36 +0200, Greg Kroah-Hartman wrote:
> > > 4.4-stable review patch. If anyone has any objections, please let me
> > > know.
> > >
> > >
On Wed, May 16, 2018 at 01:15:48AM +0100, Ben Hutchings wrote:
> On Wed, 2018-04-11 at 20:36 +0200, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Thomas Bogendoerfer
> >
> >
> > [ Upstream comm
On Wed, 2018-04-11 at 20:36 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Thomas Bogendoerfer
>
>
> [ Upstream commit e279e6d98e0cf2c2fe008b3c29042b92f0e17b1d ]
>
> sccnxp driver doesn't get the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kyle Roeschley
commit 1e23aace21515a8f7615a1de016c0ea8d4e0cc6e upstream.
Added the USB VID and PID for the USB serial console on some National
Instruments devices.
Signed-off-by: Kyle
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kyle Roeschley
commit 1e23aace21515a8f7615a1de016c0ea8d4e0cc6e upstream.
Added the USB VID and PID for the USB serial console on some National
Instruments devices.
Signed-off-by: Kyle
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kyle Roeschley
commit 1e23aace21515a8f7615a1de016c0ea8d4e0cc6e upstream.
Added the USB VID and PID for the USB serial console on some National
Instruments devices.
Signed-off-by: Kyle
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Kyle Roeschley
commit 1e23aace21515a8f7615a1de016c0ea8d4e0cc6e upstream.
Added the USB VID and PID for the USB serial console on some National
Instruments devices.
Signed-off-by: Kyle
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Kyle Roeschley
commit 1e23aace21515a8f7615a1de016c0ea8d4e0cc6e upstream.
Added the USB VID and PID for the USB serial console on some National
Instruments devices.
Signed-off-by: Kyle
On Mon, Apr 09, 2018 at 10:23:55AM -0500, Kyle Roeschley wrote:
> Added the USB VID and PID for the USB serial console on some National
> Instruments devices.
>
> Signed-off-by: Kyle Roeschley
Now applied, thanks.
Johan
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Bogendoerfer
[ Upstream commit e279e6d98e0cf2c2fe008b3c29042b92f0e17b1d ]
sccnxp driver doesn't get the correct uart clock rate, if CONFIG_HAVE_CLOCK
is disabled. Correct usage of clk A
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Bogendoerfer
[ Upstream commit e279e6d98e0cf2c2fe008b3c29042b92f0e17b1d ]
sccnxp driver doesn't get the correct uart clock rate, if CONFIG_HAVE_CLOCK
is disabled. Correct usage of clk A
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Bogendoerfer
[ Upstream commit e279e6d98e0cf2c2fe008b3c29042b92f0e17b1d ]
sccnxp driver doesn't get the correct uart clock rate, if CONFIG_HAVE_CLOCK
is disabled. Correct usage of clk
Added the USB VID and PID for the USB serial console on some National
Instruments devices.
Signed-off-by: Kyle Roeschley
---
drivers/usb/serial/cp210x.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
index 06d502b3e913..cc5b2d0d340d
From: Thomas Bogendoerfer
[ Upstream commit e279e6d98e0cf2c2fe008b3c29042b92f0e17b1d ]
sccnxp driver doesn't get the correct uart clock rate, if CONFIG_HAVE_CLOCK
is disabled. Correct usage of clk API to make it work with/without it.
Fixes: 90efa75f7ab0 (serial: sccnxp: Using CLK API for gettin
From: Thomas Bogendoerfer
[ Upstream commit e279e6d98e0cf2c2fe008b3c29042b92f0e17b1d ]
sccnxp driver doesn't get the correct uart clock rate, if CONFIG_HAVE_CLOCK
is disabled. Correct usage of clk API to make it work with/without it.
Fixes: 90efa75f7ab0 (serial: sccnxp: Using CLK API for gettin
From: Thomas Bogendoerfer
[ Upstream commit e279e6d98e0cf2c2fe008b3c29042b92f0e17b1d ]
sccnxp driver doesn't get the correct uart clock rate, if CONFIG_HAVE_CLOCK
is disabled. Correct usage of clk API to make it work with/without it.
Fixes: 90efa75f7ab0 (serial: sccnxp: Using CLK API for gettin
On 3/5/2018 3:43 AM, Rajendra Nayak wrote:
On 03/05/2018 01:29 AM, Bjorn Andersson wrote:
On Wed 21 Feb 22:12 PST 2018, Rajendra Nayak wrote:
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
b/arch/arm64/boot/dts/qcom/sdm845.dtsi
[..]
+ qup_uart2: serial@a84000 {
+
On 03/05/2018 01:29 AM, Bjorn Andersson wrote:
> On Wed 21 Feb 22:12 PST 2018, Rajendra Nayak wrote:
>> diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
>> b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> [..]
>> +qup_uart2: serial@a84000 {
>> +compatible
On Wed 21 Feb 22:12 PST 2018, Rajendra Nayak wrote:
> diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
> b/arch/arm64/boot/dts/qcom/sdm845.dtsi
[..]
> + qup_uart2: serial@a84000 {
> + compatible = "qcom,geni-debug-uart";
> +
Eric Anholt writes:
> [ Unknown signature status ]
> Tuomas Tynkkynen writes:
>
>> The Raspberry Pi 3 uses the 8250-based auxilary UART of the BCM2837 SoC
>> as the primary serial console of the board, so enable it in the
>> multiplatform defconfig.
>>
&
Add the qup uart node and geni se instance needed to
support the serial console on the MTP.
Signed-off-by: Rajendra Nayak
---
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 39 +
arch/arm64/boot/dts/qcom/sdm845.dtsi| 39 +
2 files
Hi,
On Thu, Feb 15, 2018 at 10:05 PM, Rajendra Nayak wrote:
> Add the qup uart node and geni se instance needed to
> support the serial console on the MTP.
>
> Signed-off-by: Rajendra Nayak
> ---
> arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 39
> ++
Add the qup uart node and geni se instance needed to
support the serial console on the MTP.
Signed-off-by: Rajendra Nayak
---
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 39 +
arch/arm64/boot/dts/qcom/sdm845.dtsi| 39 +
2 files
On 02/15/2018 12:41 AM, Bjorn Andersson wrote:
> [..]
>>> +
>>> + qup_1: geni-se@ac {
>> Color me confused. So you're saying here that this is "qup_1".
>> ...but above you turn the pinmux for pins "GPIO4" and "GPIO5" to
>> "qup9", right? So UART2 is on "qup 1" and "qup 9"?
>>
On Tue 13 Feb 16:32 PST 2018, Doug Anderson wrote:
> On Sun, Feb 11, 2018 at 10:28 PM, Rajendra Nayak
> wrote:
[..]
> > +&soc {
> > + geni-se@ac {
> > + serial@a84000 {
> > + status = "okay";
> > + };
> > + };
>
> If others at QC
On 02/14/2018 06:02 AM, Doug Anderson wrote:
> Hi,
>
> On Sun, Feb 11, 2018 at 10:28 PM, Rajendra Nayak
> wrote:
>> Add the qup uart node and geni se instance needed to
>> support the serial console on the MTP.
>>
>> Signed-off-by: Rajendra Nayak
>&g
Hi,
On Sun, Feb 11, 2018 at 10:28 PM, Rajendra Nayak wrote:
> Add the qup uart node and geni se instance needed to
> support the serial console on the MTP.
>
> Signed-off-by: Rajendra Nayak
> ---
> arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 34
>
Add the qup uart node and geni se instance needed to
support the serial console on the MTP.
Signed-off-by: Rajendra Nayak
---
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 34
arch/arm64/boot/dts/qcom/sdm845.dtsi| 39 +
2 files
Tuomas Tynkkynen writes:
> The Raspberry Pi 3 uses the 8250-based auxilary UART of the BCM2837 SoC
> as the primary serial console of the board, so enable it in the
> multiplatform defconfig.
>
> Signed-off-by: Tuomas Tynkkynen
Reviewed-by: Eric Anholt
I'm planning on p
[]..
>> @@ -10,4 +10,46 @@
>> / {
>> model = "Qualcomm Technologies, Inc. SDM845 MTP";
>> compatible = "qcom,sdm845-mtp";
>> +
>> + aliases {
>> + serial0 = &qup_uart2;
>> + };
>> +
>> + chosen {
>> + stdout-path = "serial0";
>> +
On 02/07/2018 01:19 AM, Doug Anderson wrote:
> Hi,
>
> On Tue, Feb 6, 2018 at 11:06 AM, Bjorn Andersson
> wrote:
>> On Tue 06 Feb 10:37 PST 2018, Doug Anderson wrote:
>>
>>> Hi,
>>>
>>> On Fri, Jan 26, 2018 at 2:18 PM, Stephen Boyd wrote:
On 01/25, Rajendra Nayak wrote:
> diff --git a
The Raspberry Pi 3 uses the 8250-based auxilary UART of the BCM2837 SoC
as the primary serial console of the board, so enable it in the
multiplatform defconfig.
Signed-off-by: Tuomas Tynkkynen
---
arch/arm/configs/multi_v7_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch
On Fri, Jan 26, 2018 at 4:18 PM, Stephen Boyd wrote:
> On 01/25, Rajendra Nayak wrote:
>> diff --git a/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
>> b/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
>> new file mode 100644
>> index ..b97f99e6f4b4
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts
On Tue 06 Feb 11:49 PST 2018, Doug Anderson wrote:
> Hi,
>
> On Tue, Feb 6, 2018 at 11:06 AM, Bjorn Andersson
> wrote:
> > On Tue 06 Feb 10:37 PST 2018, Doug Anderson wrote:
> >
> >> Hi,
> >>
> >> On Fri, Jan 26, 2018 at 2:18 PM, Stephen Boyd wrote:
> >> > On 01/25, Rajendra Nayak wrote:
> >> >
Hi,
On Tue, Feb 6, 2018 at 11:06 AM, Bjorn Andersson
wrote:
> On Tue 06 Feb 10:37 PST 2018, Doug Anderson wrote:
>
>> Hi,
>>
>> On Fri, Jan 26, 2018 at 2:18 PM, Stephen Boyd wrote:
>> > On 01/25, Rajendra Nayak wrote:
>> >> diff --git a/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
>> >> b/arch/arm
Hi,
On Wed, Jan 31, 2018 at 8:19 AM, Rajendra Nayak wrote:
> Add the qup uart node and geni se instance needed to
> support the serial console on the MTP.
>
> Signed-off-by: Rajendra Nayak
> ---
> arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 42
> ++
On Tue 06 Feb 10:37 PST 2018, Doug Anderson wrote:
> Hi,
>
> On Fri, Jan 26, 2018 at 2:18 PM, Stephen Boyd wrote:
> > On 01/25, Rajendra Nayak wrote:
> >> diff --git a/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
> >> b/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
> >> new file mode 100644
> >> index
On Mon 29 Jan 00:18 PST 2018, Rajendra Nayak wrote:
> On 01/27/2018 03:48 AM, Stephen Boyd wrote:
> > On 01/25, Rajendra Nayak wrote:
> >> diff --git a/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
> >> b/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
> >> new file mode 100644
> >> index ..b97f
Hi,
On Fri, Jan 26, 2018 at 2:18 PM, Stephen Boyd wrote:
> On 01/25, Rajendra Nayak wrote:
>> diff --git a/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
>> b/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
>> new file mode 100644
>> index ..b97f99e6f4b4
>> --- /dev/null
>> +++ b/arch/arm64/boo
Add the qup uart node and geni se instance needed to
support the serial console on the MTP.
Signed-off-by: Rajendra Nayak
---
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 42 +
arch/arm64/boot/dts/qcom/sdm845.dtsi| 21 +
2 files changed, 63
On 01/27/2018 03:48 AM, Stephen Boyd wrote:
> On 01/25, Rajendra Nayak wrote:
>> diff --git a/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
>> b/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
>> new file mode 100644
>> index ..b97f99e6f4b4
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/qcom/sd
On 01/25, Rajendra Nayak wrote:
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
> b/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
> new file mode 100644
> index ..b97f99e6f4b4
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sdm845-pins.dtsi
> @@ -0,0 +1,32 @@
> +// SPDX-License-I
Add the qup uart node and geni se instance needed to
support the serial console on the MTP.
Signed-off-by: Rajendra Nayak
---
This patch is based on the current proposed DT bindings for
the geni based serial driver [1] and also depends on the GCC
driver [2] which adds dt-bindings/clock/qcom,gcc
3.2.96-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 299d7572e46f98534033a9e65973f13ad1ce9047 upstream.
Make sure to reset the USB-console port pointer when console setup fails
in order to avoid having the struct usb_serial be
3.16.51-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 299d7572e46f98534033a9e65973f13ad1ce9047 upstream.
Make sure to reset the USB-console port pointer when console setup fails
in order to avoid having the struct usb_serial b
On Thu, 2 Nov 2017 20:01:07 +0100
Paul Menzel wrote:
> Dear Greg,
>
>
> Am 02.11.2017 um 17:53 schrieb Greg KH:
> > On Thu, Nov 02, 2017 at 04:39:36PM +0100, Paul Menzel wrote:
>
> >> If I want to output the Linux kernel messages to the serial console, bu
Dear Greg,
Am 02.11.2017 um 17:53 schrieb Greg KH:
On Thu, Nov 02, 2017 at 04:39:36PM +0100, Paul Menzel wrote:
If I want to output the Linux kernel messages to the serial console, but the
`console=ttyS…` line is missing on the Linux command line, is there a way to
activate that during run
On Thu, Nov 02, 2017 at 04:39:36PM +0100, Paul Menzel wrote:
> Dear Linux folks,
>
>
> If I want to output the Linux kernel messages to the serial console, but the
> `console=ttyS…` line is missing on the Linux command line, is there a way to
> activate that during run-ti
Dear Linux folks,
If I want to output the Linux kernel messages to the serial console, but
the `console=ttyS…` line is missing on the Linux command line, is there
a way to activate that during run-time by, for example, using the sysfs
interface?
Kind regards,
Paul
From: Johan Hovold
commit 299d7572e46f98534033a9e65973f13ad1ce9047 upstream.
Make sure to reset the USB-console port pointer when console setup fails
in order to avoid having the struct usb_serial be prematurely freed by
the console code when the device is later disconnected.
Fixes: 73e487fdb75
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 299d7572e46f98534033a9e65973f13ad1ce9047 upstream.
Make sure to reset the USB-console port pointer when console setup fails
in order to avoid having the struct usb_serial b
1 - 100 of 448 matches
Mail list logo
