From: Finn Thain <fthain@telegraphics.com.au> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>, Michael Ellerman <mpe@ellerman.id.au>, Joshua Thompson <funaho@jurai.org>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH] macintosh/adb-iop: Send correct poll command Date: Sat, 5 Dec 2020 14:10:21 +1100 (AEDT) [thread overview] Message-ID: <alpine.LNX.2.23.453.2012051340490.6@nippy.intranet> (raw) In-Reply-To: <CAMuHMdVYf83+y1aUR6HqCgr-CLfWYvbuynpfogLrt3cXA-9_aA@mail.gmail.com> On Fri, 4 Dec 2020, Geert Uytterhoeven wrote: > Hi Finn, > > On Fri, Nov 20, 2020 at 5:54 AM Finn Thain <fthain@telegraphics.com.au> wrote: > > The behaviour of the IOP firmware is not well documented but we do know > > that IOP message reply data can be used to issue new ADB commands. > > Use the message reply to better control autopoll behaviour by sending > > a Talk Register 0 command after every ADB response, not unlike the > > algorithm in the via-macii driver. This poll command is addressed to > > that device which last received a Talk command (explicit or otherwise). > > > > Cc: Joshua Thompson <funaho@jurai.org> > > Fixes: fa3b5a9929fc ("macintosh/adb-iop: Implement idle -> sending state transition") > > WARNING: Unknown commit id 'fa3b5a9929fc', maybe rebased or not pulled? > > 32226e817043? > Yes, that's the one. I accidentally gave a commit id from one of my backport branches. > > Tested-by: Stan Johnson <userm57@yahoo.com> > > Signed-off-by: Finn Thain <fthain@telegraphics.com.au> > > Thanks, will queue in the m68k for-v5.11 branch. > Thanks. > Gr{oetje,eeting}s, > > Geert > >
WARNING: multiple messages have this Message-ID (diff)
From: Finn Thain <fthain@telegraphics.com.au> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Joshua Thompson <funaho@jurai.org> Subject: Re: [PATCH] macintosh/adb-iop: Send correct poll command Date: Sat, 5 Dec 2020 14:10:21 +1100 (AEDT) [thread overview] Message-ID: <alpine.LNX.2.23.453.2012051340490.6@nippy.intranet> (raw) In-Reply-To: <CAMuHMdVYf83+y1aUR6HqCgr-CLfWYvbuynpfogLrt3cXA-9_aA@mail.gmail.com> On Fri, 4 Dec 2020, Geert Uytterhoeven wrote: > Hi Finn, > > On Fri, Nov 20, 2020 at 5:54 AM Finn Thain <fthain@telegraphics.com.au> wrote: > > The behaviour of the IOP firmware is not well documented but we do know > > that IOP message reply data can be used to issue new ADB commands. > > Use the message reply to better control autopoll behaviour by sending > > a Talk Register 0 command after every ADB response, not unlike the > > algorithm in the via-macii driver. This poll command is addressed to > > that device which last received a Talk command (explicit or otherwise). > > > > Cc: Joshua Thompson <funaho@jurai.org> > > Fixes: fa3b5a9929fc ("macintosh/adb-iop: Implement idle -> sending state transition") > > WARNING: Unknown commit id 'fa3b5a9929fc', maybe rebased or not pulled? > > 32226e817043? > Yes, that's the one. I accidentally gave a commit id from one of my backport branches. > > Tested-by: Stan Johnson <userm57@yahoo.com> > > Signed-off-by: Finn Thain <fthain@telegraphics.com.au> > > Thanks, will queue in the m68k for-v5.11 branch. > Thanks. > Gr{oetje,eeting}s, > > Geert > >
next prev parent reply other threads:[~2020-12-05 3:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-20 4:39 [PATCH] macintosh/adb-iop: Send correct poll command Finn Thain 2020-11-20 4:39 ` Finn Thain 2020-12-04 10:03 ` Geert Uytterhoeven 2020-12-04 10:03 ` Geert Uytterhoeven 2020-12-05 3:10 ` Finn Thain [this message] 2020-12-05 3:10 ` Finn Thain
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=alpine.LNX.2.23.453.2012051340490.6@nippy.intranet \ --to=fthain@telegraphics.com.au \ --cc=benh@kernel.crashing.org \ --cc=funaho@jurai.org \ --cc=geert@linux-m68k.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mpe@ellerman.id.au \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.