devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Marius.Cristea@microchip.com>
To: <jic23@kernel.org>, <krzk@kernel.org>
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 2/2] iio: adc: adding support for pac193x
Date: Mon, 6 Mar 2023 13:56:06 +0000	[thread overview]
Message-ID: <149491f6acdfeb4f1a6da7798e27ca984aace19b.camel@microchip.com> (raw)
In-Reply-To: <20230225172255.7b79374a@jic23-huawei>


Hi Krzysztof,


   Thank you for your review comments. I will handle all of them.

Thanks,
Marius

On Sat, 2023-02-25 at 17:22 +0000, Jonathan Cameron wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> On Sat, 25 Feb 2023 17:19:54 +0000
> Jonathan Cameron <jic23@kernel.org> wrote:
> 
> > On Tue, 21 Feb 2023 14:46:08 +0100
> > Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > 
> > > On 20/02/2023 13:32, marius.cristea@microchip.com wrote:
> > > > From: Marius Cristea <marius.cristea@microchip.com>
> > > > 
> > > > This is the iio driver for Microchip
> > > > PAC193X series of Power Monitor with Accumulator chip family.
> > > > 
> > > > Signed-off-by: Marius Cristea <marius.cristea@microchip.com>
> > > > ---
> > > >  MAINTAINERS               |    7 +
> > > >  drivers/iio/adc/Kconfig   |   12 +
> > > >  drivers/iio/adc/Makefile  |    1 +
> > > >  drivers/iio/adc/pac193x.c | 2072
> > > > +++++++++++++++++++++++++++++++++++++
> > > >  4 files changed, 2092 insertions(+)
> > > >  create mode 100644 drivers/iio/adc/pac193x.c
> > > > 
> > > 
> > > 
> > > Thank you for your patch. There is something to discuss/improve.
> > > 
> > > > +
> > > > +#define PAC193X_NEG_PWR_CH1_BIDI(x)      ((x) ? BIT(7) : 0)
> > > > +#define PAC193X_NEG_PWR_CH2_BIDI(x)      ((x) ? BIT(6) : 0)
> > > > +#define PAC193X_NEG_PWR_CH3_BIDI(x)      ((x) ? BIT(5) : 0)
> > > > +#define PAC193X_NEG_PWR_CH4_BIDI(x)      ((x) ? BIT(4) : 0)
> > > > +#define PAC193X_NEG_PWR_CH1_BIDV(x)      ((x) ? BIT(3) : 0)
> > > > +#define PAC193X_NEG_PWR_CH2_BIDV(x)      ((x) ? BIT(2) : 0)
> > > > +#define PAC193X_NEG_PWR_CH3_BIDV(x)      ((x) ? BIT(1) : 0)
> > > > +#define PAC193X_NEG_PWR_CH4_BIDV(x)      ((x) ? BIT(0) : 0)
> > > > +
> > > > +/*
> > > > + * Universal Unique Identifier (UUID),
> > > > + * 033771E0-1705-47B4-9535-D1BBE14D9A09, is
> > > > + * reserved to Microchip for the PAC193X and must not be
> > > > changed
> > > > + */
> > > > +#define PAC193X_DSM_UUID         "033771E0-1705-47B4-9535-
> > > > D1BBE14D9A09"
> > > > +
> > > > +enum pac193x_ids {
> > > > + pac1934,
> > > > + pac1933,
> > > > + pac1932,
> > > > + pac1931
> > > 
> > > Enums are usually uppercase.
> > 
> > I'm not sure there is anything in coding standard around that and a
> > grep finds
> > a mixture of the two when it comes to ones used for IDs.  Mind you
> > uppercase
> > is fine :)
> I take it back. Is indeed in coding style doc.  Glad checkpatch
> doesn't check for
> this though as we'd get 1000s of 'fixes' if it did and in most cases
> it doesn't
> hurt readability.  I'll try and be more consistent on this in review
> going forwards!
> 
> Thanks!
> 
> Jonathan
> 
> > 
> > 
> > > 
> > > 
> > > 
> > > Best regards,
> > > Krzysztof
> > > 
> > 
> 


  reply	other threads:[~2023-03-06 13:56 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 [this message]
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

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=149491f6acdfeb4f1a6da7798e27ca984aace19b.camel@microchip.com \
    --to=marius.cristea@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzk@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;
as well as URLs for NNTP newsgroup(s).