From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans de Goede <hdegoede@redhat.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH 08/11] platform/x86: intel_cht_int33fe: Provide software nodes for the devices
Date: Tue, 9 Apr 2019 15:41:13 +0300 [thread overview]
Message-ID: <20190409124113.GB20058@kuha.fi.intel.com> (raw)
In-Reply-To: <CAHp75VfQK_YHyfryMUO0uG_uwoKcgMn_NUXaRbiOXeXQz6xyYQ@mail.gmail.com>
On Mon, Apr 08, 2019 at 07:09:15PM +0300, Andy Shevchenko wrote:
> On Wed, Apr 3, 2019 at 7:46 PM Heikki Krogerus
> <heikki.krogerus@linux.intel.com> wrote:
> >
> > Software nodes provide two features that we will need later.
> > 1) Software nodes can have references to other software nodes.
> > 2) Software nodes can exist before a device entry is created.
>
> > #include <linux/platform_device.h>
> > #include <linux/regulator/consumer.h>
> > #include <linux/slab.h>
> > +#include <linux/pci.h>
>
> I understand your attitude to ordering here, but we already have it
> ordered, why not to keep it that way?
Sure. I'll keep the order.
> > -static struct i2c_client *cht_int33fe_find_max17047(void)
> > -{
> > - struct i2c_client *max17047 = NULL;
> > -
> > - i2c_for_each_dev(&max17047, cht_int33fe_check_for_max17047);
> > - return max17047;
> > -}
>
> This sounds like a cleanup patch before actual change.
> And I'm not sure, do we need to remove this function?
>
> > +static int
> > +cht_int33fe_max17047(struct device *dev, struct cht_int33fe_data *data)
> > +{
> > + struct fwnode_handle *fwnode = data->node[INT33FE_NODE_MAX17047];
> > + struct i2c_client *max17047 = NULL;
> > + struct i2c_board_info board_info;
> > + int ret;
> > +
> > + i2c_for_each_dev(&max17047, cht_int33fe_check_for_max17047);
> > + if (max17047) {
> > + /* Pre-existing i2c-client for the max17047, add device-props */
> > + max17047->dev.fwnode->secondary = fwnode;
> > + /* And re-probe to get the new device-props applied. */
> > + ret = device_reprobe(&max17047->dev);
> > + if (ret)
> > + dev_warn(dev, "Reprobing max17047 error: %d\n", ret);
> > + return 0;
> > + }
> > +
> > + memset(&board_info, 0, sizeof(board_info));
> > + strlcpy(board_info.type, "max17047", I2C_NAME_SIZE);
> > + board_info.dev_name = "max17047";
> > + board_info.fwnode = fwnode;
> > + data->max17047 = i2c_acpi_new_device(dev, 1, &board_info);
> > + if (IS_ERR(data->max17047))
> > + return PTR_ERR(data->max17047);
> > +
> > + return 0;
> > +}
>
> This looks like a split from the original code with some changes.
> Perhaps, split patch first.
>
> > /* Work around BIOS bug, see comment on cht_int33fe_find_max17047 */
>
> After this patch, the comment here become outdated, care to fix?
>
> > + ret = cht_int33fe_max17047(dev, data);
>
> Seems like the verb is missed in the name of the function.
Yeah, I never meant to rename the function. I'll just keep the
function name as cht_int33fe_find_max17047.
thanks,
--
heikki
next prev parent reply other threads:[~2019-04-09 12:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 16:45 [PATCH 00/11] Software fwnode references Heikki Krogerus
2019-04-03 16:45 ` [PATCH 01/11] software node: Allow node creation without properties Heikki Krogerus
2019-04-03 16:45 ` [PATCH 02/11] software node: Simplify software_node_release() function Heikki Krogerus
2019-04-03 16:45 ` [PATCH 03/11] software node: Add support for references Heikki Krogerus
2019-04-03 16:45 ` [PATCH 04/11] software node: Implement .get_reference_args fwnode operation Heikki Krogerus
2019-04-03 16:45 ` [PATCH 05/11] ACPI / property: Don't limit named child node matching to data nodes Heikki Krogerus
2019-04-03 16:45 ` [PATCH 06/11] device connection: Find connections also by checking the references Heikki Krogerus
2019-04-03 16:45 ` [PATCH 07/11] usb: typec: Registering real device entries for the muxes Heikki Krogerus
2019-04-03 16:45 ` [PATCH 08/11] platform/x86: intel_cht_int33fe: Provide software nodes for the devices Heikki Krogerus
2019-04-08 16:09 ` Andy Shevchenko
2019-04-08 16:09 ` Andy Shevchenko
2019-04-09 12:41 ` Heikki Krogerus [this message]
2019-04-09 12:41 ` Heikki Krogerus
2019-04-03 16:45 ` [PATCH 09/11] platform/x86: intel_cht_int33fe: Provide fwnode for the USB connector Heikki Krogerus
2019-04-08 16:10 ` Andy Shevchenko
2019-04-08 16:10 ` Andy Shevchenko
2019-04-03 16:45 ` [PATCH 10/11] platform/x86: intel_cht_int33fe: Link with external dependencies using fwnodes Heikki Krogerus
2019-04-08 16:42 ` Andy Shevchenko
2019-04-08 16:42 ` Andy Shevchenko
2019-04-09 12:38 ` Heikki Krogerus
2019-04-09 12:38 ` Heikki Krogerus
2019-04-03 16:45 ` [PATCH 11/11] platform/x86: intel_cht_int33fe: Replacing the old connections with references Heikki Krogerus
2019-04-08 16:45 ` Andy Shevchenko
2019-04-08 16:45 ` Andy Shevchenko
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=20190409124113.GB20058@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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