From: Gabor Juhos <juhosg@openwrt.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] tty: ar933x_uart: add device tree support and binding documentation
Date: Sat, 24 Aug 2013 13:53:45 +0200 [thread overview]
Message-ID: <52189EC9.5040906@openwrt.org> (raw)
In-Reply-To: <80D7C583-FF16-4789-B8D1-2D0881DAD8F0@codeaurora.org>
2013.09.04. 0:16 keltezéssel, Kumar Gala írta:
>
> On Aug 29, 2013, at 4:48 AM, Gabor Juhos wrote:
>
>> Modify the probe routine to get the port line number
>> from device tree if the 'of_node' is populated in the
>> platform device. The driver can be built as module,
>> thus add an OF specific module device table as well
>> to support module auto loading.
>>
>> This makes it possible to use the driver for AR9330
>> UART devices specified in device tree.
>>
>> Cc: devicetree@vger.kernel.org
>> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
>> ---
>> Changes since v1:
>> - move the doc from bindings/tty/serial to bindings/serial
>>
>> The patch is agains the 'tty-next' branch of the
>> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tree
>> ---
>> .../devicetree/bindings/serial/qca,ar9330-uart.txt | 34 ++++++++++++++++++++
>> drivers/tty/serial/ar933x_uart.c | 28 ++++++++++++++--
>> 2 files changed, 59 insertions(+), 3 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/serial/qca,ar9330-uart.txt
>>
>> diff --git a/Documentation/devicetree/bindings/serial/qca,ar9330-uart.txt b/Documentation/devicetree/bindings/serial/qca,ar9330-uart.txt
>> new file mode 100644
>> index 0000000..c5e032c
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/serial/qca,ar9330-uart.txt
>> @@ -0,0 +1,34 @@
>> +* Qualcomm Atheros AR9330 High-Speed UART
>> +
>> +Required properties:
>> +
>> +- compatible: Must be "qca,ar9330-uart"
>
> If the driver is called ar933x, is there a reason not to do so with the compatible and binding spec?
Yes, there is a reason, the compatible string should not contain wildcards. At
least the devicetree.org wiki [1] says the following:
Warning: Don't use wildcard compatible values, like "fsl,mpc83xx-uart" or
similar. Silicon vendors will invariably make a change that breaks your wildcard
assumptions the moment it is too late to change it. Instead, choose a specific
silicon implementations and make all subsequent silicon compatible with it.
Additionally, Grant Likely wrote the same thing here basically:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-January/082265.html
-Gabor
1. http://devicetree.org/Device_Tree_Usage#Understanding_the_compatible_Property
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-09-05 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 9:48 [PATCH v2] tty: ar933x_uart: add device tree support and binding documentation Gabor Juhos
2013-08-30 21:13 ` Greg Kroah-Hartman
2013-08-30 21:49 ` Gabor Juhos
2013-08-31 1:31 ` Greg Kroah-Hartman
2013-08-31 7:19 ` Gabor Juhos
2013-09-03 22:15 ` Kumar Gala
2013-09-03 22:16 ` Kumar Gala
2013-08-24 11:53 ` Gabor Juhos [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=52189EC9.5040906@openwrt.org \
--to=juhosg@openwrt.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.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 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.