linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: afaerber@suse.de (Andreas Färber)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 2/4] ARM64: dts: meson-gx: add the serial CTS and RTS pin groups
Date: Sun, 15 Jan 2017 23:50:17 +0100	[thread overview]
Message-ID: <b74ed3d7-ea69-5a5b-a313-baab3a9e2396@suse.de> (raw)
In-Reply-To: <20170115223255.10350-3-martin.blumenstingl@googlemail.com>

Am 15.01.2017 um 23:32 schrieb Martin Blumenstingl:
> This adds pinctrl group nodes for the CTS and RTS pins of each serial
> controller. This makes it possible to enable the CTS and RTS pins which
> are controlled by the serial controller hardware (through the meson_uart
> driver).
> 
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>

Tested-by: Andreas F?rber <afaerber@suse.de>

Thanks,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)

  reply	other threads:[~2017-01-15 22:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15 22:32 [PATCH 0/4] Bluetooth support for GXBB/GXL/GXM based devices Martin Blumenstingl
2017-01-15 22:32 ` [PATCH 1/4] tty: serial: meson: allow baud-rates higher than 115200 Martin Blumenstingl
2017-01-15 22:48   ` Andreas Färber
2017-01-18 21:44   ` Kevin Hilman
2017-01-15 22:32 ` [PATCH 2/4] ARM64: dts: meson-gx: add the serial CTS and RTS pin groups Martin Blumenstingl
2017-01-15 22:50   ` Andreas Färber [this message]
2017-01-18 21:52     ` Kevin Hilman
2017-01-15 22:32 ` [PATCH 3/4] ARM64: dts: meson-gx-p23x-q20x: enable the Bluetooth module Martin Blumenstingl
2017-01-16  0:47   ` Andreas Färber
2017-01-16  9:44     ` Martin Blumenstingl
2017-01-15 22:32 ` [PATCH 4/4] ARM64: dts: meson-gxbb-vega-s95: " Martin Blumenstingl
2017-01-15 22:55   ` Andreas Färber
2017-01-18 11:25 ` [PATCH 0/4] Bluetooth support for GXBB/GXL/GXM based devices Martin Blumenstingl
2017-01-18 22:02   ` Kevin Hilman
2017-01-19 13:39     ` Greg KH

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=b74ed3d7-ea69-5a5b-a313-baab3a9e2396@suse.de \
    --to=afaerber@suse.de \
    --cc=linus-amlogic@lists.infradead.org \
    /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).