From: Lee Jones <lee.jones@linaro.org>
To: ChiYuan Huang <u0084500@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Mark Brown <broonie@kernel.org>,
dmitry.torokhov@gmail.com, Liam Girdwood <lgirdwood@gmail.com>,
cy_huang <cy_huang@richtek.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: [PATCH v2 2/4] mfd: rt5120: Add Richtek PMIC support
Date: Mon, 4 Jul 2022 10:54:40 +0100 [thread overview]
Message-ID: <YsK44Dp3yZwqPi0H@google.com> (raw)
In-Reply-To: <CADiBU3_7MmPkfV7-B8rhxFRtZcrJ6BPocXzT4bs3cu36UR5XGw@mail.gmail.com>
On Mon, 04 Jul 2022, ChiYuan Huang wrote:
> Hi, Lee:
>
> ChiYuan Huang <u0084500@gmail.com> 於 2022年7月1日 週五 下午5:56寫道:
> >
> > Lee Jones <lee.jones@linaro.org> 於 2022年7月1日 週五 下午3:38寫道:
> > >
> > > On Fri, 01 Jul 2022, ChiYuan Huang wrote:
> > >
> > > > HI, Lee:
> > > >
> > > > ChiYuan Huang <u0084500@gmail.com> 於 2022年6月27日 週一 晚上10:56寫道:
> > > > >
> > > > > Lee Jones <lee.jones@linaro.org> 於 2022年6月27日 週一 晚上10:22寫道:
> > > > > >
> > > > > > On Wed, 22 Jun 2022, cy_huang wrote:
> > > > > >
> > > > > > > From: ChiYuan Huang <cy_huang@richtek.com>
> > > > > > >
> > > > > > > Add Richtek RT5120 PMIC I2C driver.
> > > > > >
> > > > > > Why a whole new driver?
> > > > > >
> > > > > > How different is this to rt5033?
> > > > > >
> > > > > > Looks like this could easily be woven into this existing support?
> > > > > >
> > > > > It's different with the function domain.
> > > > > RT5033 is most like as the SubPMIC that includes PMU (battery
> > > > > charger/gauge/led/few buck and ldo)
> > > > > RT5120 is a main PMIC with default-on power that follows the boot on sequence.
> > > > > RT5120 only integrates regulator and power key report module.
> > > > >
> > > > Since I have explained the chip difference, do you still think it's
> > > > better to merge this code into rt5033 mfd?
> > >
> > > I think it's okay to group devices which are similar but not exactly
> > > the same, if they can be. The integration of this device into the
> > > other looks trivial to my naive eyes.
> > >
> > > A PMIC is a PMIC, main or sub.
> > >
> > M.. ok. I will try to group all chip changes like as devices
> > list/regmap_irq/regmap_config ..., etc.
> > Treat it as one set of chip config and use 'of_device_get_match_data'
> > to get the chip config data.
> >
> There's a question.
> As I know, it's not the same chip series.
> The rt5033 is submitted from Samsung at 2015.
> The driver data is also defined in header file.
>
> Do you still suggest to do the merge?
> Even in our internal, it's difficult to find a rt5033 EVB for testing.
>
> And one more question is the binding. If yes, for the binding, I need to add
> rt5033 related.....
>
> Actually, it's a tough work.
If it's genuinely difficult to integrate, you can keep them separate.
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2022-07-04 9:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 10:01 [PATCH v2 0/4] Add Richtek RT5120 PMIC support cy_huang
2022-06-22 10:01 ` [PATCH v2 1/4] dt-binding: mfd: " cy_huang
2022-06-22 14:48 ` Krzysztof Kozlowski
2022-06-22 10:01 ` [PATCH v2 2/4] mfd: rt5120: Add Richtek " cy_huang
2022-06-27 14:22 ` Lee Jones
2022-06-27 14:56 ` ChiYuan Huang
2022-07-01 6:57 ` ChiYuan Huang
2022-07-01 7:37 ` Lee Jones
2022-07-01 9:56 ` ChiYuan Huang
2022-07-04 9:14 ` ChiYuan Huang
2022-07-04 9:54 ` Lee Jones [this message]
2022-07-05 3:04 ` ChiYuan Huang
2022-06-22 10:01 ` [PATCH v2 3/4] regulator: rt5120: Add PMIC regulator support cy_huang
2022-06-22 10:01 ` [PATCH v2 4/4] input: misc: rt5120: Add power key support cy_huang
2022-07-09 4:53 ` Dmitry Torokhov
2022-07-11 3:43 ` ChiYuan Huang
2022-06-23 13:23 ` (subset) [PATCH v2 0/4] Add Richtek RT5120 PMIC support Mark Brown
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=YsK44Dp3yZwqPi0H@google.com \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=u0084500@gmail.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;
as well as URLs for NNTP newsgroup(s).