From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: lkcl luke <luke.leighton@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux on small ARM machines <arm-netbook@lists.phcomp.co.uk>
Subject: Re: [advice sought] EOMA68 kernel support
Date: Sat, 10 Mar 2012 19:51:05 +0000 [thread overview]
Message-ID: <20120310195105.6d301bd5@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAPweEDx3ktAgz9vdM+E-c5YZGrbBMbX4TOy+QUHV3mRM28oWRw@mail.gmail.com>
> of particular concern is that a CPU card could be running on (small!)
> backup battery / supercapacitor whilst being hot-swapped, and thus
> that means that the LCD module (drivers/eoma68/lcd.ko?) would need to
> be loaded and unloaded from userspace (udev). that's not going to be
> a problem, is it? i may just be imagining skeletons in the closet,
> here.
Your device tree describes devices. Your bus creates them when you
hotplug and it removes them when you hot unplug. The rest is the drivers
problem to behave properly, and refcount right.
> * it's the purposes to which the 16 GPIOs can be put that will be
> radically different from one I/O board to the next. GPIO 0 could be
> "powerup for WIFI" on one I/O board, but "lid open/shut switch" on
> another.
It's "GPIO 0 of card X" and providing you remember that, watch your
refcounting and don't remap a new device over the address space of an old
one during a hotplug you should be fine.
Alan
next prev parent reply other threads:[~2012-03-10 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 22:41 lkcl luke
2012-03-10 6:45 ` lkcl luke
2012-03-10 12:40 ` [Arm-netbook] " Henrik Nordström
2012-03-10 13:00 ` Alan Cox
2012-03-10 13:25 ` lkcl luke
2012-03-10 19:51 ` Alan Cox [this message]
2012-03-10 20:20 ` lkcl luke
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=20120310195105.6d301bd5@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arm-netbook@lists.phcomp.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.leighton@gmail.com \
/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®