From: Wim Van Sebroeck <wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Linux PPC Development
<linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 3/3] mpc52xx/wdt: WDT uses GPT api
Date: Tue, 8 Dec 2009 21:48:54 +0100 [thread overview]
Message-ID: <20091208204854.GE4291@infomag.iguana.be> (raw)
In-Reply-To: <fa686aa40911122221s24efdcc9k1daf63b600e7b429-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Grant,
Sorry for the delay, I need to deliver a project in a weeks time...
> In actual fact, it is a single device with multiple functions, some of
> which can be used at the same time. The driver for the device
> determines what the device instance supports and registers the
> appropriate interfaces. There is a GPIO controller, a PWM controller,
> a general purpose timer, and the watchdog. Because of the
> multifunction nature of the device, there are subtle interactions
> between the functions that the driver needs to maintain. I don't want
> to export functions from the driver which will only be used by a
> watchdog instance. I also don't want the added code and complexity of
> a secondary probe path. It is simpler and less code to roll all the
> behaviour up into the one driver single driver that gets probed once.
>
> >From the maintenance perspective, having the main driver in
> arch/powerpc and the watchdog bit in drivers/watchdog doesn't really
> help much anyway because anything that changes the internal driver API
> (between the core and watchdog bits) will require cross-maintainer
> changes. ie. do changes go through my tree because they touch
> arch/powerpc, or do they go through yours because they touch
> drivers/watchdog? I'd much rather all the internal details be
> contained within a single driver.
Your argument about maintenance is the same one as I have: If all watchdog
driver pieces are under drivers/watchdog then it's easier for me to maintain
them. (Definitely if we are doing clean-up work and API changes).
> Besides, there is already precedence for very arch-specific drivers
> living under arch/*/. find ./arch -name *gpio*
But in this case: I know where to find them and I will keep a mental note
about this one. And yes indeed some very arch specific drivers can reside
under arch/*/* .
So please go ahead with pulling this one in a single driver.
Kind regards,
Wim.
next prev parent reply other threads:[~2009-12-08 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 19:43 [PATCH 3/3] mpc52xx/wdt: WDT uses GPT api Albrecht Dreß
2009-11-10 19:59 ` Grant Likely
2009-11-10 20:26 ` Albrecht Dreß
2009-11-10 21:07 ` Grant Likely
2009-11-11 8:32 ` Aw: " Albrecht Dreß
[not found] ` <16246194.1257928342802.JavaMail.ngmail-hrWuGRo80rRiK3oW1guXusM6rOWSkUom@public.gmane.org>
2009-11-11 20:18 ` Grant Likely
2009-11-12 21:36 ` Wim Van Sebroeck
[not found] ` <20091112213630.GE19336-flHiHfN8CTwhDM6iD19NGrNAH6kLmebB@public.gmane.org>
2009-11-13 6:21 ` Grant Likely
[not found] ` <fa686aa40911122221s24efdcc9k1daf63b600e7b429-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-08 20:48 ` Wim Van Sebroeck [this message]
[not found] ` <20091208204854.GE4291-flHiHfN8CTwhDM6iD19NGrNAH6kLmebB@public.gmane.org>
2009-12-08 21:21 ` Grant Likely
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=20091208204854.GE4291@infomag.iguana.be \
--to=wim-iqzoog9ftrqzqb+pc5nmwq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.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