From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
GTA04 owners <gta04-owner@goldelico.com>,
"Dr. H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH] OMAPDSS: restore "name" sysfs entry.
Date: Tue, 24 Feb 2015 10:40:32 +0000 [thread overview]
Message-ID: <54EC5520.1020105@ti.com> (raw)
In-Reply-To: <20150224203706.1eafa129@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Hi,
On 24/02/15 11:37, NeilBrown wrote:
>
>
> commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
> OMAPDSS: rename display-sysfs 'name' entry
>
> broke the xorg X server on my device as it couldn't find the display
> any more. It needs the 'name' file and now there isn't one.
>
> That commit claims that 'name' is not compatible with i2c or spi.
> i2c does register it own 'name' file, but spi does not, hence my
> problem - I have an spi display.
>
> So create a special case for i2c: add the name attribute for non-i2c
> devices.
What X driver is that? What's it doing with the display name? Is it just
using the display name to show something for the user, and the returned
value can be essentially any string?
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-24 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 9:37 [PATCH] OMAPDSS: restore "name" sysfs entry NeilBrown
2015-02-24 10:40 ` Tomi Valkeinen [this message]
2015-02-24 20:31 ` NeilBrown
2015-02-24 20:48 ` Tony Lindgren
2015-02-25 7:04 ` Tomi Valkeinen
2015-02-25 8:49 ` Tomi Valkeinen
2015-02-25 9:20 ` NeilBrown
2015-02-25 9:32 ` Tomi Valkeinen
2015-02-25 22:33 ` NeilBrown
2015-02-24 17:08 ` Dr. H. Nikolaus Schaller
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=54EC5520.1020105@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=gta04-owner@goldelico.com \
--cc=hns@goldelico.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=neilb@suse.de \
/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).