public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <t.figa@samsung.com>
To: "José Miguel Gonçalves" <jose.goncalves@inov.pt>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, "Heiko Stübner" <heiko@sntech.de>,
	"Sylwester Nawrocki" <s.nawrocki@samsung.com>
Subject: Re: [PATCH] serial: samsung: add support for manual RTS setting
Date: Wed, 18 Sep 2013 11:40:51 +0200	[thread overview]
Message-ID: <2325055.YfxTctqBtd@amdc1227> (raw)
In-Reply-To: <5238A8B1.9080105@inov.pt>

On Tuesday 17 of September 2013 20:08:33 José Miguel Gonçalves wrote:
> On 17-09-2013 16:21, Tomasz Figa wrote:
> > I had the following scenario in mind:
> > 1) enable CRTSCTS,
> > 2) set RTS status using the IOCTL,
> > 3) disable CRTSCTS,
> > 4) do something,
> > 5) enable CRTSCTS again.
> > 
> > I would expect that the value set in point 2 would be still valid after
> > point 5, while it will be reset.
> 
> Maybe I'm missing something but, as I see it, as soon as you enable AFC
> in the UART controller the RTS pin is no more manually controllable, so
> after point 5 the pin is set automattically by the controller according
> with the Rx FIFO contents. Don't you want to say instead that the value
> set in 2) will be valid in 4)?

Ahh, right, I inverted CRTSCTS bit polarity in points 1, 3 and 5. It should 
be:
1) disable CRTSCTS,
2) set RTS status using the IOCTL,
3) enable CRTSCTS,
4) do something,
5) disable CRTSCTS again.

> >> Regarding port capability, if it's decided to validate it in
> >> s3c24xx_serial_get_mctrl() and s3c24xx_serial_set_mctrl() it should
> >> also
> >> be validated here. The question is how to validate for the full
> >> spectrum
> >> of SoCs that this driver supports?
> > 
> > Hmm, since the driver is already broken in this aspect, ignoring this
> > in
> > your patch might be fine for now. A follow up patch fixing this would
> > be
> > welcome, though. However I don't have any good idea how to implement
> > this at the moment.
> > 
> > First thing that comes to my mind is using the variant data structures
> > to store information about per port capability (different port FIFO
> > sizes are already handled like this), but this would imply splitting
> > some of the groups, as S5PC100 supports modem control for different
> > subset of ports than S3C64xx, while they both use the same variant
> > data.
> > 
> > Using device tree, this could be passed as an extra property, but some
> > of the platforms using samsung serial driver can be booted without
> > device tree, so it wouldn't cover all the cases.
> 
> So, as I understand, for now is enough to resubmit the patch with the
> UMCON register setting in s3c24xx_serial_set_termios() preserving the
> previous manual setting of the RTS pin, correct? I was thinking in
> something like this:
> 
>      umcon = rd_regb(port, S3C2410_UMCON);
>      if (termios->c_cflag & CRTSCTS) {
>          umcon |= S3C2410_UMCOM_AFC;
>          umcon &= ~S3C2412_UMCON_AFC_8; // Disable RTS when RX FIFO
> contains 63 bytes } else {
>          umcon &= ~S3C2410_UMCOM_AFC;
>      }
>      wr_regl(port, S3C2410_UMCON, umcon);

Yes, this looks fine.

Best regards,
Tomasz


      reply	other threads:[~2013-09-18  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 10:08 [PATCH] serial: samsung: add support for manual RTS setting José Miguel Gonçalves
2013-09-17 10:18 ` Tomasz Figa
2013-09-17 13:03   ` José Miguel Gonçalves
2013-09-17 15:21     ` Tomasz Figa
2013-09-17 19:08       ` José Miguel Gonçalves
2013-09-18  9:40         ` Tomasz Figa [this message]

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=2325055.YfxTctqBtd@amdc1227 \
    --to=t.figa@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=jose.goncalves@inov.pt \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=s.nawrocki@samsung.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