All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dannenberg <dannenberg@ti.com>
To: "Sebastian Reichel" <sre@kernel.org>,
	"Dmitry Eremin-Solenikov" <dbaryshkov@gmail.com>,
	"David Woodhouse" <dwmw2@infradead.org>,
	"Pali Rohár" <pali.rohar@gmail.com>,
	"Laurentiu Palcu" <laurentiu.palcu@intel.com>
Cc: linux-pm@vger.kernel.org
Subject: [RFC] TI BQ242xx Battery Charger Development/Consolidation Plans
Date: Wed, 5 Aug 2015 11:28:39 -0500	[thread overview]
Message-ID: <55C239B7.4000902@ti.com> (raw)

Not too long I ago started working on a new driver called bq242xx_charger.c 
that will add support for TI's BQ24250, BQ24251, BQ24261M, and BQ24262 Li-Ion
battery charger/power-path management ICs and that work is about 50% done. I 
chose a working name of bq242xx_charger.c in the hopes that in addition to
providing immediate support for said devices that this driver can later be used
as a platform to add other devices of the BQ242xx sub-family in an effort to
re-use/consolidate and help keep drivers/power organized.

Long story short I also realized that we just got a new bq24257_charger.c
driver (for the BQ24257) already in the Linux 4.2 tree which creates somewhat
of a conflict with the bq242xx_charger.c work in progress.

I would like to solicit ideas/comments regarding the following plan of attack:

- Continue bq242xx_charger.c development as scoped in the first paragraph
- Work on getting it accepted into upstream
- As future work, absorb the already existing bq24257_charger.c driver into the
  bq242xx_charger.c driver, and deprecate its usage

There might be a potential risk for user confusion for a transitional time if
somebody was just looking at the filenames to select their driver due to part
number overlap. However I argue folks are more likely to go the Kconfig route
to select their driver so this may not be a problem after all.

Thanks!

--
Andreas Dannenberg Texas Instruments Inc.

             reply	other threads:[~2015-08-05 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 16:28 Andreas Dannenberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-04 16:36 [PATCH RESEND] power: bq24190_charger: Fix charge type sysfs property Andreas Dannenberg
2015-08-05 16:05 ` [RFC] TI BQ242xx Battery Charger Development/Consolidation Plans Andreas Dannenberg
2015-08-07  8:58   ` Laurentiu Palcu
2015-08-11 11:12     ` Pallala, Ramakrishna
2015-08-12 16:20       ` Andreas Dannenberg
2015-08-13 16:19         ` Pallala, Ramakrishna
2015-08-12 16:10     ` Andreas Dannenberg

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=55C239B7.4000902@ti.com \
    --to=dannenberg@ti.com \
    --cc=dbaryshkov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=laurentiu.palcu@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=sre@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 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.