From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Danny Kaehn <kaehndan@gmail.com>,
krzysztof.kozlowski+dt@linaro.org, jikos@kernel.org,
benjamin.tissoires@redhat.com, devicetree@vger.kernel.org,
linux-input@vger.kernel.org, ethan.twardy@plexus.com
Subject: Re: [PATCH v3 4/4] HID: cp2112: Devicetree Support
Date: Thu, 9 Feb 2023 22:01:25 +0100 [thread overview]
Message-ID: <CACMJSeuP9sVcadnD+yL5LGOcxGkJnyn7DKQB2=GUcZW2FUdC0A@mail.gmail.com> (raw)
In-Reply-To: <20230206163912.GA182582-robh@kernel.org>
On Mon, 6 Feb 2023 at 17:39, Rob Herring <robh@kernel.org> wrote:
>
> +Bartosz
>
> On Sun, Feb 05, 2023 at 08:54:50AM -0600, Danny Kaehn wrote:
> > Bind i2c and gpio interfaces to subnodes with names
> > "i2c" and "gpio" if they exist, respectively. This
> > allows the gpio and i2c controllers to be described
> > in DT as usual. Additionally, support configuring the
> > i2c bus speed from the clock-frequency property.
> >
> > Signed-off-by: Danny Kaehn <kaehndan@gmail.com>
> > ---
> > drivers/hid/hid-cp2112.c | 22 ++++++++++++++++++++--
> > 1 file changed, 20 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/hid/hid-cp2112.c b/drivers/hid/hid-cp2112.c
> > index 27cadadda7c9..aa634accdfb0 100644
> > --- a/drivers/hid/hid-cp2112.c
> > +++ b/drivers/hid/hid-cp2112.c
> > @@ -1234,6 +1234,7 @@ static int cp2112_probe(struct hid_device *hdev, const struct hid_device_id *id)
> > u8 buf[3];
> > struct cp2112_smbus_config_report config;
> > struct gpio_irq_chip *girq;
> > + struct i2c_timings timings;
> > int ret;
> >
> > dev = devm_kzalloc(&hdev->dev, sizeof(*dev), GFP_KERNEL);
> > @@ -1292,6 +1293,10 @@ static int cp2112_probe(struct hid_device *hdev, const struct hid_device_id *id)
> > goto err_power_normal;
> > }
> >
> > + dev->adap.dev.of_node = of_get_child_by_name(hdev->dev.of_node, "i2c");
> > + i2c_parse_fw_timings(&dev->adap.dev, &timings, true);
> > +
> > + config.clock_speed = cpu_to_be32(timings.bus_freq_hz);
> > config.retry_time = cpu_to_be16(1);
> >
> > ret = cp2112_hid_output(hdev, (u8 *)&config, sizeof(config),
> > @@ -1300,7 +1305,7 @@ static int cp2112_probe(struct hid_device *hdev, const struct hid_device_id *id)
> > hid_err(hdev, "error setting SMBus config\n");
> > if (ret >= 0)
> > ret = -EIO;
> > - goto err_power_normal;
> > + goto err_free_i2c_of;
> > }
> >
> > hid_set_drvdata(hdev, (void *)dev);
> > @@ -1322,7 +1327,7 @@ static int cp2112_probe(struct hid_device *hdev, const struct hid_device_id *id)
> >
> > if (ret) {
> > hid_err(hdev, "error registering i2c adapter\n");
> > - goto err_power_normal;
> > + goto err_free_i2c_of;
> > }
> >
> > hid_dbg(hdev, "adapter registered\n");
> > @@ -1336,6 +1341,9 @@ static int cp2112_probe(struct hid_device *hdev, const struct hid_device_id *id)
> > dev->gc.ngpio = 8;
> > dev->gc.can_sleep = 1;
> > dev->gc.parent = &hdev->dev;
> > +#if IS_ENABLED(CONFIG_OF_GPIO)
> > + dev->gc.of_node = of_get_child_by_name(hdev->dev.of_node, "gpio");
> > +#endif
>
> The scarcity of CONFIG_OF_GPIO ifdefs in the tree tells me this is
> wrong. I think you want to use the fwnode pointer instead. GPIO
> maintainers should review this.
>
> Rob
Yep, we're moving away from OF in favor of fwnode - so you'd need to
use device_get_named_child_node() and assign gc.fwnode.
Bart
prev parent reply other threads:[~2023-02-09 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 14:54 [PATCH v3 0/4] DeviceTree Support for USB-HID Devices and CP2112 Danny Kaehn
2023-02-05 14:54 ` [PATCH v3 1/4] dt-bindings: input: Add CP2112 HID USB to SMBus Bridge Danny Kaehn
2023-02-06 7:59 ` Krzysztof Kozlowski
2023-02-06 13:15 ` Daniel Kaehn
2023-02-06 13:37 ` Krzysztof Kozlowski
2023-02-06 16:51 ` Rob Herring
2023-02-05 14:54 ` [PATCH v3 2/4] HID: usbhid: Share USB device devicetree node with child HID device Danny Kaehn
2023-02-05 14:54 ` [PATCH v3 3/4] HID: cp2112: Fix driver not registering GPIO IRQ chip as threaded Danny Kaehn
2023-02-05 14:54 ` [PATCH v3 4/4] HID: cp2112: Devicetree Support Danny Kaehn
2023-02-06 16:39 ` Rob Herring
2023-02-09 21:01 ` Bartosz Golaszewski [this message]
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='CACMJSeuP9sVcadnD+yL5LGOcxGkJnyn7DKQB2=GUcZW2FUdC0A@mail.gmail.com' \
--to=bartosz.golaszewski@linaro.org \
--cc=benjamin.tissoires@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=ethan.twardy@plexus.com \
--cc=jikos@kernel.org \
--cc=kaehndan@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.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).