public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Debjeet Banerjee <debjeetbanerjee48@gmail.com>
Cc: dtwlin@gmail.com, johan@kernel.org, elder@kernel.org,
	greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: uart: document c_cflag handling in set_termios
Date: Sun, 26 Apr 2026 21:16:05 +0200	[thread overview]
Message-ID: <2026042618-whole-cassette-b15e@gregkh> (raw)
In-Reply-To: <20260419032632.35351-1-debjeetbanerjee48@gmail.com>

On Sun, Apr 19, 2026 at 08:56:32AM +0530, Debjeet Banerjee wrote:
> gb_tty_set_termios() derives UART line configuration from a subset of
> termios->c_cflag bits, namely CSIZE, CSTOPB, PARENB, PARODD, CMSPAR,
> CRTSCTS, CLOCAL and CBAUD. Other c_cflag bits are not interpreted by
> the driver and are not represented in the Greybus UART protocol
> messages.
> 
> The existing FIXME suggests clearing unsupported bits from termios.
> However, the driver already limits its behavior to the supported subset
> when constructing line coding, and unused bits are effectively ignored.
> No invalid or unsupported values are propagated to the hardware.
> 
> Replace the FIXME with a comment documenting which c_cflag bits are
> consumed by the driver and clarifying that other bits are ignored.

Ignoring is fine, but shouldn't the bits be cleared to let userspace
know about this?  I think that's why we wrote that FIXME all so long
ago.

thanks,

greg k-h

  reply	other threads:[~2026-04-27  3:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-19  3:26 [PATCH] staging: greybus: uart: document c_cflag handling in set_termios Debjeet Banerjee
2026-04-26 19:16 ` Greg KH [this message]
2026-04-27  4:15   ` Debjeet Banerjee
2026-04-27  4:54   ` [PATCH v2] staging: greybus: uart: clear unsupported c_cflag bits " Debjeet Banerjee

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=2026042618-whole-cassette-b15e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=debjeetbanerjee48@gmail.com \
    --cc=dtwlin@gmail.com \
    --cc=elder@kernel.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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