From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
Michael Hennerich <michael.hennerich@analog.com>,
linux-input@vger.kernel.org
Subject: Re: [Uclinux-dist-devel] [PATCH 2/2] input/joystick: new Blackfin rotary input driver
Date: Thu, 23 Jul 2009 01:13:04 -0700 [thread overview]
Message-ID: <20090723081304.GD3997@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <8bd0f97a0907230046t108e9ff1y747caf16aadc6de4@mail.gmail.com>
On Thu, Jul 23, 2009 at 03:46:18AM -0400, Mike Frysinger wrote:
> On Thu, Jul 23, 2009 at 03:25, Dmitry Torokhov wrote:
> > On Thu, Jul 23, 2009 at 02:46:11AM -0400, Mike Frysinger wrote:
> >> On Thu, Jul 23, 2009 at 00:43, Dmitry Torokhov wrote:
> >> > On Tue, Jul 14, 2009 at 01:33:47PM -0400, Mike Frysinger wrote:
> >> >> +struct platform_driver bfin_rotary_device_driver = {
> >> >> + .probe = bfin_rotary_probe,
> >> >> + .remove = __devexit_p(bfin_rotary_remove),
> >> >> + .suspend = bfin_rotary_suspend,
> >> >> + .resume = bfin_rotary_resume,
> >> >
> >> > Need to use dev_pm_ops so platform code won;t yell at us.
> >>
> >> looks like something new post 2.6.30 ... guess i'll have to keep this
> >> in mind for migrating drivers when 2.6.31 comes out
> >>
> >> > I also think that this driver should too live in drivers/input/misc so I
> >> > moved it there. I did a bit of reshuffling in the patch, could you
> >> > please give it a try and if it still works I'll apply to the 'next'
> >> > branch.
> >>
> >> could you toss like a standard dev_info("initialized") into the end of
> >> bfin_rotary_probe ? otherwise, builds and works fine for me with
> >> 2.6.31-rc4. thanks!
> >
> > Don't you find the boot to be too noisy? The input core already
> > prints a message when a new input device is registered...
>
> you're right. when i was testing, i didnt update my board resources
> and so was seeing no output, so i added the dev_info() while also
> fixing the resources. didnt notice the additional input core output.
> current behavior is fine then, thanks!
Cool. Then I'll also zap the similar message in bf54x-keys while applying
your other patch.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-07-23 8:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 17:33 [PATCH 1/2] input/joystick: new AD7142 driver Mike Frysinger
2009-07-14 17:33 ` [PATCH 2/2] input/joystick: new Blackfin rotary input driver Mike Frysinger
2009-07-23 4:43 ` Dmitry Torokhov
2009-07-23 6:46 ` [Uclinux-dist-devel] " Mike Frysinger
2009-07-23 7:25 ` Dmitry Torokhov
2009-07-23 7:46 ` Mike Frysinger
2009-07-23 8:13 ` Dmitry Torokhov [this message]
2009-07-14 18:03 ` [PATCH 1/2] input/joystick: new AD7142 driver Dmitry Torokhov
[not found] ` <20090714180309.GC14661-wUGeVx6es1+Q2O5dskk9LyLysJ1jNyTM@public.gmane.org>
2009-07-14 22:56 ` Mike Frysinger
2009-07-15 15:50 ` Mike Frysinger
2009-07-15 3:42 ` [Uclinux-dist-devel] [PATCH 1/2] input/joystick: new AD7142driver Robin Getz
2009-07-15 10:01 ` Song, Barry
2009-07-15 15:29 ` Dmitry Torokhov
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=20090723081304.GD3997@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier.adi@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;
as well as URLs for NNTP newsgroup(s).