From: Chen Gang <gang.chen@asianux.com>
To: kyungmin.park@samsung.com, kgene.kim@samsung.com,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org
Subject: [Suggestion] ARM:S5PV210: version merging compiling issue for 'struct fimc_source_info'
Date: Sat, 16 Feb 2013 17:26:39 +0800 [thread overview]
Message-ID: <511F50CF.90403@asianux.com> (raw)
Hello Kukjin Kim:
it is a compiling issue, please help check when you have time.
thanks.
gchen.
in arch/arm/mach-s5pv210/mach-goni.c:848:
error: unknown field 'bus_type' specified in initializer
843 static struct fimc_source_info goni_camera_sensors[] = {
844 {
845 .mux_id = 0,
846 .flags = V4L2_MBUS_PCLK_SAMPLE_FALLING |
847 V4L2_MBUS_VSYNC_ACTIVE_LOW,
848 .bus_type = FIMC_BUS_TYPE_ITU_601,
849 .board_info = &noon010pc30_board_info,
850 .i2c_bus_num = 0,
851 .clk_frequency = 16000000UL,
852 },
853 };
in include/media/s5p_fimc.h:50
37 /**
38 * struct fimc_source_info - video source description required for the host
39 * interface configuration
40 *
41 * @board_info: pointer to I2C subdevice's board info
42 * @clk_frequency: frequency of the clock the host interface provides to sensor
43 * @fimc_bus_type: FIMC camera input type
44 * @sensor_bus_type: image sensor bus type, MIPI, ITU-R BT.601 etc.
45 * @flags: the parallel sensor bus flags defining signals polarity (V4L2_MBUS_*)
46 * @i2c_bus_num: i2c control bus id the sensor is attached to
47 * @mux_id: FIMC camera interface multiplexer index (separate for MIPI and ITU)
48 * @clk_id: index of the SoC peripheral clock for sensors
49 */
50 struct fimc_source_info {
51 struct i2c_board_info *board_info;
52 unsigned long clk_frequency;
53 enum fimc_bus_type fimc_bus_type;
54 enum fimc_bus_type sensor_bus_type;
55 u16 flags;
56 u16 i2c_bus_num;
57 u16 mux_id;
58 u8 clk_id;
59 };
60
WARNING: multiple messages have this Message-ID (diff)
From: gang.chen@asianux.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [Suggestion] ARM:S5PV210: version merging compiling issue for 'struct fimc_source_info'
Date: Sat, 16 Feb 2013 17:26:39 +0800 [thread overview]
Message-ID: <511F50CF.90403@asianux.com> (raw)
Hello Kukjin Kim:
it is a compiling issue, please help check when you have time.
thanks.
gchen.
in arch/arm/mach-s5pv210/mach-goni.c:848:
error: unknown field 'bus_type' specified in initializer
843 static struct fimc_source_info goni_camera_sensors[] = {
844 {
845 .mux_id = 0,
846 .flags = V4L2_MBUS_PCLK_SAMPLE_FALLING |
847 V4L2_MBUS_VSYNC_ACTIVE_LOW,
848 .bus_type = FIMC_BUS_TYPE_ITU_601,
849 .board_info = &noon010pc30_board_info,
850 .i2c_bus_num = 0,
851 .clk_frequency = 16000000UL,
852 },
853 };
in include/media/s5p_fimc.h:50
37 /**
38 * struct fimc_source_info - video source description required for the host
39 * interface configuration
40 *
41 * @board_info: pointer to I2C subdevice's board info
42 * @clk_frequency: frequency of the clock the host interface provides to sensor
43 * @fimc_bus_type: FIMC camera input type
44 * @sensor_bus_type: image sensor bus type, MIPI, ITU-R BT.601 etc.
45 * @flags: the parallel sensor bus flags defining signals polarity (V4L2_MBUS_*)
46 * @i2c_bus_num: i2c control bus id the sensor is attached to
47 * @mux_id: FIMC camera interface multiplexer index (separate for MIPI and ITU)
48 * @clk_id: index of the SoC peripheral clock for sensors
49 */
50 struct fimc_source_info {
51 struct i2c_board_info *board_info;
52 unsigned long clk_frequency;
53 enum fimc_bus_type fimc_bus_type;
54 enum fimc_bus_type sensor_bus_type;
55 u16 flags;
56 u16 i2c_bus_num;
57 u16 mux_id;
58 u8 clk_id;
59 };
60
next reply other threads:[~2013-02-16 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 9:26 Chen Gang [this message]
2013-02-16 9:26 ` [Suggestion] ARM:S5PV210: version merging compiling issue for 'struct fimc_source_info' Chen Gang
[not found] ` <CAH9JG2WS5q4SR8zk5=OC32PHLZ2+ZYva7csyshG7oANacqbCuA@mail.gmail.com>
2013-02-17 1:11 ` Chen Gang
2013-02-17 1:11 ` Chen Gang
2013-02-26 6:38 ` Chen Gang
2013-02-26 6:38 ` Chen Gang
2013-02-26 9:50 ` Sylwester Nawrocki
2013-02-26 9:50 ` Sylwester Nawrocki
2013-02-27 1:14 ` Chen Gang
2013-02-27 1:14 ` Chen Gang
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=511F50CF.90403@asianux.com \
--to=gang.chen@asianux.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.