public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: Felipe Balbi <balbi@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Daniel Scally <djrscally@gmail.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: [PATCH v3 0/4] Remove one more platform_device_add_properties() call
Date: Fri, 15 Jan 2021 12:49:10 +0300	[thread overview]
Message-ID: <20210115094914.88401-1-heikki.krogerus@linux.intel.com> (raw)

Hi,

I'm now clearing the dev_fwnode(dev)->secondary pointer in
device_remove_software_node() as requested by Daniel and Andy. Thanks
guys, it's much better now. I also took the liberty of including one
more PCI ID patch where I add PCI ID for the Alder Lake-P variant. I
hope that is OK.

Andy, I dropped your Tested-by tag because of the change I made to the
first patch. If you have time to retest these, I would much appreciate.


v2 cover letter:

Hi Felipe, Rafael,

This is the second version of this series. There are no real changes,
but I added the Tiger Lake ID patch to this series in hope that it
will make your life a bit easier, assuming that Rafael will still pick
these.


The original over letter:

I originally introduced these as part of my series where I was
proposing PM ops for software nodes [1], but since that still needs
work, I'm sending these two separately.

So basically I'm only modifying dwc3-pci.c so it registers a software
node directly at this point. That will remove one more user of
platform_device_add_properties().

[1] https://lore.kernel.org/lkml/20201029105941.63410-1-heikki.krogerus@linux.intel.com/

thanks,

Heikki Krogerus (4):
  software node: Introduce device_add_software_node()
  usb: dwc3: pci: Register a software node for the dwc3 platform device
  usb: dwc3: pci: ID for Tiger Lake CPU
  usb: dwc3: pci: add support for the Intel Alder Lake-P

 drivers/base/swnode.c       | 71 ++++++++++++++++++++++++++++++++-----
 drivers/usb/dwc3/dwc3-pci.c | 69 ++++++++++++++++++++++-------------
 include/linux/property.h    |  3 ++
 3 files changed, 110 insertions(+), 33 deletions(-)

-- 
2.29.2


             reply	other threads:[~2021-01-15  9:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  9:49 Heikki Krogerus [this message]
2021-01-15  9:49 ` [PATCH v3 1/4] software node: Introduce device_add_software_node() Heikki Krogerus
2021-01-15  9:49 ` [PATCH v3 2/4] usb: dwc3: pci: Register a software node for the dwc3 platform device Heikki Krogerus
2021-01-15  9:49 ` [PATCH v3 3/4] usb: dwc3: pci: ID for Tiger Lake CPU Heikki Krogerus
2021-01-15  9:49 ` [PATCH v3 4/4] usb: dwc3: pci: add support for the Intel Alder Lake-P Heikki Krogerus
2021-01-15 11:14   ` Felipe Balbi
2021-01-16 20:23 ` [PATCH v3 0/4] Remove one more platform_device_add_properties() call Andy Shevchenko
2021-01-16 21:29   ` Daniel Scally
2021-01-17 21:05     ` Andy Shevchenko
2021-01-17 21:15       ` Daniel Scally

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=20210115094914.88401-1-heikki.krogerus@linux.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=balbi@kernel.org \
    --cc=djrscally@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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