All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: ChiYuan Huang <cy_huang@richtek.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] iio: adc: rtq6056: Add support for the whole RTQ6056 family
Date: Wed, 3 Jan 2024 09:49:08 +0000	[thread overview]
Message-ID: <20240103094908.00006baf@Huawei.com> (raw)
In-Reply-To: <20240103010452.GA6655@linuxcarl2.richtek.com>

On Wed, 3 Jan 2024 09:04:52 +0800
ChiYuan Huang <cy_huang@richtek.com> wrote:

> On Tue, Jan 02, 2024 at 07:36:42PM +0000, Jonathan Cameron wrote:
> > On Tue, 2 Jan 2024 16:30:42 +0800
> > ChiYuan Huang <cy_huang@richtek.com> wrote:
> >   
> > > Hi, Johathan:
> > > 
> > > Most comments are good and will be fixed in next revision.
> > > 
> > > Still one comment I cannot make sure.
> > > 
> > > Please see the comment that's below yours.
> > > 	  
> > Hi ChiYuan,
> > 
> > It's good practice to crop away all the parts where the discussion is finished.
> > Makes it easier for people to find the bit you want discussion to continue on!
> > 
> > I've done so in this reply.
> > 
> > ...  
> > > > > +
> > > > >  enum {
> > > > >  	RTQ6056_CH_VSHUNT = 0,
> > > > >  	RTQ6056_CH_VBUS,
> > > > > @@ -50,16 +60,29 @@ enum {
> > > > >  enum {
> > > > >  	F_OPMODE = 0,
> > > > >  	F_VSHUNTCT,
> > > > > +	F_SADC = F_VSHUNTCT,    
> > > > 
> > > > If the devices have different register fields, better to have different enums
> > > > for them as well as that should result in less confusing code.
> > > >     
> > > Actually, this is all the same register, just the control naming difference.
> > > If not to define the new eum, I can remain to use the same field to handle rtq6059 part.  
> > 
> > If the bits in the register control the same thing across both parts then
> > add a comment alongside the enum to make that clear. 
> > 
> > Given the naming that seems very unlikely.  PGA and AVG would eman
> > very different things to me for starters (oversampling vs a programmble
> > gain amplifier on the front end)
> >   
> I'm also thinking how to write this difference like as comments or a seperate enum.
> But if to define a new enum, many function about the regfield controls must be seperated
> for 6056 and 6059.
> > > >     
> > > > >  	F_VBUSCT,
> > > > > +	F_BADC = F_VBUSCT,
> > > > >  	F_AVG,
> > > > > +	F_PGA = F_AVG,
> > > > >  	F_RESET,
> > > > >  	F_MAX_FIELDS
> > > > >  };  
> 
> What if to keep the original coding, just to rename the different part like as below
> F_SADC -> F_RTQ6059_SDAC
> F_BADC -> F_RTQ6059_BADC
> F_PGA -> F_RTQ6059_PGA

That works well. It makes it clear they are different across the parts.
So agreed this is the best option.
> 
> At least, the nameing already shows the difference between 6056 and 6059.
> Only these three parts are different, others are the same like as F_OPMODE, F_RESET.
> 
> 


  reply	other threads:[~2024-01-03  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 11:29 [PATCH v2 0/2] RTQ6056: Add compatible for the same chip family cy_huang
2023-12-28 11:29 ` [PATCH v2 1/2] dt-bindings: iio: adc: rtq6056: add support for the whole RTQ6056 family cy_huang
2023-12-28 11:50   ` Krzysztof Kozlowski
2023-12-28 11:29 ` [PATCH v2 2/2] iio: adc: rtq6056: Add " cy_huang
2023-12-30 12:03   ` Jonathan Cameron
2024-01-02  8:30     ` ChiYuan Huang
2024-01-02 19:36       ` Jonathan Cameron
2024-01-03  1:04         ` ChiYuan Huang
2024-01-03  9:49           ` Jonathan Cameron [this message]
2024-01-02  8:39     ` ChiYuan Huang

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=20240103094908.00006baf@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=conor+dt@kernel.org \
    --cc=cy_huang@richtek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.