mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jakob Bornecrantz" <wallbraker@gmail.com>
To: "Jesse Barnes" <jbarnes@virtuousgeek.org>
Cc: dri-devel@lists.sourceforge.net,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: DRM modesetting & sysfs
Date: Wed, 9 Apr 2008 10:57:12 +0200	[thread overview]
Message-ID: <427ca1a20804090157t4fa1bbcei27d3bbea085aa9c3@mail.gmail.com> (raw)
In-Reply-To: <200804081317.43712.jbarnes@virtuousgeek.org>

On Tue, Apr 8, 2008 at 10:17 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>
>  I just pushed a few changes updating the DRM modesetting sysfs support, both
>  for debugging and eventual HAL friendliness.
>
>  So far, the support is limited to describing outputs and generating hotplug
>  events.  A typical "card0" directory now looks like this:
>
>  .
>  |-- card0-DAC-1
>  |   |-- device -> ../../../../../../devices/pci0000:00/0000:00:02.0/drm/card0
>  |   |-- dpms
>  |   |-- edid
>  |   |-- modes
>  |   |-- power
>  |   |   `-- wakeup
>  |   |-- status
>  |   |-- subsystem -> ../../../../../../class/drm
>  |   `-- uevent
>  |-- card0-LVDS-1
>  |   |-- device -> ../../../../../../devices/pci0000:00/0000:00:02.0/drm/card0
>  |   |-- dpms
>  |   |-- edid
>  |   |-- modes
>  |   |-- power
>  |   |   `-- wakeup
>  |   |-- status
>  |   |-- subsystem -> ../../../../../../class/drm
>  |   `-- uevent
>  |-- dev
>  |-- device -> ../../../../../devices/pci0000:00/0000:00:02.0
>  |-- dri_library_name
>  |-- power
>  |   `-- wakeup
>  |-- subsystem -> ../../../../../class/drm
>  `-- uevent
>
>  Each output is listed, prefixed with its associated card number to
>  disambiguate it at the top level /sys/class/drm directory (where it also has
>  some symlinks).  Currently, only DPMS, EDID, mode list and connection status
>  properties are exported, but we could list more as needed.  You can
>  use 'udevmonitor --env' to look for hotplug events; you should see several at
>  load time, and presumably some at connection hotplug time (though I haven't
>  gotten that working yet, any ideas Jakob?).
>

I was going to suggest that you plug it into the hotplug_stage_two
function but it looks like you have already done that. Things might be
routed differently now then since the last time I looked at the code,
are you sure that stage_two is being run?

>  Any thoughts on the interface?  Anything in particular people would like to
>  see?
>

Looks good, can you write to dpms, that is turn a monitor on and of,
that would be slightly cool but not overly useful. On the whole I
think exporting properties are fine, but I don't think setting modes
and crtc's are to be done in sysfs. However it is entirely possible.

>  Thanks,
>  Jesse

Cheers Jakob.

  reply	other threads:[~2008-04-09  8:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 20:17 Jesse Barnes
2008-04-09  8:57 ` Jakob Bornecrantz [this message]
2008-04-09 15:17   ` Jesse Barnes
2008-04-09 16:15     ` Alan Hourihane
2008-04-09 16:34       ` Jesse Barnes
2008-04-09 17:23         ` Alan Hourihane
2008-04-09 17:39           ` Jesse Barnes
2008-04-09 18:12             ` Jesse Barnes

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=427ca1a20804090157t4fa1bbcei27d3bbea085aa9c3@mail.gmail.com \
    --to=wallbraker@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jbarnes@virtuousgeek.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

all inboxes | Powered by JetHome®