From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: linux-fbdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Subject: [PATCH 0/3] viafb auxiliary device support
Date: Tue, 14 Feb 2012 06:35:00 +0000 [thread overview]
Message-ID: <cover.1329200232.git.FlorianSchandinat@gmx.de> (raw)
Hi all,
this patch series aims to add infrastructure to viafb to support
devices that are connected via I2C. Even before these patches viafb
had support for some of these but no structure, instead ranging from
a single file for a device to various places in the code writing to
such devices, probably even sometimes without knowing that it is
talking to the correct device.
This patch series adds just the infrastructure to add such devices
and a few stub driver which print the name of the chips, if detected.
Even this is quite useful for debugging or recruiting testers. The
long term goal is to move all existing support for such devices in
those drivers and extend them to whatever is required.
The chip detection aside the only user visible change is that if no
viafb_mode/viafb_mode1 is given on startup the initial resolution
is derived from EDID data, if present for the desired configuration.
Best regards,
Florian Tobias Schandinat
Florian Tobias Schandinat (3):
viafb: add auxiliary device management infrastructure
viafb: fix I2C emulation on GPIO ports
viafb: add initial EDID support
drivers/video/via/Makefile | 5 ++-
drivers/video/via/via_aux.c | 88 ++++++++++++++++++++++++++++++++
drivers/video/via/via_aux.h | 93 ++++++++++++++++++++++++++++++++++
drivers/video/via/via_aux_ch7301.c | 50 ++++++++++++++++++
drivers/video/via/via_aux_edid.c | 97 ++++++++++++++++++++++++++++++++++++
drivers/video/via/via_aux_sii164.c | 54 ++++++++++++++++++++
drivers/video/via/via_aux_vt1621.c | 44 ++++++++++++++++
drivers/video/via/via_aux_vt1622.c | 50 ++++++++++++++++++
drivers/video/via/via_aux_vt1625.c | 50 ++++++++++++++++++
drivers/video/via/via_aux_vt1631.c | 46 +++++++++++++++++
drivers/video/via/via_aux_vt1632.c | 54 ++++++++++++++++++++
drivers/video/via/via_aux_vt1636.c | 46 +++++++++++++++++
drivers/video/via/via_i2c.c | 10 +++-
drivers/video/via/viafbdev.c | 53 +++++++++++++++++---
drivers/video/via/viafbdev.h | 6 ++
15 files changed, 736 insertions(+), 10 deletions(-)
create mode 100644 drivers/video/via/via_aux.c
create mode 100644 drivers/video/via/via_aux.h
create mode 100644 drivers/video/via/via_aux_ch7301.c
create mode 100644 drivers/video/via/via_aux_edid.c
create mode 100644 drivers/video/via/via_aux_sii164.c
create mode 100644 drivers/video/via/via_aux_vt1621.c
create mode 100644 drivers/video/via/via_aux_vt1622.c
create mode 100644 drivers/video/via/via_aux_vt1625.c
create mode 100644 drivers/video/via/via_aux_vt1631.c
create mode 100644 drivers/video/via/via_aux_vt1632.c
create mode 100644 drivers/video/via/via_aux_vt1636.c
--
1.7.9
next reply other threads:[~2012-02-14 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 6:35 Florian Tobias Schandinat [this message]
2012-02-14 6:35 ` [PATCH 1/3] viafb: add auxiliary device management infrastructure Florian Tobias Schandinat
2012-02-14 6:35 ` [PATCH 2/3] viafb: fix I2C emulation on GPIO ports Florian Tobias Schandinat
2012-02-14 6:35 ` [PATCH 3/3] viafb: add initial EDID support Florian Tobias Schandinat
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=cover.1329200232.git.FlorianSchandinat@gmx.de \
--to=florianschandinat@gmx.de \
--cc=linux-fbdev@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).