devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Danny Kaehn <danny.kaehn@plexus.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	Jiri Kosina <jikos@kernel.org>,
	devicetree@vger.kernel.org, linux-input@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Ethan Twardy <ethan.twardy@plexus.com>
Subject: Re: [PATCH v11 3/4] HID: cp2112: Fwnode Support
Date: Thu, 6 Jun 2024 02:39:27 +0300	[thread overview]
Message-ID: <ZmD3L0YGm977BBmV@smile.fi.intel.com> (raw)
In-Reply-To: <20240605-cp2112-dt-v11-3-d55f0f945a62@plexus.com>

On Wed, Jun 05, 2024 at 06:12:46PM -0500, Danny Kaehn wrote:
> Support describing the CP2112's I2C and GPIO interfaces in firmware.
> 
> The GPIO chip shares a firmware node with the CP2112. The I2C child
> node can either be a child with the name "i2c" or, in ACPI, a device
> node with _ADR Zero.

...

> +	device_for_each_child_node(&hdev->dev, child) {
> +		ret = acpi_get_local_address(ACPI_HANDLE_FWNODE(child), &addr);
> +		if (ret) {
> +			name = fwnode_get_name(child);
> +			if (!name)
> +				continue;
> +			ret = match_string(cp2112_cell_names,
> +					ARRAY_SIZE(cp2112_cell_names), name);
> +			if (ret < 0)
> +				continue;
> +			addr = ret;
> +		}
> +
> +		switch (addr) {
> +		case CP2112_I2C_ADR:
> +			device_set_node(&dev->adap.dev, child);
> +			break;

		default:
			break;

?

> +		}
> +	}

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-06-05 23:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 23:12 [PATCH v11 0/4] Firmware Support for USB-HID Devices and CP2112 Danny Kaehn
2024-06-05 23:12 ` [PATCH v11 1/4] dt-bindings: i2c: Add CP2112 HID USB to SMBus Bridge Danny Kaehn
2024-06-06  0:18   ` Rob Herring (Arm)
2024-06-06  6:28   ` Krzysztof Kozlowski
2024-06-06 15:12     ` Danny Kaehn
2024-06-06 15:18   ` Rob Herring
2024-06-06 16:24     ` Danny Kaehn
2024-06-06 19:49       ` Andy Shevchenko
2024-06-07 18:38         ` Danny Kaehn
2024-06-05 23:12 ` [PATCH v11 2/4] HID: usbhid: Share USB device firmware node with child HID device Danny Kaehn
2024-06-05 23:43   ` Andy Shevchenko
2024-06-06  7:31     ` Benjamin Tissoires
2024-06-05 23:12 ` [PATCH v11 3/4] HID: cp2112: Fwnode Support Danny Kaehn
2024-06-05 23:39   ` Andy Shevchenko [this message]
2024-06-05 23:12 ` [PATCH v11 4/4] HID: cp2112: Configure I2C Bus Speed from Firmware Danny Kaehn
2024-06-05 23:42 ` [PATCH v11 0/4] Firmware Support for USB-HID Devices and CP2112 Andy Shevchenko
2024-06-06 15:54   ` Danny Kaehn
2024-06-06 19:47     ` Andy Shevchenko
2024-06-07 17:20       ` Danny Kaehn
2024-06-06  7:30 ` (subset) " Benjamin Tissoires
2025-07-29 14:53 ` Re " Willie Thai
2025-07-29 17:49   ` Danny Kaehn
2025-08-05 21:32     ` Andy Shevchenko
2025-08-06 11:07     ` Willie Thai

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=ZmD3L0YGm977BBmV@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=bentiss@kernel.org \
    --cc=danny.kaehn@plexus.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=ethan.twardy@plexus.com \
    --cc=jikos@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).