From: "Choi Sonim" <choisonim@gmail.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] /sys/devices/platform/bluetooth
Date: Fri, 19 Jan 2007 01:59:09 +0200 [thread overview]
Message-ID: <4f436aae0701181559h63b7d509n5dc73c55353d8c79@mail.gmail.com> (raw)
In-Reply-To: <1169164343.6853.7.camel@violet>
Hi Marcel,
On 1/19/07, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Choi,
>
> > > > Where is the code that does the platform registration to this device :
> > > > /sys/devices/platform/bluetooth
> > >
> > > you find it in net/bluetooth/hci_sysfs.c in the kernel source code.
> >
> > What is the purpose of the bluetooth platform device (and bus and class..) ?
> >
> > I guess that bluetooth devices would prefer to register themselves as children
> > of their true bus (like USB or PCI or even serial) so when the system goes
> > to suspend, their suspend function will be called before their father's
> > (the true hardware bus of our bluetooth device).
>
> if they do have a physical parent. Some devices like virtual HCI or
> serial based chips don't have a physical parent.
About the serial based chips -
I'm sure they would like their suspend function to be called before the
serial uart driver's suspend, so for them to set device parent to the
serial device
can be a benefit too, no ?
About the virtual HCI - I really don't know what are them, can you please
explain this ?
Thank You Very very Much !
Choi.
>
> Regards
>
> Marcel
>
>
>
next prev parent reply other threads:[~2007-01-18 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 6:08 [Bluez-devel] /sys/devices/platform/bluetooth Choi Sonim
2007-01-18 8:13 ` Marcel Holtmann
2007-01-18 23:23 ` Choi Sonim
2007-01-18 23:52 ` Marcel Holtmann
2007-01-18 23:59 ` Choi Sonim [this message]
2007-01-19 1:02 ` Marcel Holtmann
2007-01-19 6:26 ` Choi Sonim
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=4f436aae0701181559h63b7d509n5dc73c55353d8c79@mail.gmail.com \
--to=choisonim@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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