All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Gregory <gg@slimlogic.co.uk>
To: Oleksandr Kozaruk <oleksandr.kozaruk@ti.com>
Cc: Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	sameo@linux.intel.com, lgirdwood@gmail.com, balbi@ti.com,
	peter.ujfalusi@ti.com, t-kristo@ti.com, tony@atomide.com
Subject: Re: [RFC v1] MFD: Change TWL6025 references to TWL6032
Date: Thu, 13 Jun 2013 11:32:42 +0100	[thread overview]
Message-ID: <20130613103242.GA5456@mint> (raw)
In-Reply-To: <51B99D0D.4050603@ti.com>

On Thu, Jun 13, 2013 at 01:21:01PM +0300, Oleksandr Kozaruk wrote:
> On 06/07/2013 05:44 PM, gg@slimlogic.co.uk wrote:
> >On 2013-06-07 15:36, Mark Brown wrote:
> >>On Fri, Jun 07, 2013 at 01:53:10PM +0300, Oleksandr Kozaruk wrote:
> >>>From: Graeme Gregory <gg@slimlogic.co.uk>
> >>>
> >>>The TWL6025 was never released beyond sample form and was replaced by
> >>>the PhoenixLite range of chips - TWL6032. Change the references to
> >>>reference the TWL6032 class and name the registers to twl6032
> >>>in line with
> >>>an actual released chip name to avoid confusion.
> >>>
> >>>Currently there is no users of TWL6025 in the code.
> >>
> >>Given that the chip exists even if not widely distributed it seems as
> >>well to keep the twl6025 references in there at least in the device ID
> >>table - it won't do any harm to people using the twl6032 name and might
> >>help someone who happens to pick up an old board for whatever reason.
> >
> >I do not think any "old boards" exist, it really was a limited run!
> >
> >Graeme
> >
> Hello Mark, Graeme,
> 
> Taking in account that:
> - there is no hardware to test twl6025, testing is not possible;
> - there is no documentation for twl6025, and if there are any
> changes to twl6032 is not known;
> - twl6032 is available, and in production, twl6025 is not even found
> on ti.com <http://ti.com>
> 
> So, what do you think, can this change be accepted?
> 
> // I apologize for sending personal e-mails, not to the mail list

I have never seen a twl6025 board, it only ever existed AFAIK in lab samples
which were used on a generic carrier board. twl6032 was the actual production
device.

Graeme


  reply	other threads:[~2013-06-13 15:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 10:53 [RFC v1] MFD: Change TWL6025 references to TWL6032 Oleksandr Kozaruk
2013-06-07 10:53 ` Oleksandr Kozaruk
2013-06-07 14:36 ` Mark Brown
2013-06-07 14:44   ` gg
2013-06-13  7:56     ` Oleksandr Kozaruk
2013-06-13  7:56       ` Oleksandr Kozaruk
2013-06-13 10:21     ` Oleksandr Kozaruk
2013-06-13 10:21       ` Oleksandr Kozaruk
2013-06-13 10:32       ` Graeme Gregory [this message]
2013-06-13 10:38     ` Oleksandr Kozaruk
2013-06-13 10:38       ` Oleksandr Kozaruk
     [not found]     ` <CAPb7_mtVg7Uz6jS5BwCCxo-dcju6Ophh4+QWG7N5zOHJQixw5A@mail.gmail.com>
2013-06-13 11:20       ` Oleksandr Kozaruk
2013-06-13 11:20         ` Oleksandr Kozaruk
2013-06-19  8:35 ` Lee Jones

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=20130613103242.GA5456@mint \
    --to=gg@slimlogic.co.uk \
    --cc=balbi@ti.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=oleksandr.kozaruk@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.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 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.