From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Cercueil <paul@crapouillou.net>
Cc: Noralf T <noralf@tronnes.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v1 2/5] pardata: new bus for parallel data access
Date: Mon, 20 Jan 2020 19:48:04 +0100 [thread overview]
Message-ID: <20200120184804.GA7630@ravnborg.org> (raw)
In-Reply-To: <CAMuHMdVP4UwGYuNcOphPO9F2pSCaHS1j-ODxYrv_LNOoo_4coA@mail.gmail.com>
Hi Geert.
On Mon, Jan 20, 2020 at 11:10:37AM +0100, Geert Uytterhoeven wrote:
> Hi Sam,
>
> (stumbled on this accidentally)
>
> On Thu, Aug 2, 2018 at 9:46 PM Sam Ravnborg <sam@ravnborg.org> wrote:
> > The pardata supports implement a simple bus for devices
> > that are connected using a parallel bus driven by GPIOs.
> > The is often used in combination with simple displays
> > that is often seen in older embedded designs.
> > There is a demand for this support also in the linux
> > kernel for HW designs that uses these kind of displays.
> >
> > The pardata bus uses a platfrom_driver that when probed
> > creates devices for all child nodes in the DT,
> > which are then supposed to be handled by pardata_drivers.
> >
> > Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
>
> > --- /dev/null
> > +++ b/Documentation/driver-api/pardata.rst
> > @@ -0,0 +1,60 @@
> > +.. SPDX-License-Identifier: GPL-2.0
> > +
> > +=========================
> > +Parallel Data Bus/Drivers
> > +=========================
> > +
> > +Displays may be connected using a simple parallel bus.
> > +This is often seen in embedded systems with a simple MCU, but is also
> > +used in Linux based systems to a small extent.
> > +
> > +The bus looks like this:
> > +
> > +.. code-block:: none
> > +
> > + ----+
> > + | DB0-DB7 or DB4-DB7 +----
> > + ===/========================
> > + | E - enable | D
> > + ---------------------------- I
> > + C | Reset | S
> > + P ---------------------------- P
> > + U | Read/Write (one or two) | L
> > + ---------------------------- A
> > + | RS - instruction/data | Y
> > + ----------------------------
> > + | +----
> > + ----+
>
> Oh, cool! Looks like this can be used by the hd44780 driver.
>
> Documentation/devicetree/bindings/auxdisplay/hit,hd44780.txt
> drivers/auxdisplay/hd44780.c
This patchset was from a time when I knew next to nothing about DRM.
Now I am just confused on a different level :-)
It is on my TODO list to make a mipi-dbi driver that in the future
replaces the auxdisplay driver for hd44780.
But that TODO list have a growing tendency.
It seems that pretending to be co-maintainer on panel/ stuff
alone can take up most of my DRM time.
I hope Paul will contribute the i8080 support to drm_mipi_dbi,
at least he mentioned he planned to work on this.
Sam
next prev parent reply other threads:[~2020-01-20 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 19:39 [RFC PATCH v1 0/5] Add pardata bus + tinydrm driver Sam Ravnborg
2018-08-02 19:45 ` [PATCH v1 1/5] dt-bindings: add parallel data bus (pardata) Sam Ravnborg
2018-08-02 19:45 ` [PATCH v1 2/5] pardata: new bus for parallel data access Sam Ravnborg
2018-08-07 16:40 ` Noralf Trønnes
2018-08-08 8:24 ` Sam Ravnborg
2018-08-08 16:22 ` Noralf Trønnes
2020-01-20 10:10 ` Geert Uytterhoeven
2020-01-20 18:48 ` Sam Ravnborg [this message]
2020-01-20 19:12 ` Geert Uytterhoeven
2020-01-20 19:23 ` Sam Ravnborg
2018-08-02 19:45 ` [PATCH v1 3/5] tinydrm: add support for parallel data displays Sam Ravnborg
2018-08-02 19:45 ` [PATCH v1 4/5] dt-bindings: add winstar,wg160160 display bindings Sam Ravnborg
2018-08-02 19:45 ` [PATCH v1 5/5] tinydrm: add winstar wg160160 driver Sam Ravnborg
2018-08-06 9:15 ` Dan Carpenter
2018-08-06 12:07 ` Sam Ravnborg
2018-08-07 17:35 ` Noralf Trønnes
2018-08-08 8:32 ` Sam Ravnborg
2018-08-08 16:31 ` Noralf Trønnes
2018-08-02 19:46 ` [RFC PATCH v1 0/5] Add pardata bus + tinydrm driver Miguel Ojeda
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=20200120184804.GA7630@ravnborg.org \
--to=sam@ravnborg.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=paul@crapouillou.net \
/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