From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Ryan Mallon <ryan@bluewatersys.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
spi-devel-general@lists.sourceforge.net, mike@steroidmicros.com,
linux kernel <linux-kernel@vger.kernel.org>,
dedekind@infradead.org
Subject: Re: [PATCH] SST25L (non JEDEC) SPI Flash driver
Date: Tue, 23 Jun 2009 09:04:57 +0200 [thread overview]
Message-ID: <63386a3d0906230004m66360f4fhbdc80c8e552a01d0@mail.gmail.com> (raw)
In-Reply-To: <4A3FFE02.8020001@bluewatersys.com>
2009/6/22 Ryan Mallon <ryan@bluewatersys.com>:
> Out of curiosity: I'm not too clear on what makes a particular chip
> hot-pluggable. I think technically the sst25l chip could be put onto a
> hot-pluggable board or power domain. Can't most devices be made
> hot-pluggable? Is the general rule to make devices non hot-pluggable if
> most/all boards in the mainline do not allow it to be hot-plugged?
I haven't seen any rule about it, but nominally the drivers support the
configurations found in the kernel tree, so if some board physically
existing and soon-to-run linux hotplugs chips like this, then have it
__dev{init|exit} else __{init|exit} IMHO.
Of course you can design for all plausible use cases but it will pile up
indefinitely. Personally I try to not design software for a hardware until it
exists, and I like the IETF catch-phrase "rough consensus and running
code" and this sort of fits that :-)
Yours,
Linus Walleij
next prev parent reply other threads:[~2009-06-23 7:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 3:58 Ryan Mallon
2009-06-22 4:14 ` [spi-devel-general] " Baruch Siach
2009-06-22 4:25 ` Ryan Mallon
2009-06-22 8:15 ` Artem Bityutskiy
2009-06-22 8:22 ` Linus Walleij
2009-06-22 21:56 ` Ryan Mallon
2009-06-23 7:04 ` Linus Walleij [this message]
2009-06-23 20:48 ` Ryan Mallon
2009-06-24 22:43 ` Linus Walleij
2009-06-24 22:49 ` Ryan Mallon
2009-06-24 23:49 ` Linus Walleij
2009-06-25 1:39 ` [spi-devel-general] " H Hartley Sweeten
2009-06-25 2:06 ` Ryan Mallon
2009-06-25 2:30 ` H Hartley Sweeten
2009-06-25 2:52 ` Ryan Mallon
2009-06-25 7:49 ` Linus Walleij
2009-06-24 23:59 Ryan Mallon
2009-06-25 0:08 ` Linus Walleij
2009-06-25 2:40 ` Andrew Morton
2009-06-25 3:07 ` Ryan Mallon
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=63386a3d0906230004m66360f4fhbdc80c8e552a01d0@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mike@steroidmicros.com \
--cc=ryan@bluewatersys.com \
--cc=spi-devel-general@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®