linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Rob Herring <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, service@rdamicro.com,
	zhao_steven@263.net,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-serial@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 4/6] dt-bindings: serial: Document RDA Micro UART
Date: Fri, 30 Jun 2017 13:12:33 +0200	[thread overview]
Message-ID: <e8b8eb0c-0362-0cfb-4d18-3e1ab2b77412@suse.de> (raw)
In-Reply-To: <20170629201051.cfr37kh2gozompqo@rob-hp-laptop>

Am 29.06.2017 um 22:10 schrieb Rob Herring:
> On Tue, Jun 27, 2017 at 02:55:18AM +0200, Andreas Färber wrote:
>> Add an initial binding for the RDA8810PL UART.
>>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> ---
>>  Documentation/devicetree/bindings/serial/rda-uart.txt | 13 +++++++++++++
>>  1 file changed, 13 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/serial/rda-uart.txt
>>
>> diff --git a/Documentation/devicetree/bindings/serial/rda-uart.txt b/Documentation/devicetree/bindings/serial/rda-uart.txt
>> new file mode 100644
>> index 000000000000..6840a8aee035
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/serial/rda-uart.txt
>> @@ -0,0 +1,13 @@
>> +RDA Micro UART
>> +
>> +Required properties:
>> +- compatible :  "rda,8810pl-uart" for RDA8810PL
>> +- reg        :  Offset and length of the register set for the device.
> 
> No clocks or interrupts?

Not yet. I've only pieced together an earlycon driver so far, no full
serial driver. The .dtsi doesn't even have an interrupt-controller node
yet - wasn't clear to me whether this SoC even has a GIC and, if so,
where, from the downstream pre-DT code.

Regards,
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-06-30 11:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27  0:55 [PATCH 0/6] ARM: Initial RDA8810PL and Orange Pi 2G-IoT enablement Andreas Färber
2017-06-27  0:55 ` [PATCH 1/6] dt-bindings: Add RDA Micro vendor prefix Andreas Färber
2017-06-29 20:08   ` Rob Herring
2017-06-27  0:55 ` [PATCH 2/6] dt-bindings: arm: Document RDA8810PL and Orange Pi 2G-IoT Andreas Färber
2017-06-29 20:09   ` Rob Herring
2017-06-27  0:55 ` [PATCH 3/6] ARM: Prepare RDA8810PL Andreas Färber
2017-06-27  0:55 ` [PATCH 4/6] dt-bindings: serial: Document RDA Micro UART Andreas Färber
2017-06-29 20:10   ` Rob Herring
2017-06-30 11:12     ` Andreas Färber [this message]
2017-06-30 14:27       ` Rob Herring
2017-07-02  1:52         ` Andreas Färber
2017-07-05 14:12           ` Rob Herring
2017-06-27  0:55 ` [PATCH 5/6] tty: serial: Add RDA Micro UART driver Andreas Färber
2017-06-27  0:55 ` [PATCH 6/6] ARM: dts: Add RDA8810PL and Orange Pi 2G-IoT Andreas Färber

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=e8b8eb0c-0362-0cfb-4d18-3e1ab2b77412@suse.de \
    --to=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=service@rdamicro.com \
    --cc=zhao_steven@263.net \
    /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).