From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Fbdev development list" <linux-fbdev@vger.kernel.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Maxime Ripard" <maxime@cerno.tech>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 3/4] drm/tiny: Add driver for Solomon SSD1307 OLED displays
Date: Wed, 2 Feb 2022 09:29:27 +0100 [thread overview]
Message-ID: <042a42a9-0446-1b29-beae-493882cc18ca@redhat.com> (raw)
In-Reply-To: <946f8fbb-cd64-12d0-ecd9-13af18a00590@suse.de>
Hello Thomas,
On 2/2/22 09:23, Thomas Zimmermann wrote:
[snip]
>
> Thanks to both of you. I was asking because I found the code to be
> repetitive and it's not clear that these 3 statements belong together.
>
> I'd like to suggest to add a function
>
> ssd1307_write_cmds(client, len, const u8 *cmds)
>
> that loops through cmds and sends the values one by one. A call would
> look like this:
>
> const u8 set_col_range[] = {
> SSD1307_SET_COL_RANGE,
> col_start,
> col_end
> };
>
> ssd1307_write_cmds(client, ARRAY_SIZE(set_col_range), set_col_range);
>
> AND/OR
>
> You could have functions that take a command with arguments; either as
> va_args or with one function per number of arguments. Or you could
> combine all these somehow.
>
Thanks for the suggestion, that a makes sense to me. I'll look into
it when working on v2. Probably during the weekend.
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
prev parent reply other threads:[~2022-02-02 8:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 20:29 [PATCH 3/4] drm/tiny: Add driver for Solomon SSD1307 OLED displays Javier Martinez Canillas
[not found] ` <YfhVBtv1UIA7bJja@ravnborg.org>
2022-02-01 0:14 ` Javier Martinez Canillas
2022-02-01 9:44 ` Andy Shevchenko
2022-02-01 11:45 ` Javier Martinez Canillas
2022-02-01 14:02 ` Andy Shevchenko
2022-02-01 15:10 ` Javier Martinez Canillas
2022-02-01 9:41 ` Andy Shevchenko
2022-02-01 11:40 ` Javier Martinez Canillas
2022-02-01 9:33 ` Thomas Zimmermann
2022-02-01 9:48 ` Andy Shevchenko
2022-02-01 13:01 ` Javier Martinez Canillas
2022-02-01 14:05 ` Geert Uytterhoeven
2022-02-01 14:36 ` Javier Martinez Canillas
2022-02-02 8:23 ` Thomas Zimmermann
2022-02-02 8:29 ` Javier Martinez Canillas [this message]
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=042a42a9-0446-1b29-beae-493882cc18ca@redhat.com \
--to=javierm@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=noralf@tronnes.org \
--cc=tzimmermann@suse.de \
/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).