public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [PATCH 0/4] Remove struct device_connection
Date: Fri,  4 Sep 2020 15:51:19 +0300	[thread overview]
Message-ID: <20200904125123.83725-1-heikki.krogerus@linux.intel.com> (raw)

Hi,

The purpose of the struct device_connection was to allow
connections between devices to be described somehow when the
firmware did not do that. Later support for also firmware
described connections, for example walking device graph, was
added to the API. But now software nodes make it possible to
describe for example device graph if needed, so we don't
need a separate method of describing the connections.

All the users of struct device_connection have now been
concerted to use software nodes instead, so we can remove
the data structure, and the list for it.

thanks,

Heikki Krogerus (4):
  device connection: Remove device_connection_find()
  device connection: Remove device_connection_add()
  device connection: Remove struct device_connection
  device property: Move fwnode_connection_find_match() under
    drivers/base/property.c

 .../driver-api/device_connection.rst          |  43 ----
 drivers/base/Makefile                         |   2 +-
 drivers/base/devcon.c                         | 231 ------------------
 drivers/base/property.c                       |  73 ++++++
 drivers/usb/roles/class.c                     |  12 +-
 drivers/usb/typec/mux.c                       |  19 +-
 include/linux/device.h                        |  56 -----
 include/linux/property.h                      |  14 ++
 8 files changed, 102 insertions(+), 348 deletions(-)
 delete mode 100644 Documentation/driver-api/device_connection.rst
 delete mode 100644 drivers/base/devcon.c

-- 
2.28.0


             reply	other threads:[~2020-09-04 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 12:51 Heikki Krogerus [this message]
2020-09-04 12:51 ` [PATCH 1/4] device connection: Remove device_connection_find() Heikki Krogerus
2020-09-04 12:51 ` [PATCH 2/4] device connection: Remove device_connection_add() Heikki Krogerus
2020-09-04 12:51 ` [PATCH 3/4] device connection: Remove struct device_connection Heikki Krogerus
2020-09-04 12:51 ` [PATCH 4/4] device property: Move fwnode_connection_find_match() under drivers/base/property.c Heikki Krogerus
2020-09-07  9:04   ` Greg Kroah-Hartman
2020-09-07  9:13     ` 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=20200904125123.83725-1-heikki.krogerus@linux.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.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