From: Jon Hunter <jonathanh@nvidia.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.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 3/6] usb: typec: ucsi_ccg: Add OF support
Date: Fri, 20 Jan 2023 13:18:20 +0000 [thread overview]
Message-ID: <794c2cb5-e5da-5c49-5465-9b9c8049ceb7@nvidia.com> (raw)
In-Reply-To: <Y8pf0Vo+HzTZ7+H7@kuha.fi.intel.com>
On 20/01/2023 09:33, Heikki Krogerus wrote:
> On Thu, Jan 19, 2023 at 12:16:36PM +0000, Jon Hunter wrote:
>> From: Wayne Chang <waynec@nvidia.com>
>>
>> Add device-tree support for the Cypress CCG UCSI driver. The device-tree
>> binding for the Cypress CCG device uses the standard device-tree
>> 'firmware-name' string property to indicate the firmware build that is
>> used. For ACPI a 16-bit property named 'ccgx,firmware-build' is used and
>> if this is not found fall back to the 'firmware-name' property.
>>
>> Signed-off-by: Wayne Chang <waynec@nvidia.com>
>> Co-developed-by: Jon Hunter <jonathanh@nvidia.com>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>> V5 -> V6: fixed compilation
>> V4 -> V5: add support for 'firmware-name'
>> V1 -> V4: nothing has changed
>>
>> drivers/usb/typec/ucsi/ucsi_ccg.c | 23 +++++++++++++++++++++--
>> 1 file changed, 21 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/usb/typec/ucsi/ucsi_ccg.c b/drivers/usb/typec/ucsi/ucsi_ccg.c
>> index 46441f1477f2..661a3988b39d 100644
>> --- a/drivers/usb/typec/ucsi/ucsi_ccg.c
>> +++ b/drivers/usb/typec/ucsi/ucsi_ccg.c
>> @@ -643,7 +643,7 @@ static int ccg_request_irq(struct ucsi_ccg *uc)
>> {
>> unsigned long flags = IRQF_ONESHOT;
>>
>> - if (!has_acpi_companion(uc->dev))
>> + if (!dev_fwnode(uc->dev))
>> flags |= IRQF_TRIGGER_HIGH;
>>
>> return request_threaded_irq(uc->irq, NULL, ccg_irq_handler, flags, dev_name(uc->dev), uc);
>> @@ -1342,6 +1342,7 @@ static int ucsi_ccg_probe(struct i2c_client *client)
>> {
>> struct device *dev = &client->dev;
>> struct ucsi_ccg *uc;
>> + const char *fw_name;
>> int status;
>>
>> uc = devm_kzalloc(dev, sizeof(*uc), GFP_KERNEL);
>> @@ -1359,7 +1360,18 @@ static int ucsi_ccg_probe(struct i2c_client *client)
>> /* Only fail FW flashing when FW build information is not provided */
>> status = device_property_read_u16(dev, "ccgx,firmware-build",
>> &uc->fw_build);
>
> You don't need this anymore. You already added the new property
> "firmware-name" to drivers/i2c/busses/i2c-nvidia-gpu.c.
I was planning to get rid of this here, but I was not sure if AMD need
this. I see now that Sanket has confirmed they don't use this and so
will drop it from here.
Jon
--
nvpublic
next prev parent reply other threads:[~2023-01-20 13:25 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 [this message]
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
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=794c2cb5-e5da-5c49-5465-9b9c8049ceb7@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.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).