From: sshtylyov@mvista.com (Sergei Shtylyov) Date: Tue, 23 Nov 2010 19:02:14 +0300 Subject: [PATCH 1/4] FB: added a structure for CPU interface to linux/fb.h In-Reply-To: <1290496504-4867-1-git-send-email-inki.dae@samsung.com> References: <> <1290496504-4867-1-git-send-email-inki.dae@samsung.com> Message-ID: <4CEBE586.8010007@ru.mvista.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hello. Inki Dae wrote: > RGB or CPU interfaces could be used as display mode but framebuffer > framework doesn't consider CPU interface so I added this structure > because fb_cpumode structure could be used commonly. > Signed-off-by: Inki Dae > Signed-off-by: Kyungmin Park > --- > include/linux/fb.h | 12 ++++++++++++ > 1 files changed, 12 insertions(+), 0 deletions(-) > diff --git a/include/linux/fb.h b/include/linux/fb.h > index 7fca3dc..9b9842c 100644 > --- a/include/linux/fb.h > +++ b/include/linux/fb.h > @@ -1147,6 +1147,18 @@ struct fb_videomode { > u32 flag; > }; > > +struct fb_cpumode { > + const char *name; /* optional */ > + u32 refresh; /* optional */ > + u32 xres; > + u32 yres; I think that those two fields should happily fit into 'u16' type. > + u32 pixclock; > + u32 cs_setup; > + u32 wr_setup; > + u32 wr_act; > + u32 wr_hold; Suspecting the same about the above 4 fields... WBR, Sergei