From: Jonathan Cameron <jic23@kernel.org>
To: <Marius.Cristea@microchip.com>
Cc: <devicetree@vger.kernel.org>, <lars@metafoo.de>,
<linux-iio@vger.kernel.org>, <robh+dt@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] adding support for Microchip PAC193X Power Monitor
Date: Sun, 12 Mar 2023 16:45:33 +0000 [thread overview]
Message-ID: <20230312164533.491a7402@jic23-huawei> (raw)
In-Reply-To: <178ee962c5fc7ee7806475cb38527b8bdbfa8d09.camel@microchip.com>
On Mon, 6 Mar 2023 14:03:52 +0000
<Marius.Cristea@microchip.com> wrote:
> Hi Jonathan,
>
> Please, see my comments below...
>
>
> On Sat, 2023-02-25 at 17:11 +0000, Jonathan Cameron wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you
> > know the content is safe
> >
> > On Mon, 20 Feb 2023 14:32:30 +0200
> > <marius.cristea@microchip.com> wrote:
> >
> > > From: Marius Cristea <marius.cristea@microchip.com>
> > >
> > > Adding support for Microchip PAC193X series of Power Monitor with
> > > Accumulator chip family.
> >
> > This device is at the messy boundary between IIO and HWMON. Perhaps
> > call out
> > the reasons you think IIO is more appropriate in this cover letter.
> > + Often a good idea for these borderline parts to cc both mailing
> > lists and
> > maintainers.
> >
> > Often the conclusion is that it is fine to have these in IIO because
> > we can
> > bridge to hwmon anyway with the iio-hwmon driver.
> >
>
> Indeed the driver (the device) is at the boundary between IIO and
> HWMON. I was thinking to start with a simple driver (this one that is
> more apropiate to be a HWMON) and add more functionality later (like
> data buffering that is quite important for example if someone wants to
> profile power consumtion of the procesor itself, or a pheriperic, or a
> battery)
>
OK. List out some of the things you want to do later as the reasoning
+CC hmwon maintainers just to be sure. They are usually fine with this
sort of reasoning, but it is best to check anyway.
Thanks,
Jonathan
>
> > >
> > > Differences related to previous patch:
> > >
> > > v1:
> > > - first version comitted to review
> > >
> > >
> > > Marius Cristea (2):
> > > dt-bindings: iio: adc: adding dt-bindings for PAC193X
> > > iio: adc: adding support for pac193x
> > >
> > > .../bindings/iio/adc/microchip,pac193x.yaml | 122 +
> > > MAINTAINERS | 7 +
> > > drivers/iio/adc/Kconfig | 12 +
> > > drivers/iio/adc/Makefile | 1 +
> > > drivers/iio/adc/pac193x.c | 2072
> > > +++++++++++++++++
> > > 5 files changed, 2214 insertions(+)
> > > create mode 100644
> > > Documentation/devicetree/bindings/iio/adc/microchip,pac193x.yaml
> > > create mode 100644 drivers/iio/adc/pac193x.c
> > >
> >
>
> Thanks,
> Marius
>
prev parent reply other threads:[~2023-03-12 16:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 12:32 [PATCH v1 0/2] adding support for Microchip PAC193X Power Monitor marius.cristea
2023-02-20 12:32 ` [PATCH v1 1/2] dt-bindings: iio: adc: adding dt-bindings for PAC193X marius.cristea
2023-02-21 13:44 ` Krzysztof Kozlowski
2023-02-25 17:17 ` Jonathan Cameron
2023-03-06 13:53 ` Marius.Cristea
2023-03-06 16:09 ` Krzysztof Kozlowski
2023-03-06 16:26 ` Jonathan Cameron
2023-02-20 12:32 ` [PATCH v1 2/2] iio: adc: adding support for pac193x marius.cristea
2023-02-20 20:04 ` kernel test robot
2023-02-20 21:36 ` kernel test robot
2023-02-21 13:46 ` Krzysztof Kozlowski
2023-02-25 17:19 ` Jonathan Cameron
2023-02-25 17:22 ` Jonathan Cameron
2023-03-06 13:56 ` Marius.Cristea
2023-02-25 19:27 ` Jonathan Cameron
2023-03-06 15:42 ` Marius.Cristea
2023-03-12 16:42 ` Jonathan Cameron
2023-03-23 15:15 ` Marius.Cristea
2023-03-25 18:06 ` Jonathan Cameron
2023-02-25 17:11 ` [PATCH v1 0/2] adding support for Microchip PAC193X Power Monitor Jonathan Cameron
2023-03-06 14:03 ` Marius.Cristea
2023-03-12 16:45 ` Jonathan Cameron [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=20230312164533.491a7402@jic23-huawei \
--to=jic23@kernel.org \
--cc=Marius.Cristea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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