mbox series

[RESEND,0/4] Drop ROHM BD70528 support

Message ID cover.1635412162.git.matti.vaittinen@fi.rohmeurope.com
Headers show
Series Drop ROHM BD70528 support | expand

Message

Matti Vaittinen Oct. 28, 2021, 9:18 a.m. UTC
Drop ROHM BD70528 support

Unfortunately there has not been a big demand for ROHM BD70528
IC. The few users I know control PMIC from separate M4-core,
which is not running Linux. I am not aware of any users of this
Linux driver.

While I did really like this IC and writing the drivers for it,
seems like these drivers are becoming useless burden. So, I see
no point in maintaining them. Let's just drop the drivers if
there is no objections to this series. :(

The regulator, WDG and power-supply drivers were already dropped.

The RTC and clk drivers remain in use by few other ROHM IC drivers.
Nevertheless, they are already converted to not depend the BD70528
defines during previous cycle.

This series cleans the remaining pieces, GPIO, MFD, dt-bindings and
MAINTAINER entries. The GPIO code uses defines from MFD - but the GPIO
part is also depending on MFD KConfig entry - so there should be no
breakages even if the patches were applied to respective subsystem trees
and were not carried via single tree.

---

Matti Vaittinen (4):
  dt-bindings: mfd: regulator: Drop BD70528 support
  gpio: bd70528 Drop BD70528 support
  mfd: bd70528: Drop BD70528 support
  MAINTAINERS: bd70528: Drop ROHM BD70528 drivers

 .../bindings/mfd/rohm,bd70528-pmic.txt        | 102 -----
 .../regulator/rohm,bd70528-regulator.txt      |  68 ---
 MAINTAINERS                                   |   8 -
 drivers/gpio/Kconfig                          |  11 -
 drivers/gpio/Makefile                         |   1 -
 drivers/gpio/gpio-bd70528.c                   | 230 -----------
 drivers/mfd/Kconfig                           |  17 -
 drivers/mfd/Makefile                          |   1 -
 drivers/mfd/rohm-bd70528.c                    | 314 --------------
 include/linux/mfd/rohm-bd70528.h              | 389 ------------------
 include/linux/mfd/rohm-generic.h              |   1 -
 11 files changed, 1142 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd70528-pmic.txt
 delete mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd70528-regulator.txt
 delete mode 100644 drivers/gpio/gpio-bd70528.c
 delete mode 100644 drivers/mfd/rohm-bd70528.c
 delete mode 100644 include/linux/mfd/rohm-bd70528.h


base-commit: 3906fe9bb7f1a2c8667ae54e967dc8690824f4ea

Comments

Andy Shevchenko Oct. 31, 2021, 1:06 p.m. UTC | #1
On Thu, Oct 28, 2021 at 12:18 PM Matti Vaittinen
<matti.vaittinen@fi.rohmeurope.com> wrote:
>
> Drop ROHM BD70528 support

I am always for the code removal, but the Q here is do you think there
won't be similar chips that may utilize the code and avoid duplication
in the future?
Matti Vaittinen Nov. 1, 2021, 6:18 a.m. UTC | #2
Hello Andy,

On 10/31/21 15:06, Andy Shevchenko wrote:
> On Thu, Oct 28, 2021 at 12:18 PM Matti Vaittinen
> <matti.vaittinen@fi.rohmeurope.com> wrote:
>>
>> Drop ROHM BD70528 support
> 
> I am always for the code removal, but the Q here is do you think there
> won't be similar chips that may utilize the code and avoid duplication
> in the future?

The BD70528 RTC driver will stay because we do really have couple of 
other PMICs with RTC blocks that have similarities to BD70528. Also the 
CLK driver used by BD70528 is also used by a few other ROHM ICs.

As for the regulators - The PMICs which I have seen from ROHM have 
pretty mauch all had different gpio control design. Seems like HW 
colleagues like reinventing the wheel. Well, perhaps this will 
eventually result a better wheel - for SW colleague this does bring some 
additional work though...

Same goes with the GPIOs - although - as you probably know - I do think 
many of the GPIOs could be handled by a generic GPIO helpers by allowing 
IC specific GPIO config functions. Well, the BD70528 GPIO driver is not 
written to be generic - and no, I don't see similar GPIO block in other 
ROHM PMICs. Same goes with the MFD.

After all this being written - code dublication won't be an issue if we 
_drop_ the BD70528 support. Even re-adding similar driver for another IC 
in the future won't bring dublication as BD70528 is dropped. And if we 
will see BD70528 v2.0 - then I (or someone else) can dig the old BD70528 
drivers - or write a new ones - and bring them back in-tree. But until 
that happens carrying the existing drivers is just an additional burden 
and waste. The BD70528 v2.0 may never come.

Well, don't get me wrong. The BD70528 drivers won't bother me in 
community kernel. I do like seeing my name in the spotlight XD What I do 
not like is leaving others to hold up the light - or to pay the 
electricity for it :)

So yes. I did submit this patch series as I really think maintaining the 
driver(s) for dead IC is not worth the work :/ Oh, by the way, part of 
the drivers were already dropped during the previous cycles.

Best Regards
   -- Matti Vaittinen