From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Lemon <jonathan.lemon@gmail.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Cc: netdev@vger.kernel.org,
Richard Cochran <richardcochran@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] ptp: ocp: don't allow on S390
Date: Thu, 19 Aug 2021 15:58:32 -0700 [thread overview]
Message-ID: <0e6bd492-a3f5-845c-9d93-50f1cc182a62@infradead.org> (raw)
In-Reply-To: <20210816214103.w54pfwcuge4nqevw@bsd-mbp.dhcp.thefacebook.com>
On 8/16/21 2:41 PM, Jonathan Lemon wrote:
> On Mon, Aug 16, 2021 at 02:15:51PM -0700, Randy Dunlap wrote:
>> On 8/16/21 2:09 PM, Jonathan Lemon wrote:
>>> On Fri, Aug 13, 2021 at 01:30:26PM -0700, Randy Dunlap wrote:
>>>> There is no 8250 serial on S390. See commit 1598e38c0770.
>>>
>>> There's a 8250 serial device on the PCI card. Its been
>>> ages since I've worked on the architecture, but does S390
>>> even support PCI?
>>
>> Yes, it does.
>>
>>>> Is this driver useful even without 8250 serial?
>>>
>>> The FB timecard has an FPGA that will internally parse the
>>> GNSS strings and correct the clock, so the PTP clock will
>>> work even without the serial devices.
>>>
>>> However, there are userspace tools which want to read the
>>> GNSS signal (for holdolver and leap second indication),
>>> which is why they are exposed.
>>
>> So what do you recommend here?
>
> Looking at 1598e38c0770, it appears the 8250 console is the
> problem. Couldn't S390 be fenced by SERIAL_8250_CONSOLE, instead
> of SERIAL_8250, which would make the 8250 driver available?
OK, that sounds somewhat reasonable.
> For now, just disabling the driver on S390 sounds reasonable.
>
S390 people, how does this look to you?
This still avoids having serial 8250 console conflicting
with S390's sclp console.
(reference commit 1598e38c0770)
---
drivers/tty/serial/8250/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20210819.orig/drivers/tty/serial/8250/Kconfig
+++ linux-next-20210819/drivers/tty/serial/8250/Kconfig
@@ -6,7 +6,6 @@
config SERIAL_8250
tristate "8250/16550 and compatible serial support"
- depends on !S390
select SERIAL_CORE
select SERIAL_MCTRL_GPIO if GPIOLIB
help
@@ -85,6 +84,7 @@ config SERIAL_8250_FINTEK
config SERIAL_8250_CONSOLE
bool "Console on 8250/16550 and compatible serial port"
depends on SERIAL_8250=y
+ depends on !S390
select SERIAL_CORE_CONSOLE
select SERIAL_EARLYCON
help
--
~Randy
next prev parent reply other threads:[~2021-08-19 22:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 20:30 [PATCH] ptp: ocp: don't allow on S390 Randy Dunlap
2021-08-16 10:20 ` patchwork-bot+netdevbpf
2021-08-16 21:09 ` Jonathan Lemon
2021-08-16 21:15 ` Randy Dunlap
2021-08-16 21:41 ` Jonathan Lemon
2021-08-19 22:58 ` Randy Dunlap [this message]
2021-08-20 8:02 ` Christian Borntraeger
2021-08-20 9:59 ` Niklas Schnelle
2021-08-20 10:45 ` Arnd Bergmann
2021-08-20 15:31 ` Richard Cochran
2021-08-24 21:48 ` Randy Dunlap
2021-08-25 10:55 ` Arnd Bergmann
2021-08-25 17:08 ` Jonathan Lemon
2021-08-25 17:29 ` Randy Dunlap
2021-08-25 18:05 ` Arnd Bergmann
2021-08-25 20:40 ` Jonathan Lemon
2021-08-25 20:45 ` Randy Dunlap
2021-08-25 21:14 ` Jonathan Lemon
2021-08-25 23:22 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e6bd492-a3f5-845c-9d93-50f1cc182a62@infradead.org \
--to=rdunlap@infradead.org \
--cc=borntraeger@de.ibm.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathan.lemon@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).