devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ayush Singh <ayushdevel1325@gmail.com>
Cc: greybus-dev@lists.linaro.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, vaishnav@beagleboard.org,
	jkridner@beagleboard.org, nm@ti.com,
	krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v9 0/3] greybus: Add BeaglePlay Greybus Driver
Date: Fri, 27 Oct 2023 13:21:32 +0200	[thread overview]
Message-ID: <2023102701-safely-limping-0c26@gregkh> (raw)
In-Reply-To: <20231017101116.178041-1-ayushdevel1325@gmail.com>

On Tue, Oct 17, 2023 at 03:41:11PM +0530, Ayush Singh wrote:
> BeagleConnect is both a technology concept and a line of board designs
> that implement the technology. Born from Greybus, a mechanism for
> dynamically extending a Linux system with embedded peripherals,
> BeagleConnect adds two key elements: a 6LoWPAN transport and mikroBUS
> manifests. The 6LoWPAN transport provides for arbitrary connections,
> including the IEEE802.15.4g long-range wireless transport supported
> between BeaglePlay and BeagleConnect Freedom (the first BeagleConnect
> board design). The mikroBUS manifests provide for rapid prototyping
> and low-node-count production with sensor boards following the
> mikroBUS freely-licensable embedded bus standard such that existing
> Linux drivers can be loaded upon Greybus discovery of the nodes.
> This patch set provides the Linux-side hooks required for the 6LoWPAN
> transport for BeagleConnect on BeaglePlay. Also adds required devicetree
> additions.
> 
> Tested over `next-20230825`.
> 
> Link: https://programmershideaway.xyz/tags/gsoc23/ GSoC23 Blog
> Link: https://git.beagleboard.org/gsoc/greybus/cc1352-firmware Zephyr App
> Link: https://github.com/Ayush1325/linux/tree/gb-beagleplay GitHub Branch
> Link: https://docs.beagleboard.org/latest/boards/beagleconnect/index.html BeagleConnect
> Link: https://docs.beagleboard.org/latest/boards/beagleplay/index.html BeaglePlay
> Link: https://github.com/Ayush1325/linux/tree/gb-beagleplay Github Repo
> Link: https://lists.linaro.org/archives/list/greybus-dev@lists.linaro.org/thread/5RQV7OG5KI4BQWRN5ZCGZIFRMM6ERKPP/ Patch v8
> 
> Changes in Patch v9
> v8 -> v9:
> - Some capitalization in dt-bindings
> - add reset-gpios and vdds-supply to beagleplay device tree

Given a lack of objections, and nothing I could find wrong with this,
I've now applied this to my tree, thanks for sticking with this.

Now the real work begins!  :)

thanks,

greg k-h

      parent reply	other threads:[~2023-10-27 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 10:11 [PATCH v9 0/3] greybus: Add BeaglePlay Greybus Driver Ayush Singh
2023-10-17 10:11 ` [PATCH v9 1/3] dt-bindings: net: Add ti,cc1352p7 Ayush Singh
2023-10-26 14:00   ` kernel test robot
2023-10-17 10:11 ` [PATCH v9 2/3] greybus: Add BeaglePlay Linux Driver Ayush Singh
2023-10-17 10:11 ` [PATCH v9 3/3] dts: ti: k3-am625-beagleplay: Add beaglecc1352 Ayush Singh
2023-10-27 11:21 ` Greg KH [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=2023102701-safely-limping-0c26@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ayushdevel1325@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=jkridner@beagleboard.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=vaishnav@beagleboard.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 NNTP newsgroup(s).