From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, Wayne Chang <waynec@nvidia.com>
Subject: Re: [PATCH V6 4/6] i2c: nvidia-gpu: Remove ccgx,firmware-build property
Date: Fri, 20 Jan 2023 11:37:49 +0200 [thread overview]
Message-ID: <Y8pg7ZN1sbOBJbaf@kuha.fi.intel.com> (raw)
In-Reply-To: <20230119121639.226729-5-jonathanh@nvidia.com>
On Thu, Jan 19, 2023 at 12:16:37PM +0000, Jon Hunter wrote:
> From: Wayne Chang <waynec@nvidia.com>
>
> Now the Cypress CCG driver has been updated to support the
> 'firmware-name' property to align with device-tree, remove the
> 'ccgx,firmware-build' property as this is no longer needed.
>
> Signed-off-by: Wayne Chang <waynec@nvidia.com>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> V6: no changes
> V5: Added this patch from V3
>
> drivers/i2c/busses/i2c-nvidia-gpu.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-nvidia-gpu.c b/drivers/i2c/busses/i2c-nvidia-gpu.c
> index 6d81ea530a83..a8b99e7f6262 100644
> --- a/drivers/i2c/busses/i2c-nvidia-gpu.c
> +++ b/drivers/i2c/busses/i2c-nvidia-gpu.c
> @@ -259,8 +259,7 @@ static const struct pci_device_id gpu_i2c_ids[] = {
> MODULE_DEVICE_TABLE(pci, gpu_i2c_ids);
>
> static const struct property_entry ccgx_props[] = {
> - /* Use FW built for NVIDIA (nv) only */
> - PROPERTY_ENTRY_U16("ccgx,firmware-build", ('n' << 8) | 'v'),
> + /* Use FW built for NVIDIA GPU only */
> PROPERTY_ENTRY_STRING("firmware-name", "nvidia,gpu"),
> { }
> };
This patch is fine, and it's in the right place, but you need to
squash 5/6 into 3/6.
thanks,
--
heikki
next prev parent reply other threads:[~2023-01-20 9:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 12:16 [PATCH V6 0/6] Add device-tree support for Cypress CYPD4226 Jon Hunter
2023-01-19 12:16 ` [PATCH V6 1/6] dt-bindings: usb: Add Cypress cypd4226 Type-C controller Jon Hunter
2023-01-20 8:32 ` Krzysztof Kozlowski
2023-01-23 14:28 ` Jon Hunter
2023-01-23 15:04 ` Jon Hunter
2023-01-23 15:54 ` Krzysztof Kozlowski
2023-01-23 22:16 ` Jon Hunter
2023-01-24 7:27 ` Krzysztof Kozlowski
2023-01-19 12:16 ` [PATCH V6 2/6] i2c: nvidia-gpu: Add ACPI property to align with device-tree Jon Hunter
2023-01-20 9:18 ` Heikki Krogerus
2023-01-19 12:16 ` [PATCH V6 3/6] usb: typec: ucsi_ccg: Add OF support Jon Hunter
2023-01-20 9:33 ` Heikki Krogerus
2023-01-20 13:18 ` Jon Hunter
2023-01-19 12:16 ` [PATCH V6 4/6] i2c: nvidia-gpu: Remove ccgx,firmware-build property Jon Hunter
2023-01-20 9:37 ` Heikki Krogerus [this message]
2023-01-19 12:16 ` [PATCH V6 5/6] usb: typec: ucsi_ccg: " Jon Hunter
2023-01-20 9:34 ` Heikki Krogerus
2023-01-20 13:20 ` Jon Hunter
2023-01-19 12:16 ` [PATCH V6 6/6] arm64: tegra: Populate USB Type-C Controller for Jetson AGX Orin Jon Hunter
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=Y8pg7ZN1sbOBJbaf@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=waynec@nvidia.com \
/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).