linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org
Subject: Re: ADB Reset
Date: Thu, 11 Mar 1999 12:53:29 +0100	[thread overview]
Message-ID: <19990311125329.016856@mail.mipsys.com> (raw)
In-Reply-To: <199903102251.JAA08378@tango.anu.edu.au>


On Thu, Mar 11, 1999, Paul Mackerras <paulus@cs.anu.edu.au> wrote:

>If we have two devices with the same default ID, they may get assigned
>different IDs after re-probing.  Any ideas how to cope with that?
>
>On my 3400, after a snooze, sometimes the adb bus has been reset and
>sometimes it hasn't.  I haven't been able to discern any pattern,
>e.g. it doesn't seem to depend on how long the machine is asleep for.
>I believe that the power to the adb bus is supposed to stay on during
>sleep, so I don't see why it's getting reset.

I plan to re-do the entire bus reset, probing and intialisation after the
sleep. Actually, anyone (and so ADB device handlers) will be able to
register a notification proc with the ADB core. Messages will be sent to
devices before and after a bus reset, at initialisation time, and
eventually in other circumstances.
Sleep will cause a reset (but with an additional parameter indicating
that it's coming from a sleep, so that the device knows that the power on
the bus may be turned off. This may be useful for some devices).

Under MacOS, the bus is reset after sleep and devices are notified via a
low-memory hook just before and after the bus reset.


-- 
           E-Mail: <mailto:bh40@calva.net>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>





[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-03-11 11:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-05 10:08 ADB Reset Hubert Figuiere
1999-03-05 14:32 ` Benjamin Herrenschmidt
1999-03-10 11:36   ` Hubert Figuiere
1999-03-10 12:19     ` Benjamin Herrenschmidt
1999-03-10 16:40       ` Hubert Figuiere
1999-03-10 22:51       ` Paul Mackerras
1999-03-11 11:53         ` Benjamin Herrenschmidt [this message]
1999-03-11  7:55       ` Hubert Figuiere
1999-03-11 15:37         ` David A. Gatwood
1999-03-10 15:43     ` David A. Gatwood
  -- strict thread matches above, loose matches on Subject: below --
1999-03-05 13:47 Christian Jaeger
1999-03-05 18:46 ` Hubert Figuiere
1999-03-11 13:16 Benjamin Herrenschmidt
1999-03-11 14:26 ` Geert Uytterhoeven

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=19990311125329.016856@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).