From: Bongsu Jeon <bongsu.jeon2@gmail.com>
To: linux-nfc@lists.01.org
Subject: [linux-nfc] Re: [PATCH net-next 1/2] dt-bindings: net: nfc: s3fwrn5: Support a UART interface
Date: Wed, 25 Nov 2020 12:08:38 +0900 [thread overview]
Message-ID: <CACwDmQDWtfa8tXkG8W+EQxjdYJ6rkVgN9PjOVQdK8CwUXAURMg@mail.gmail.com> (raw)
In-Reply-To: 20201124114151.GA32873@kozik-lap
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On 11/24/20, krzk@kernel.org <krzk@kernel.org> wrote:
> On Tue, Nov 24, 2020@08:39:40PM +0900, Bongsu Jeon wrote:
>> On Mon, Nov 23, 2020@5:02 PM krzk@kernel.org <krzk@kernel.org> wrote:
>> >
>> > On Mon, Nov 23, 2020@04:55:26PM +0900, Bongsu Jeon wrote:
> > > examples:
>> > > - |
>> > > #include <dt-bindings/gpio/gpio.h>
>> > > @@ -71,3 +81,17 @@ examples:
>> > > wake-gpios = <&gpj0 2 GPIO_ACTIVE_HIGH>;
>> > > };
>> > > };
>> > > + # UART example on Raspberry Pi
>> > > + - |
>> > > + &uart0 {
>> > > + status = "okay";
>> > > +
>> > > + s3fwrn82_uart {
>> >
>> > Just "bluetooth" to follow Devicetree specification.
>> Sorry. I don't understand this comment.
>> Could you explain it?
>> Does it mean i need to refer to the net/broadcom-bluetooth.txt?
>
> The node name should be "bluetooth", not "s3fwrn82_uart", because of
> Devicetree naming convention - node names should represent generic class
> of a device.
>
Actually, RN82 is the nfc device.
So, is it okay to use the name as nfc instead of Bluetooth?
> Best regards,
> Krzysztof
>
>
next reply other threads:[~2020-11-25 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 3:08 Bongsu Jeon [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-25 7:37 [linux-nfc] Re: [PATCH net-next 1/2] dt-bindings: net: nfc: s3fwrn5: Support a UART interface Krzysztof Kozlowski
2020-11-24 11:41 krzk
2020-11-24 11:39 Bongsu Jeon
2020-11-23 8:01 krzk
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=CACwDmQDWtfa8tXkG8W+EQxjdYJ6rkVgN9PjOVQdK8CwUXAURMg@mail.gmail.com \
--to=bongsu.jeon2@gmail.com \
--cc=linux-nfc@lists.01.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 read-only IMAP folder(s) and NNTP newsgroup(s).