All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] drivers: rtc: remove dead drivers
Date: Tue, 5 Aug 2014 20:34:23 -0600	[thread overview]
Message-ID: <CAPnjgZ3DUndr=T6Z5fgcrN+p_ZvkHdnouCZDnwugyYWk7s+w9Q@mail.gmail.com> (raw)
In-Reply-To: <53E08314.4090003@denx.de>

Hi,

On 5 August 2014 01:09, Stefano Babic <sbabic@denx.de> wrote:
> Hi Tom, hi Masahiro,
>
> On 04/08/2014 19:30, Tom Rini wrote:
>> On Wed, Jul 30, 2014 at 07:20:03PM +0900, Masahiro Yamada wrote:
>>
>>> The following configs are not defined at all:
>>>
>>>  - CONFIG_RTC_DS1388
>>>  - CONFIG_RTC_ISL1208
>>>  - CONFIG_RTC_MX27
>>>  - CONFIG_RTC_PL031
>>>  - CONFIG_RTC_RS5C372A
>>>  - CONFIG_SYS_DS1388_TCR_VAL
>>>
>>> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
>>
>> I'm inclined to NAK this.  I can't speak to MX27 (Stefano?)
>> but in other
>> cases those RTCs can be breadboarded up on other EVMs or otherwise
>> used in things that aren't quite upstream.
>
> I agree with Tom. RTC_MX27 was tested and submitted with the armadeus
> apf27 board, but then another RTC was chosen on this target. The
> RTC_MX27 remains ready to be used.
> It is easy to enable this driver on some other targets - if these kind
> of drivers are not explicitely broken, I think we should let live in
> mainline.

Would it be possible to add a board to use these, just so it is not
dead code? Even a fake board?

Regards,
Simon

  reply	other threads:[~2014-08-06  2:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 10:20 [U-Boot] [PATCH] drivers: rtc: remove dead drivers Masahiro Yamada
2014-08-04 17:30 ` Tom Rini
2014-08-05  1:16   ` Masahiro Yamada
2014-08-05  7:09   ` Stefano Babic
2014-08-06  2:34     ` Simon Glass [this message]
2014-08-06 11:01       ` Stefano Babic

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='CAPnjgZ3DUndr=T6Z5fgcrN+p_ZvkHdnouCZDnwugyYWk7s+w9Q@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.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.