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: Tue, 24 Nov 2020 20:39:40 +0900 [thread overview]
Message-ID: <CACwDmQBh77pqivk=bBv3SJ14HLucY42jZyEaKAX+n=yS3TSqFw@mail.gmail.com> (raw)
In-Reply-To: 20201123080123.GA5656@kozik-lap
[-- Attachment #1: Type: text/plain, Size: 2421 bytes --]
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:
> > Since S3FWRN82 NFC Chip, The UART interface can be used.
> > S3FWRN82 supports I2C and UART interface.
> >
> > Signed-off-by: Bongsu Jeon <bongsu.jeon@samsung.com>
> > ---
> > .../bindings/net/nfc/samsung,s3fwrn5.yaml | 28 +++++++++++++++++--
> > 1 file changed, 26 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/net/nfc/samsung,s3fwrn5.yaml b/Documentation/devicetree/bindings/net/nfc/samsung,s3fwrn5.yaml
> > index cb0b8a560282..37b3e5ae5681 100644
> > --- a/Documentation/devicetree/bindings/net/nfc/samsung,s3fwrn5.yaml
> > +++ b/Documentation/devicetree/bindings/net/nfc/samsung,s3fwrn5.yaml
> > @@ -13,6 +13,7 @@ maintainers:
> > properties:
> > compatible:
> > const: samsung,s3fwrn5-i2c
> > + const: samsung,s3fwrn82-uart
>
> This does not work, you need to use enum. Did you run@least
> dt_bindings_check?
>
Sorry. I didn't. I fixed it as below and ran dt_bindings_check.
compatible:
oneOf:
- enum:
- samsung,s3fwrn5-i2c
- samsung,s3fwrn82
> The compatible should be just "samsung,s3fwrn82". I think it was a
> mistake in the first s3fwrn5 submission to add a interface to
> compatible.
>
Ok. I will change the name.
> >
> > en-gpios:
> > maxItems: 1
> > @@ -47,10 +48,19 @@ additionalProperties: false
> > required:
> > - compatible
> > - en-gpios
> > - - interrupts
> > - - reg
> > - wake-gpios
> >
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + const: samsung,s3fwrn5-i2c
> > + then:
> > + required:
> > + - interrupts
> > + - reg
> > +
> > 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?
>
> Best regards,
> Krzysztof
next reply other threads:[~2020-11-24 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 11:39 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-25 3:08 Bongsu Jeon
2020-11-24 11:41 krzk
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='CACwDmQBh77pqivk=bBv3SJ14HLucY42jZyEaKAX+n=yS3TSqFw@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).