linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vaishnav M A <vaishnav@beagleboard.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: greybus-dev@lists.linaro.org, linux-kernel@vger.kernel.org,
	arnd@arndb.de, johan@kernel.org, elder@kernel.org,
	robh@kernel.org, mchehab+huawei@kernel.org, davem@davemloft.net,
	"Jason Kridner" <jkridner@beagleboard.org>,
	"Drew Fustini" <drew@beagleboard.org>,
	"Robert Nelson" <robertcnelson@beagleboard.org>,
	"Ivan Rajković" <rajkovic@mikroe.com>,
	chrisfriedt@gmail.com, zoran.stojsavljevic@gmail.com
Subject: Re: [RFC PATCH v2 0/3] mikroBUS driver for add-on boards
Date: Wed, 19 Aug 2020 03:22:48 +0530	[thread overview]
Message-ID: <CALudOK4jgtJiB8sn4CsDm2c=va=d8M7ocoa55f=NV9sTaBHJJg@mail.gmail.com> (raw)
In-Reply-To: <20200818152426.GA713928@kroah.com>

On Tue, Aug 18, 2020 at 8:54 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Aug 18, 2020 at 06:18:12PM +0530, Vaishnav M A wrote:
> > Hi,
> >
> > This Patch series is an update to the mikroBUS driver
> > RFC v1 Patch : https://lkml.org/lkml/2020/7/24/518 .
>
> Please use lore.kernel.org for links, we have no idea if lkml.org will
> be working tomorrow or not :)
>
Hi Greg,

Thanks, will use lore.kernel.org for the links, attaching the corresponding
link to the v1 RFC patch thread for reference:
https://lore.kernel.org/lkml/20200724120637.GA427284@vaishnav-VirtualBox/

> > The mikrobus driver is updated to add mikrobus ports from device-tree
> > overlays, the debug interfaces for adding mikrobus ports through sysFS
> > is removed, and the driver considers the extended usage of mikrobus
> > port pins from their standard purposes.
>
> I don't know what "properties" and "device" mean with regards to things
> here, any chance you can provide a patch to the greybus spec itself that
> adds this information so we can better understand the reasoning here to
> see if the kernel changes match up with the goals?
>
> thanks,
>
> greg k-h
Sure, I will add a patch to the greybus-spec to describe the new descriptors,
the property and device descriptors are introduced to add information
about the SPI/I2C/UART chip/sensor which is required by the corresponding
device drivers, With these descriptors, it will be possible to describe devices
on I2C, SPI, UART, etc. behind a greybus device so as to bind existing kernel
drivers to them, This is not what is currently being done within the mikroBUS
driver, now it tries to instantiate devices on actual I2C, SPI, UART from
describing manifests, but the ultimate goal is to describe the devices on
I2C/SPI/UART behind a greybus device, thus enabling to attach existing
kernel drivers to devices present in add-on boards attached to mikroBUS
ports added via greybus.

Shall I submit a pull request to https://github.com/projectara/greybus-spec
for the specs, is there a different official upstream to greybus-spec?

Thanks and Regards,
Vaishnav M A

  reply	other threads:[~2020-08-18 21:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 12:48 [RFC PATCH v2 0/3] mikroBUS driver for add-on boards Vaishnav M A
2020-08-18 12:48 ` [RFC PATCH v2 1/3] add mikrobus descriptors to greybus_manifest Vaishnav M A
2020-08-20  0:49   ` Vaishnav M A
2020-08-31  6:26     ` Zoran Stojsavljevic
2020-09-01  8:33       ` Vaishnav M A
2020-08-18 12:48 ` [RFC PATCH v2 2/3] mikroBUS driver for add-on boards on mikrobus ports Vaishnav M A
2020-08-18 12:48 ` [RFC PATCH v2 3/3] Add Device Tree Bindings for mikroBUS port Vaishnav M A
2020-08-18 13:35   ` [greybus-dev] " Laurent Pinchart
2020-08-18 21:22     ` Vaishnav M A
2020-08-27 15:45   ` Rob Herring
2020-08-18 15:24 ` [RFC PATCH v2 0/3] mikroBUS driver for add-on boards Greg KH
2020-08-18 21:52   ` Vaishnav M A [this message]
2020-08-19  5:54     ` Greg KH
2020-08-18 20:38 ` Frank Rowand
2020-08-18 21:56   ` Vaishnav M A
2020-08-25  1:44   ` Frank Rowand

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='CALudOK4jgtJiB8sn4CsDm2c=va=d8M7ocoa55f=NV9sTaBHJJg@mail.gmail.com' \
    --to=vaishnav@beagleboard.org \
    --cc=arnd@arndb.de \
    --cc=chrisfriedt@gmail.com \
    --cc=davem@davemloft.net \
    --cc=drew@beagleboard.org \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=jkridner@beagleboard.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=rajkovic@mikroe.com \
    --cc=robertcnelson@beagleboard.org \
    --cc=robh@kernel.org \
    --cc=zoran.stojsavljevic@gmail.com \
    /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).