Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Ayush Singh <ayush@beagleboard.org>
Cc: "Jason Kridner" <jkridner@beagleboard.org>,
	robertcnelson@gmail.com, "Johan Hovold" <johan@kernel.org>,
	"Alex Elder" <elder@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Tamir Duberstein" <tamird@kernel.org>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Onur Özkan" <work@onurozkan.dev>,
	"Eric Biggers" <ebiggers@kernel.org>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Ayush Singh" <ayush@beagleboard.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	greybus-dev@lists.linaro.org, linux-kernel@vger.kernel.org,
	rust-for-linux@vger.kernel.org, linux-crypto@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 7/7] dt-bindings: beagle: Add BeagleConnect Freedom
Date: Fri, 21 Aug 2026 18:20:58 +0100	[thread overview]
Message-ID: <20260821-zesty-penalty-a9a485150545@spud> (raw)
In-Reply-To: <f93c5f18-580c-46ce-971f-8e2073485b4b@beagleboard.org>

[-- Attachment #1: Type: text/plain, Size: 3024 bytes --]

On Fri, Aug 21, 2026 at 11:01:16AM +0530, Ayush Singh wrote:
> On 8/21/26 12:03 AM, Conor Dooley wrote:
> 
> > On Thu, Aug 20, 2026 at 02:55:49PM +0530, Ayush Singh wrote:
> > > Add devicetree bindings for the BeagleBoard.org BeagleConnect Freedom,
> > > a wireless-enabled board based on the TI CC1352P7. The board exposes an
> > > MCU that can be attached to a host over USB, UART, SPI or I2C, and is
> > > described as a child node of the corresponding bus.
> > > 
> > > Signed-off-by: Ayush Singh <ayush@beagleboard.org>
> > > ---
> > >   .../beagle/beagle,beagleconnect-freedom.yaml       | 30 ++++++++++++++++++++++
> > >   MAINTAINERS                                        |  1 +
> > >   2 files changed, 31 insertions(+)
> > > 
> > > diff --git a/Documentation/devicetree/bindings/beagle/beagle,beagleconnect-freedom.yaml b/Documentation/devicetree/bindings/beagle/beagle,beagleconnect-freedom.yaml
> > > new file mode 100644
> > > index 000000000000..5a246f81261e
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/beagle/beagle,beagleconnect-freedom.yaml
> > > @@ -0,0 +1,30 @@
> > > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/beagle/beagle,beagleconnect-freedom.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: BeagleBoard.org BeagleConnect Freedom
> > > +
> > > +description:
> > > +  The BeagleBoard.org BeagleConnect Freedom board connected over USB, UART, SPI or I2C.
> > > +
> > > +maintainers:
> > > +  - Ayush Singh <ayush@beagleboard.org>
> > > +
> > > +properties:
> > > +  compatible:
> > > +    const: beagle,beagleconnect-freedom
> > These compatible only devices always look suspect to me, I feel like
> > these things probably at least have an optional regulator if the power
> > source for the freedom is provided by the device running linux.
> 
> Well, the power source can be provided, yes, so will add that. In my
> testing, I was powering the BeagleConnect Freedom [0] via USB to view logs.
> 
> 
> > You're also short the required properties for dealing with anything
> > other than uart, so spi or i2c. (I assume USB doesn't need devicetree to
> > function).
> 
> I have only tested with UART at the moment. Is just having
> `additional_properties: true` sufficient? I think the reg property is the

No, only bindings intended to be included by others should have that.
You should ref spi-peripheral-props if anything is relevant and have
"{additional,unevaluated}Properties: false" depending on whether or not
anything other than reg is.

> only thing SPI and I2C will require setting here.

Ye, then add a "reg: maxItems: 1" for those cases then.

pw-bot: changes-requested

Cheers,
Conor.

> 
> 
> > pw-bot: changes-requested
> > 
> > Thanks,
> > Conor.
> 
> 
> Best Regards,
> 
> Ayush Singh
> 
> 
> [0]: https://www.beagleboard.org/boards/beagleconnect-freedom
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-08-21 17:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  9:25 [PATCH 0/7] Add Greybus Sotfsvc and UART Node drivers Ayush Singh
2026-08-20  9:25 ` [PATCH 1/7] greybus: connection: Export gb_connection_get() and gb_connection_put() Ayush Singh
2026-08-20  9:41   ` sashiko-bot
2026-08-20  9:25 ` [PATCH 2/7] greybus: connection: Add gb_connection_hd_find_by_intf() Ayush Singh
2026-08-20  9:32   ` sashiko-bot
2026-08-20  9:25 ` [PATCH 3/7] rust: crc_ccitt: add CRC-CCITT abstraction Ayush Singh
2026-08-20  9:33   ` sashiko-bot
2026-08-21  3:00   ` Eric Biggers
2026-08-21  5:25     ` Ayush Singh
2026-08-25 17:56       ` Eric Biggers
2026-08-25 19:20         ` Miguel Ojeda
2026-08-20  9:25 ` [PATCH 4/7] rust: kernel: Add greybus abstractions Ayush Singh
2026-08-20  9:42   ` sashiko-bot
2026-08-20  9:25 ` [PATCH 5/7] drivers: greybus: Add software SVC implementation Ayush Singh
2026-08-20  9:40   ` sashiko-bot
2026-08-20  9:25 ` [PATCH 6/7] greybus: Add Rust UART node driver Ayush Singh
2026-08-20  9:38   ` sashiko-bot
2026-08-20  9:25 ` [PATCH 7/7] dt-bindings: beagle: Add BeagleConnect Freedom Ayush Singh
2026-08-20  9:31   ` sashiko-bot
2026-08-20 18:33   ` Conor Dooley
2026-08-21  5:31     ` Ayush Singh
2026-08-21 17:20       ` Conor Dooley [this message]
2026-08-21  6:20   ` Krzysztof Kozlowski

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=20260821-zesty-penalty-a9a485150545@spud \
    --to=conor@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=ardb@kernel.org \
    --cc=ayush@beagleboard.com \
    --cc=ayush@beagleboard.org \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=elder@kernel.org \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=jkridner@beagleboard.org \
    --cc=johan@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=robertcnelson@gmail.com \
    --cc=robh@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=work@onurozkan.dev \
    /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