All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Guenter Roeck <linux@roeck-us.net>,
	Hans de Goede <hdegoede@redhat.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC,1/5] driver core: Add fwnode member to struct device_connection
Date: Thu, 25 Oct 2018 10:28:05 +0300	[thread overview]
Message-ID: <20181025072805.GD2034@kuha.fi.intel.com> (raw)

On Wed, Oct 24, 2018 at 08:33:53AM -0700, Randy Dunlap wrote:
> On 10/24/18 8:05 AM, Heikki Krogerus wrote:
> > This will prepare the device connection API for connections
> > described in firmware.
> > 
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > ---
> >  include/linux/device.h | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/include/linux/device.h b/include/linux/device.h
> > index 90224e75ade4..a964a0d614fa 100644
> > --- a/include/linux/device.h
> > +++ b/include/linux/device.h
> > @@ -753,11 +753,17 @@ struct device_dma_parameters {
> >  
> >  /**
> >   * struct device_connection - Device Connection Descriptor
> > + * @fwnode: The device node of the connected device
> >   * @endpoint: The names of the two devices connected together
> >   * @id: Unique identifier for the connection
> >   * @list: List head, private, for internal use only
> > + *
> > + * NOTE: @fwnode is not used together with @endpoint. @fwnode is used when
> > + * platform firmware defines the connection. When the connection is registeded
> 
> for your next version:)                                                registered

OK.

thanks,

WARNING: multiple messages have this Message-ID (diff)
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Guenter Roeck <linux@roeck-us.net>,
	Hans de Goede <hdegoede@redhat.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] driver core: Add fwnode member to struct device_connection
Date: Thu, 25 Oct 2018 10:28:05 +0300	[thread overview]
Message-ID: <20181025072805.GD2034@kuha.fi.intel.com> (raw)
In-Reply-To: <a00ff7d0-4cac-2454-7c12-7844aecb68f1@infradead.org>

On Wed, Oct 24, 2018 at 08:33:53AM -0700, Randy Dunlap wrote:
> On 10/24/18 8:05 AM, Heikki Krogerus wrote:
> > This will prepare the device connection API for connections
> > described in firmware.
> > 
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > ---
> >  include/linux/device.h | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/include/linux/device.h b/include/linux/device.h
> > index 90224e75ade4..a964a0d614fa 100644
> > --- a/include/linux/device.h
> > +++ b/include/linux/device.h
> > @@ -753,11 +753,17 @@ struct device_dma_parameters {
> >  
> >  /**
> >   * struct device_connection - Device Connection Descriptor
> > + * @fwnode: The device node of the connected device
> >   * @endpoint: The names of the two devices connected together
> >   * @id: Unique identifier for the connection
> >   * @list: List head, private, for internal use only
> > + *
> > + * NOTE: @fwnode is not used together with @endpoint. @fwnode is used when
> > + * platform firmware defines the connection. When the connection is registeded
> 
> for your next version:)                                                registered

OK.

thanks,

-- 
heikki

             reply	other threads:[~2018-10-25  7:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  7:28 Heikki Krogerus [this message]
2018-10-25  7:28 ` [RFC PATCH 1/5] driver core: Add fwnode member to struct device_connection Heikki Krogerus
  -- strict thread matches above, loose matches on Subject: below --
2019-01-22 13:23 [RFC,3/5] usb: roles: Find the muxes by also matching against the device node Heikki Krogerus
2019-01-22 13:23 ` [RFC PATCH 3/5] " Heikki Krogerus
2019-01-22  5:40 [RFC,3/5] " Jun Li
2019-01-22  5:40 ` [RFC PATCH 3/5] " Jun Li
2018-10-25  9:02 [RFC,4/5] usb: typec: Find the ports " Heikki Krogerus
2018-10-25  9:02 ` [RFC PATCH 4/5] " Heikki Krogerus
2018-10-25  7:27 [RFC,4/5] " Heikki Krogerus
2018-10-25  7:27 ` [RFC PATCH 4/5] " Heikki Krogerus
2018-10-24 17:07 [RFC,4/5] " Sergei Shtylyov
2018-10-24 17:07 ` [RFC PATCH 4/5] " Sergei Shtylyov
2018-10-24 15:33 [RFC,1/5] driver core: Add fwnode member to struct device_connection Randy Dunlap
2018-10-24 15:33 ` [RFC PATCH 1/5] " Randy Dunlap
2018-10-24 15:05 [RFC,5/5] drivers core: Find device connections also from device graphs Heikki Krogerus
2018-10-24 15:05 ` [RFC PATCH 5/5] " Heikki Krogerus
2018-10-24 15:05 [RFC,4/5] usb: typec: Find the ports by also matching against the device node Heikki Krogerus
2018-10-24 15:05 ` [RFC PATCH 4/5] " Heikki Krogerus
2018-10-24 15:05 [RFC,3/5] usb: roles: Find the muxes " Heikki Krogerus
2018-10-24 15:05 ` [RFC PATCH 3/5] " Heikki Krogerus
2018-10-24 15:05 [RFC,2/5] usb: typec: mux: " Heikki Krogerus
2018-10-24 15:05 ` [RFC PATCH 2/5] " Heikki Krogerus
2018-10-24 15:05 [RFC,1/5] driver core: Add fwnode member to struct device_connection Heikki Krogerus
2018-10-24 15:05 ` [RFC PATCH 1/5] " Heikki Krogerus
2018-10-24 15:05 [RFC PATCH 0/5] Adding graph handling to device connection API Heikki Krogerus

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=20181025072805.GD2034@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.