linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] video: Add support for the Solomon SSD1307 OLED Controller
Date: Tue, 25 Sep 2012 12:06:58 +0200	[thread overview]
Message-ID: <50618242.2070302@free-electrons.com> (raw)
In-Reply-To: <505C73D1.7030800@free-electrons.com>

Hello Florian,

Le 21/09/2012 16:04, Maxime Ripard a ?crit :
> Le 20/09/2012 18:33, Maxime Ripard a ?crit :
>> This patch adds support for the Solomon SSD1307 OLED
>> controller found on the Crystalfontz CFA10036 board.
>>
>> This controller can drive a display with a resolution up
>> to 128x39 and can operate over I2C or SPI.
>>
>> The current driver has only been tested on the CFA-10036,
>> that is using this controller over I2C to driver a 96x16
>> OLED screen.
>>
>> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>> Cc: Brian Lilly <brian@crystalfontz.com>
> 
> Would you consider merging this patch or review it?
> It has been around for quite some time now and has not received any
> comments for at least the 2 last versions, so I guess there is not much
> left holding it back (unless, of course, if you have some comments to
> address), and I really would like to have it in 3.7.

I guess we missed the 3.7 merge here. That's no big deal, but I sent the
patch series on a regular basis, starting 07/17 (sent new versions on
07/31, 08/23, 09/05 and 09/20), addressed all the issues that were
raised, and never got any feedback from you, either positive or
negative. The patches affecting the MX28 device trees have already been
merged by Shawn Guo into its tree, so only the driver and the bindings
remain to be merged. So I'm kind of lost on what should I do here?

Is it because I have an obviously broken driver or you don't have enough
time, or you don't want to merge drivers for such type of low resolution
controllers, or any other reason?

Thanks for your answer,
Maxime


-- 
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-09-25 10:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 16:33 [PATCHv5 0/2] Add support for the OLED in the CFA10036 Maxime Ripard
2012-09-20 16:33 ` [PATCH 1/2] video: Add support for the Solomon SSD1307 OLED Controller Maxime Ripard
2012-09-21 14:04   ` Maxime Ripard
2012-09-25 10:06     ` Maxime Ripard [this message]
2012-10-11  1:06       ` Florian Tobias Schandinat
2012-10-18 15:11         ` Maxime Ripard
2012-09-20 16:33 ` [PATCH 2/2] ARM: dts: mxs: add oled support for the cfa-10036 Maxime Ripard
  -- strict thread matches above, loose matches on Subject: below --
2012-10-31  9:12 [PATCHv6 0/2] Add support for the OLED in the CFA10036 Maxime Ripard
2012-10-31  9:12 ` [PATCH 1/2] video: Add support for the Solomon SSD1307 OLED Controller Maxime Ripard
2012-09-05  9:35 [PATCHv4] Add support for the OLED in the CFA10036 Maxime Ripard
2012-09-05  9:35 ` [PATCH 1/2] video: Add support for the Solomon SSD1307 OLED Controller Maxime Ripard

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=50618242.2070302@free-electrons.com \
    --to=maxime.ripard@free-electrons.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).