linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.ml.walleij@gmail.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: driver for the character LCD found in ARM refdesigns
Date: Wed, 7 Jul 2010 14:32:43 +0200	[thread overview]
Message-ID: <AANLkTimdl0q5S3Vhog6WN1L0oy82yVkYkmAV_SCK5N9S@mail.gmail.com> (raw)
In-Reply-To: <F01D8B85CFF58440B2A13965FBA90CA42DA39B5220@GEORGE.Emea.Arm.com>

2010/7/7 Colin Tuckley <Colin.Tuckley@arm.com>:

>> The 4bit mode is the only one that seems to work. I tried putting
>> the display into 8bit mode and failed miserably.
>
> I've had a check with the hardware guys. Our self-test software uses the
> 4-bit mode, the 8-bit mode is untested.

OK I can make another round. I modeled the 4bit mode after
the ROM selftest actually.

The phenomenon is like commands go through in 8bit but not
characters, so whatever you write into CHAR_DAT only the 4 higher
bits go through, often with the effect of letters like "@@@@@" in
the display (if you write something with big letters).

>> The IRQ is stated in the reference manual as "don't use" because it
>> is "reserved for future use" but I implemented it anyway.
>
> The answer seems to be that "future use" means "for an OS".

Aha OK, then it's all mine! :-)

Yours,
Linus Walleij

  reply	other threads:[~2010-07-07 12:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 15:21 [PATCH 1/3] ARM: driver for the character LCD found in ARM refdesigns Linus Walleij
2010-07-07  8:47 ` Colin Tuckley
2010-07-07 12:32   ` Linus Walleij [this message]
2010-07-15 10:22 ` Russell King - ARM Linux
2010-07-15 11:49   ` Linus Walleij
2010-07-15 11:53     ` Russell King - ARM Linux
2010-07-15 16:32       ` H Hartley Sweeten
2010-07-16  9:19     ` Arnd Bergmann
2010-07-16  9:25       ` Russell King - ARM Linux

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=AANLkTimdl0q5S3Vhog6WN1L0oy82yVkYkmAV_SCK5N9S@mail.gmail.com \
    --to=linus.ml.walleij@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).