qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Filip Navara <filip.navara@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 01/14] GPIO rotary encoder implementation
Date: Sat, 18 Jul 2009 12:00:00 +0300	[thread overview]
Message-ID: <f43fc5580907180200w51098b77q7079a43f07024cbd@mail.gmail.com> (raw)
In-Reply-To: <5b31733c0907180152x31e6a6c4g2b15b6ad2b9d3007@mail.gmail.com>

On Sat, Jul 18, 2009 at 11:52 AM, Filip Navara<filip.navara@gmail.com> wrote:
> On Wed, Jul 15, 2009 at 5:38 PM, Filip Navara<filip.navara@gmail.com> wrote:
>> On Wed, Jul 15, 2009 at 5:33 PM, Blue Swirl<blauwirbel@gmail.com> wrote:
>>> On Wed, 15 Jul 09 16:52:12 Central Europe Standard Time, Filip Navara
>>> <filip.navara@gmail.com> wrote:
>>>> This patch introduces an emulation of the rotary encoder that could be connected
>>>>  to GPIO controller.
>>>
>>> How about reset handling (qemu_register_reset)?
>>>
>>
>> Good point, it was on my TODO list, but I never implemented it. All
>> the devices currently lack it. I'll include it in next version.
>
> On second thought the GPIO devices don't need reset handling. In real
> hardware the rotary encoder is not affected by reset, so why would it
> be affected in QEMU? Unfortunately to get that working correctly the
> late_init callbacks, proposed in the devtree patches, are needed.

There is still internal state (for example s->extension) that may need reset.

  reply	other threads:[~2009-07-18  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 14:52 [Qemu-devel] [PATCH 01/14] GPIO rotary encoder implementation Filip Navara
2009-07-15 15:33 ` Blue Swirl
2009-07-15 15:38   ` Filip Navara
2009-07-18  8:52     ` Filip Navara
2009-07-18  9:00       ` Blue Swirl [this message]
2009-07-18 15:26         ` Filip Navara

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=f43fc5580907180200w51098b77q7079a43f07024cbd@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=filip.navara@gmail.com \
    --cc=qemu-devel@nongnu.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).