From: Maarten Brock <m.brock@vanmierlo.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sean Anderson <sean.anderson@seco.com>,
Peter Korsgaard <peter.korsgaard@barco.com>,
Peter Korsgaard <peter@korsgaard.com>,
linux-serial@vger.kernel.org,
Alexander Sverdlin <alexander.sverdlin@nokia.com>,
Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH 5/5] tty: serial: uartlite: Prevent changing fixed parameters
Date: Mon, 09 Aug 2021 10:58:26 +0200 [thread overview]
Message-ID: <29eb6890d4ff05dc550e18e57eaf0fb6@vanmierlo.com> (raw)
In-Reply-To: <YQONMMetaYI4aLMJ@kroah.com>
On 2021-07-30 07:25, Greg Kroah-Hartman wrote:
> On Thu, Jul 29, 2021 at 11:43:08AM -0400, Sean Anderson wrote:
>>
>>
>> On 7/29/21 11:32 AM, Greg Kroah-Hartman wrote:
>> > On Thu, Jul 29, 2021 at 11:26:59AM -0400, Sean Anderson wrote:
>> >>
>> >>
>> >> On 7/29/21 11:01 AM, Greg Kroah-Hartman wrote:
>> >> > On Fri, Jul 23, 2021 at 06:31:51PM -0400, Sean Anderson wrote:
>> >> > Through all of this, you are warning that nothing is supported, yet you
>> >> > are continuing on as if all of this worked just fine.
>> >>
>> >> We don't. The idea is that we see if (e.g.) CSIZE is something the
>> >> hardware can't produce, warn about it (once), and then set it to what we
>> >> can support.
>> >
>> > So you are ignoring what the user wanted, and doing whatever you wanted.
>> >
>> > As you can only support one setting, why even care? Just set it to what
>> > you want and ignore userspace's requests.
>>
>> That is exactly what we are doing. We set it to what we can support
>> and
>> ignore what userspace requested.
>
> If you can only support one set of options, just set it and always fail
> the tcsetattr call which will allow userspace to know it shouldn't have
> tried to do that.
I have to disagree strongly here against *always*. If the user calls
tcsetattr
to set it to exactly what is supported it *should not fail*. Every
decent
(terminal) program will start by setting or getting the initial
settings.
Maarten
next prev parent reply other threads:[~2021-08-09 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 22:31 [PATCH 0/5] tty: serial: uartlite: Disable changing fixed parameters Sean Anderson
2021-07-23 22:31 ` [PATCH 1/5] dt-bindings: serial: uartlite: Convert to json-schema Sean Anderson
2021-07-23 22:31 ` [PATCH 2/5] dt-bindings: serial: uartlite: Add properties for synthesis-time parameters Sean Anderson
2021-07-26 12:30 ` Michal Simek
2021-07-26 15:16 ` Sean Anderson
2021-07-23 22:31 ` [PATCH 3/5] sh: j2: Update uartlite binding with data and parity properties Sean Anderson
2021-07-23 22:31 ` [PATCH 4/5] tty: serial: uartlite: Initialize termios with fixed synthesis parameters Sean Anderson
2021-07-26 20:53 ` Sean Anderson
2021-07-29 15:02 ` Greg Kroah-Hartman
2021-07-23 22:31 ` [PATCH 5/5] tty: serial: uartlite: Prevent changing fixed parameters Sean Anderson
2021-07-29 15:01 ` Greg Kroah-Hartman
2021-07-29 15:26 ` Sean Anderson
2021-07-29 15:32 ` Greg Kroah-Hartman
2021-07-29 15:43 ` Sean Anderson
2021-07-30 5:25 ` Greg Kroah-Hartman
2021-07-30 15:33 ` Sean Anderson
2021-08-09 8:58 ` Maarten Brock [this message]
2021-07-26 14:19 ` [PATCH 0/5] tty: serial: uartlite: Disable " Michal Simek
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=29eb6890d4ff05dc550e18e57eaf0fb6@vanmierlo.com \
--to=m.brock@vanmierlo.com \
--cc=alexander.sverdlin@nokia.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=peter.korsgaard@barco.com \
--cc=peter@korsgaard.com \
--cc=sean.anderson@seco.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