From: "Ville Syrjälä" <ville.syrjala@nokia.com>
To: ext Paul Mundt <lethal@linux-sh.org>
Cc: "Valkeinen Tomi (Nokia-D/Helsinki)" <Tomi.Valkeinen@nokia.com>,
ext Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/4] fbdev: add a MIPI DSI header
Date: Wed, 19 May 2010 15:39:50 +0000 [thread overview]
Message-ID: <20100519153950.GK30960@nokia.com> (raw)
In-Reply-To: <20100519150057.GA16082@linux-sh.org>
On Wed, May 19, 2010 at 05:00:58PM +0200, ext Paul Mundt wrote:
> On Wed, May 19, 2010 at 05:27:32PM +0300, Ville Syrj?l? wrote:
> > On Wed, May 19, 2010 at 10:21:48AM +0200, Valkeinen Tomi (Nokia-D/Helsinki) wrote:
> > > I think a simple solution would be to just use defines, and have
> > > functions that take the command as u8. That's what the OMAP DSI driver
> > > does. If you have better ideas, please share =).
> >
> > I find enums easier on the eye than defines. Less irrelevant junk on
> > each line. There's no reason you can't pass enum values as u8. But in
> > that case giving the enum a name doesn't really make sense.
> >
> enums are cleaner for these cases, but you also have the case where the
> enum type itself is variable size depending on the ABI being used. If
> the type in question isn't being packed in to a user-visible data
> structure then this will never matter, but it does help to be a bit
> careful here regardless. Many people were bitten by this in the ARM
> OABI -> EABI conversion, while other architectures generally managed to
> get it right from the onset.
Yeah using the enum type in ABI is a bad idea since actual type is
implementation defined. But if you don't give the enum an identifier
there's no way to even accidentally use it as a type.
--
Ville Syrjälä
next prev parent reply other threads:[~2010-05-19 15:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 9:07 [PATCH 0/4] MIPI DSI support for SH-mobile, common header, switch Guennadi Liakhovetski
2010-05-07 9:07 ` [PATCH 1/4] fbdev: add a MIPI DSI header Guennadi Liakhovetski
2010-05-19 4:42 ` Damian
2010-05-19 7:49 ` Tomi Valkeinen
2010-05-19 8:08 ` Guennadi Liakhovetski
2010-05-19 8:21 ` Tomi Valkeinen
2010-05-19 14:27 ` Ville Syrjälä
2010-05-19 15:00 ` Paul Mundt
2010-05-19 15:39 ` Ville Syrjälä [this message]
2010-05-20 8:07 ` Guennadi Liakhovetski
2010-05-20 8:32 ` Tomi Valkeinen
2010-05-20 8:54 ` Felipe Balbi
2010-05-20 9:02 ` Guennadi Liakhovetski
2010-05-20 11:03 ` Guennadi Liakhovetski
2010-05-20 14:20 ` Tomi Valkeinen
2010-05-07 9:07 ` [PATCH 2/4] sh-mobile: add support for displays, connected over the Guennadi Liakhovetski
2010-05-19 4:43 ` [PATCH 2/4] sh-mobile: add support for displays, connected over Damian
2010-05-07 9:07 ` [PATCH 3/4] ARM: add framebuffer support for ap4evb Guennadi Liakhovetski
2010-05-07 14:45 ` [PATCH 3/4 v2] " Guennadi Liakhovetski
2010-05-10 0:11 ` Kuninori Morimoto
2010-05-10 6:12 ` Guennadi Liakhovetski
2010-05-10 9:37 ` Kuninori Morimoto
2010-05-19 4:36 ` Damian
2010-05-19 4:47 ` [PATCH 3/4] " Damian
2010-05-07 9:07 ` [PATCH 4/4] video: switch OMAP LCD MIPI driver to use the common Guennadi Liakhovetski
2010-05-07 10:05 ` [PATCH 2.5/4] ARM: add LCDC and MIPI DSI-Tx clock definitions to Guennadi Liakhovetski
2010-05-07 10:49 ` [PATCH 1.5/4] sh: add a YUV422 output data format, that is also Guennadi Liakhovetski
2010-05-19 4:44 ` Damian
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=20100519153950.GK30960@nokia.com \
--to=ville.syrjala@nokia.com \
--cc=Tomi.Valkeinen@nokia.com \
--cc=g.liakhovetski@gmx.de \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).