From: Jonathan Cameron <jic23@kernel.org>
To: <victor.duicu@microchip.com>
Cc: <matteomartelli3@gmail.com>, <lars@metafoo.de>,
<marius.cristea@microchip.com>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7] iio: adc: pac1921: Add ACPI support to Microchip pac1921
Date: Sun, 3 Nov 2024 11:01:27 +0000 [thread overview]
Message-ID: <20241103110127.6453b537@jic23-huawei> (raw)
In-Reply-To: <20241102154509.4b2495fa@jic23-huawei>
On Sat, 2 Nov 2024 15:45:09 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> On Thu, 31 Oct 2024 08:52:05 +0200
> <victor.duicu@microchip.com> wrote:
>
> > From: Victor Duicu <victor.duicu@microchip.com>
> >
> > This patch implements ACPI support to Microchip pac1921.
> > The driver can read shunt resistor value and label from ACPI table.
> >
> > Signed-off-by: Victor Duicu <victor.duicu@microchip.com>
> Hi Victor.
>
> I made a few minor tweaks whilst applying (see inline)
>
> Applied to the togreg branch of iio.git and pushed out as testing for now
> so that the bots can take a look and see if we missed anything.
Backed out again so you can resolve Andy's comments.
Jonathan
>
> Jonathan
>
> > +/*
> > + * documentation related to the ACPI device definition
> > + * https://ww1.microchip.com/downloads/aemDocuments/documents/OTH/ApplicationNotes/ApplicationNotes/PAC193X-Integration-Notes-for-Microsoft-Windows-10-and-Windows-11-Driver-Support-DS00002534.pdf
> > + */
> > +static int pac1921_match_acpi_device(struct iio_dev *indio_dev)
> > +{
> > + acpi_handle handle;
> > + union acpi_object *rez;
> > + guid_t guid;
> > + char *label;
> > + struct pac1921_priv *priv = iio_priv(indio_dev);
> > + struct device *dev = &priv->client->dev;
> > +
> > + guid_parse(PAC1921_DSM_UUID, &guid);
> > + handle = ACPI_HANDLE(dev);
> > +
> > + rez = acpi_evaluate_dsm(handle, &guid, 1, PAC1921_ACPI_GET_UOHMS_VALS, NULL);
> > + if (!rez)
> > + return dev_err_probe(dev, -EINVAL,
> > + "Could not read shunt from ACPI table\n");
> > +
> > + priv->rshunt_uohm = rez->package.elements[0].integer.value;
> > + ACPI_FREE(rez);
> > +
> > + rez = acpi_evaluate_dsm(handle, &guid, 1, PAC1921_ACPI_GET_LABEL, NULL);
> > + if (!rez)
> > + return dev_err_probe(dev, -EINVAL,
> > + "Could not read label from ACPI table\n");
> > +
> > + label = devm_kstrdup(dev, rez->package.elements->string.pointer, GFP_KERNEL);
> > + if (!label)
> > + return dev_err_probe(dev, -EINVAL, "Label is NULL\n");
> ENOMEM appropriate I think.
>
> Also, a package is an array of elements, and this is the first one so
> maybe res->package.elements[0].string.pointer is more appropriate?
> (similar to above).
>
>
> > +
> > + indio_dev->label = label;
> > + ACPI_FREE(rez);
> > +
> > + return 0;
> > +}
>
>
next prev parent reply other threads:[~2024-11-03 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 6:52 [PATCH v7] iio: adc: pac1921: Add ACPI support to Microchip pac1921 victor.duicu
2024-11-02 15:45 ` Jonathan Cameron
2024-11-03 11:01 ` Jonathan Cameron [this message]
2024-11-02 19:48 ` Andy Shevchenko
2024-11-03 11:10 ` Jonathan Cameron
2024-11-05 8:31 ` Victor.Duicu
2024-11-02 20:01 ` 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=20241103110127.6453b537@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.cristea@microchip.com \
--cc=matteomartelli3@gmail.com \
--cc=victor.duicu@microchip.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