linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 01/14] watchdog/mpcore_wdt: Mark it as BROKEN
Date: Wed, 19 Jun 2013 09:56:03 +0200	[thread overview]
Message-ID: <319bb53672a5fa97b7aa603392b6a2fa@localhost> (raw)
In-Reply-To: <CAKohpom3S3NMhxbhbmyC6bceS51727CnWRWmWDGxwDcRJkHFyQ@mail.gmail.com>

On Wed, 19 Jun 2013 08:40:25 +0530, Viresh Kumar <viresh.kumar@linaro.org>
wrote:
> Wow!! So many replies, let me reply to everyone in this chain.
> 
> On 18 June 2013 22:05, Olof Johansson <olof@lixom.net> wrote:
>> On Tue, Jun 18, 2013 at 9:11 AM, Marc Zyngier <marc.zyngier@arm.com>
>> wrote:
>>> On 18/06/13 16:42, Guenter Roeck wrote:
>>>> On Tue, Jun 18, 2013 at 08:50:25PM +0530, Viresh Kumar wrote:
> 
>>>>> Lets mark it broken until somebody with this hardware gets up and
>>>>> fixes it.
>>>>>
>>>> I must be missing something. What is the point of the remaining
>>>> patches in this
>>>> case ?
> 
> In case somebody wakes up and tries to fix this driver, he doesn't have
to
> write stuff which I already wrote. That's it. This stuff was pending in
my
> tree
> for more than a year now and I wanted to get rid of it (without deleting
> it) :)
> 
>>> Indeed. This looks like pointless churn to me, unless someone actually
>>> picks up the driver and fixes it for good.
>>>
>>> If nobody cares enough about it, then maybe it should be moved into
>>> staging and eventually retired...
>>
>>
>> That was a year ago, and nobody has done anything to the driver. Just
>> remove it -- if someone wants to do the work later on it's easy to
>> revert the commit and start over.
>>
>> Keeping code in the kernel but marking it BROKEN is only useful if we
>> think someone will fix it soon. It seems very unlikely in this case.
> 
> I believed that this is the driver which will be used by all cortex
> family, i.e.
> all ARM SMP platforms, isn't it? I am sure atleast the A9 family had
this.

ARM11, A5 and A9 in their MP configurations only.

> If no, then which ones are the real users of this driver/hardware?
> If yes, Why isn't anybody using this?

Because, as Russell mentioned, the piece of IP doesn't fit our watchdog
model at all (per-CPU watchdog???), and most SoCs/boards have a separate
watchdog anyway.

> I will send a patch that will delete this driver and will provide link
to
> my
> patches, in case somebody wants it back in future.

Thanks.

        M.
-- 
Fast, cheap, reliable. Pick two.

  reply	other threads:[~2013-06-19  7:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 15:20 [PATCH V3 00/14] watchdog: ARM mpcore Improvements Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 01/14] watchdog/mpcore_wdt: Mark it as BROKEN Viresh Kumar
2013-06-18 15:42   ` Guenter Roeck
2013-06-18 16:11     ` Marc Zyngier
2013-06-18 16:35       ` Olof Johansson
2013-06-19  3:10         ` Viresh Kumar
2013-06-19  7:56           ` Marc Zyngier [this message]
2013-06-19  8:15             ` Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 02/14] watchdog/mpcore_wdt: convert to watchdog core Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 03/14] watchdog/mpcore_wdt: Fix multiline comments Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 04/14] watchdog/mpcore_wdt: Arrange #includes in alphabetical order Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 05/14] watchdog/mpcore_wdt: Set default heartbeat in probe instead of init Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 06/14] watchdog/mpcore_wdt: convert to use module_platform_driver() Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 07/14] watchdog/mpcore_wdt: Add support for dev_pm_ops interface Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 08/14] watchdog/mpcore_wdt: disable wdt in suspend only if it is busy Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 09/14] watchdog/mpcore_wdt: replace (__raw_)readl/writel with lighter *_relaxed variants Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 10/14] watchdog/mpcore_wdt: Add support for WDIOC_GETBOOTSTATUS IOCTL Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 11/14] watchdog/mpcore_wdt: Add clock framework support Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 12/14] watchdog/mpcore_wdt: use correct clk_rate to program timeout Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 13/14] watchdog/mpcore_wdt: Start registers from 0x00 instead of 0x20 Viresh Kumar
2013-06-18 15:20 ` [PATCH V3 14/14] watchdog/mpcore_wdt: Add DT probing support for ARM mpcore watchdog Viresh Kumar
2013-06-18 16:03 ` [PATCH V3 00/14] watchdog: ARM mpcore Improvements Russell King - ARM Linux

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=319bb53672a5fa97b7aa603392b6a2fa@localhost \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).