From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: NeilBrown <neilb@suse.de>
Cc: "Dr. H. Nikolaus Schaller" <hns@goldelico.com>,
linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
GTA04 owners <gta04-owner@goldelico.com>
Subject: Re: [PATCH] OMAPDSS: restore "name" sysfs entry.
Date: Wed, 25 Feb 2015 09:32:18 +0000 [thread overview]
Message-ID: <54ED96A2.6080300@ti.com> (raw)
In-Reply-To: <20150225202042.2adaea4f@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]
On 25/02/15 11:20, NeilBrown wrote:
> Tested-by: NeilBrown <neilb@suse.de>
>
> Before the patch:
>
> # ls -l /sys/devices/platform/omapdss/display0
> lrwxrwxrwx 1 root root 0 Feb 8 12:57 /sys/devices/platform/omapdss/display0 -> ../spi_lcd/spi_master/spi32766/spi32766.0
>
> After the patch:
>
> # ls -l /sys/devices/platform/omapdss/display0
> total 0
> -r--r--r-- 1 root root 4096 Feb 8 13:37 display_name
> -rw-r--r-- 1 root root 4096 Feb 8 13:37 enabled
> -rw-r--r-- 1 root root 4096 Feb 8 13:37 mirror
> -r--r--r-- 1 root root 4096 Feb 8 13:37 name
> -rw-r--r-- 1 root root 4096 Feb 8 13:37 rotate
> -rw-r--r-- 1 root root 4096 Feb 8 13:37 tear_elim
> -rw-r--r-- 1 root root 4096 Feb 8 13:37 timings
> -rw-r--r-- 1 root root 4096 Feb 8 13:37 wss
>
>
> So as you say it creates a directory just for the display0 device, and that
> has the 'name' that we want.
I think this was something similar than how the sysfs files were set up
originally for omapdss. If I remember right, we didn't have proper
devices for the displays then. Things have evolved quite a bit since then.
There's a small chance of this patch breaking things, of course... If
someone accessed those display sysfs files via the display device
(../spi_lcd/spi_master/spi32766/spi32766.0), the files are now gone.
But I think (hope...) they are always accessed via the omapdss's
displayX directories.
> This works for me, and it seems to me to be a better fit to the general
> structure of /sys/devices - symlinks within /sys/devices are a substantial
> minority, other than 'subsystem', 'device', 'driver' and 'bdi' which have
> very generic meanings.
>
> I guess I'm a little surprised that there doesn't seem to be any linkage from
> the display0 to the spi device. Maybe that isn't important.
Yep, I don't think so. In any case, all this is to be deprecated, and as
soon as omapdrm driver works reliably that should be the driver to use.
So of course we need to keep omapfb working for the years to come, but
I'd rather not add any new sysfs files for a soon deprecated driver.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-25 9:32 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
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 [this message]
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=54ED96A2.6080300@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).