linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH] wm97xx-core: Report a phys for WM97xx touchscreens
Date: Thu, 22 May 2008 16:01:19 +0100	[thread overview]
Message-ID: <20080522150119.GA25172@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20080522093759.ZZRA012@mailhub.coreip.homeip.net>

On Thu, May 22, 2008 at 09:41:48AM -0400, Dmitry Torokhov wrote:
> On Thu, May 22, 2008 at 12:35:06PM +0100, Mark Brown wrote:

> > phys is displayed in various diagnostic output so ensure that it is set
> > to something sensible.

> Phys is used to describe the physical connection of a device that is
> ideally not changing between reboots so having it set up based on
> device's bus_id is not a best option I think.

It didn't seem terribly wonderful to me either but I saw that some other
drivers were doing the same thing so I assumed it was idiomatic.  A
quick survey of devices on my laptop suggets that it's getting filled in
with USB bus IDs for some devices.

For a WM97xx device it should actually be OK almost all the time - AC97
bus identifiers are fixed in hardware, there would only be a problem if
additional AC97 buses are added which is relatively unlikely, especially
in the embedded applications where the WM97xx devices get used.
However, if it's supposed to be OK to leave this null then that would be
better.

> What tools besides evbug use phys? They probably should display both
> phys and sysfs paths (I will be changing evbug soon).

It was actually evbug that prompted this - it prints a rather alarming
'Connected device: "foo", NULL' when phys is left empty.

      reply	other threads:[~2008-05-22 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 11:35 [PATCH] wm97xx-core: Report a phys for WM97xx touchscreens Mark Brown
2008-05-22 13:41 ` Dmitry Torokhov
2008-05-22 15:01   ` Mark Brown [this message]

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=20080522150119.GA25172@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).