Tushar Behera wrote: > > On 07/20/2012 04:26 AM, Kukjin Kim wrote: > > [...] > >> > > Yeah, I know the situation, but I don't know why we should having the > same > > i2c channel is included in different platform_data. I need to talk about > > this approach to hdmi guys in my team, I'll let you know as soon as > > possible. > > > > While configuring all the i2c channels, we need to pass the channel > number. Since the channel number is not fixed for hdmiphy, it was > updated as per respective CPUs. > > The same would be done for other I2C channels also, we pass channel > number in platform data (s3c_i2c0_set_platdata) and then specify the bus > number as the first parameter in i2c_register_board_info(...) while > adding i2c devices. > > It would be great if we can find a resolution on this before the merge > window. HDMI support in mainline kernel is broken since 3.4-rc1 and we > would love to get this fixed during 3.6. > OK, firstly let's fix its working. But I'm still thinking we need to sort this out next time. Will apply this series, thanks. Best regards, Kgene. -- Kukjin Kim <kgene.kim@xxxxxxxxxxx>, Senior Engineer, SW Solution Development Team, Samsung Electronics Co., Ltd. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |