All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-sh@vger.kernel.org, gregkh@linuxfoundation.org,
	geert@glider.be, laurent.pinchart@ideasonboard.com,
	linux-serial@vger.kernel.org, jslaby@suse.cz
Subject: Re: [PATCH v2 00/05] serial: sh-sci: Hardware flow control update V2
Date: Thu, 19 Mar 2015 15:57:19 +0000	[thread overview]
Message-ID: <550AF1DF.4070509@hurleysoftware.com> (raw)
In-Reply-To: <20150319014933.14235.44835.sendpatchset@little-apple>

Hi Magnus,

On 03/18/2015 09:49 PM, Magnus Damm wrote:
> serial: sh-sci: Hardware flow control update V2
> 
> [PATCH v2 01/05] serial: sh-sci: Break out default CTS/RTS pin setup
> [PATCH v2 02/05] serial: sh-sci: Fix default RTS handling
> [PATCH v2 03/05] serial: sh-sci: Expose default CTS pin
> [PATCH v2 04/05] serial: sh-sci: Add SCIFA/SCIFB CTS/RTS pin setup
> [PATCH v2 05/05] serial: sh-sci: Expose SCIFA/SCIFB CTS pin
> 
> These patches are my latest take at improving CTS/RTS pin handling in
> the SCIF driver. The goal for these patches is to improve the default
> hardware flow control handling and also add CTS/RTS support for SCIFA/SCIFB.

The serial core expects RTS pin control to be implemented via the driver's
set_mctrl() method, and will take care of raising and lowering it when
necessary.

Regards,
Peter Hurley


WARNING: multiple messages have this Message-ID (diff)
From: Peter Hurley <peter@hurleysoftware.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-sh@vger.kernel.org, gregkh@linuxfoundation.org,
	geert@glider.be, laurent.pinchart@ideasonboard.com,
	linux-serial@vger.kernel.org, jslaby@suse.cz
Subject: Re: [PATCH v2 00/05] serial: sh-sci: Hardware flow control update V2
Date: Thu, 19 Mar 2015 11:57:19 -0400	[thread overview]
Message-ID: <550AF1DF.4070509@hurleysoftware.com> (raw)
In-Reply-To: <20150319014933.14235.44835.sendpatchset@little-apple>

Hi Magnus,

On 03/18/2015 09:49 PM, Magnus Damm wrote:
> serial: sh-sci: Hardware flow control update V2
> 
> [PATCH v2 01/05] serial: sh-sci: Break out default CTS/RTS pin setup
> [PATCH v2 02/05] serial: sh-sci: Fix default RTS handling
> [PATCH v2 03/05] serial: sh-sci: Expose default CTS pin
> [PATCH v2 04/05] serial: sh-sci: Add SCIFA/SCIFB CTS/RTS pin setup
> [PATCH v2 05/05] serial: sh-sci: Expose SCIFA/SCIFB CTS pin
> 
> These patches are my latest take at improving CTS/RTS pin handling in
> the SCIF driver. The goal for these patches is to improve the default
> hardware flow control handling and also add CTS/RTS support for SCIFA/SCIFB.

The serial core expects RTS pin control to be implemented via the driver's
set_mctrl() method, and will take care of raising and lowering it when
necessary.

Regards,
Peter Hurley


  parent reply	other threads:[~2015-03-19 15:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  1:49 [PATCH v2 00/05] serial: sh-sci: Hardware flow control update V2 Magnus Damm
2015-03-19  1:49 ` Magnus Damm
2015-03-19  1:49 ` [PATCH v2 01/05] serial: sh-sci: Break out default CTS/RTS pin setup Magnus Damm
2015-03-19  1:49   ` Magnus Damm
2015-03-19  1:49 ` [PATCH v2 02/05] serial: sh-sci: Fix default RTS handling Magnus Damm
2015-03-19  1:49   ` Magnus Damm
2015-03-19  1:50 ` [PATCH v2 03/05] serial: sh-sci: Expose default CTS pin Magnus Damm
2015-03-19  1:50   ` Magnus Damm
2015-03-19  1:50 ` [PATCH v2 04/05] serial: sh-sci: Add SCIFA/SCIFB CTS/RTS pin setup Magnus Damm
2015-03-19  1:50   ` Magnus Damm
2015-03-19  1:50 ` [PATCH v2 05/05] serial: sh-sci: Expose SCIFA/SCIFB CTS pin Magnus Damm
2015-03-19  1:50   ` Magnus Damm
2015-03-19 15:57 ` Peter Hurley [this message]
2015-03-19 15:57   ` [PATCH v2 00/05] serial: sh-sci: Hardware flow control update V2 Peter Hurley

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=550AF1DF.4070509@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=geert@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.