[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8501493.uUGsNVQOhe@wuerfel>
Date: Thu, 23 Oct 2014 17:23:55 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
wim@...ana.be, linux-watchdog@...r.kernel.org, linux@...ck-us.net,
David Paris <david.paris@...com>, kernel@...inux.com
Subject: Re: [PATCH 4/4] watchdog: st_wdt: Add new driver for ST's LPC Watchdog
On Thursday 23 October 2014 16:18:44 Lee Jones wrote:
> +config ST_WATCHDOG
> + tristate "STMicroelectronics LPC Watchdog"
> + depends on ARCH_STI && OF
> + depends on !RTC_DRV_ST_LPC
> + select WATCHDOG_CORE
> + help
> + Say Y here to include Watchdog timer support for the watchdog
> + existing in the LPC of STMicroelectronics SOCs.
> + !!! BE CARREFUL !!!
> + This driver shares hardware resources with RTC Alarm part of the
> + LPC. Both LPC Watchdog driver and LPC RTC driver cannot be
> + used together.
> +
> + To compile this driver as a module, choose M here: the
> + module will be called st-wdt.
> +
>
How is this ensured by the code? Do both drivers try to bind to the
same device node? Would it make more sense to have a single driver
that registers both to the rtc and the watchdog subsystems?
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists