From: Tushar Behera <tushar.behera@linaro.org>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Sachin Kamat' <sachin.kamat@linaro.org>,
linux-samsung-soc@vger.kernel.org, patches@linaro.org,
a.sim@samsung.com, jiun.yu@samsung.com, june.bae@samsung.com
Subject: Re: [PATCH 2/4] ARM: SAMSUNG: Add API to set platform data for s5p-tv driver
Date: Fri, 20 Jul 2012 13:58:23 +0530 [thread overview]
Message-ID: <500916A7.7090803@linaro.org> (raw)
In-Reply-To: <195901cd6601$ab971c60$02c55520$%kim@samsung.com>
On 07/20/2012 04:26 AM, Kukjin Kim wrote:
>
>> -----Original Message-----
>> From: Tushar Behera [mailto:tushar.behera@linaro.org]
>> Sent: Tuesday, July 17, 2012 12:33 PM
>> To: Kukjin Kim
>> Cc: 'Sachin Kamat'; linux-samsung-soc@vger.kernel.org; patches@linaro.org;
>> a.sim@samsung.com; jiun.yu@samsung.com
>> Subject: Re: [PATCH 2/4] ARM: SAMSUNG: Add API to set platform data for
>> s5p-tv driver
>>
>> On 07/17/2012 08:11 AM, Kukjin Kim wrote:
>>> Sachin Kamat wrote:
>>>>
>>>> From: Tushar Behera <tushar.behera@linaro.org>
>>>>
>>>> Commit 350f2f4dad64 ("[media] v4l: s5p-tv: hdmi: add support for
>>>> platform data") makes the presence of platform data mandatory for s5p-
>> tv
>>>> driver. Adding an API to plat-samsung for this purpose.
>>>>
>>>> Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
>>>> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
>>>> ---
>>>> arch/arm/plat-samsung/devs.c | 26
>>> ++++++++++++++++++++++++++
>>>> arch/arm/plat-samsung/include/plat/hdmi.h | 16 ++++++++++++++++
>>>> 2 files changed, 42 insertions(+), 0 deletions(-)
>>>> create mode 100644 arch/arm/plat-samsung/include/plat/hdmi.h
>>>>
>>>> diff --git a/arch/arm/plat-samsung/devs.c b/arch/arm/plat-
>> samsung/devs.c
>>>> index 07b5ac6..921ed88 100644
>>>> --- a/arch/arm/plat-samsung/devs.c
>>>> +++ b/arch/arm/plat-samsung/devs.c
>>>> @@ -32,6 +32,8 @@
>>>> #include <linux/platform_data/s3c-hsudc.h>
>>>> #include <linux/platform_data/s3c-hsotg.h>
>>>>
>>>> +#include <media/s5p_hdmi.h>
>>>> +
>>>> #include <asm/irq.h>
>>>> #include <asm/pmu.h>
>>>> #include <asm/mach/arch.h>
>>>> @@ -759,6 +761,30 @@ void __init s5p_i2c_hdmiphy_set_platdata(struct
>>>> s3c2410_platform_i2c *pd)
>>>> npd = s3c_set_platdata(pd, sizeof(struct s3c2410_platform_i2c),
>>>> &s5p_device_i2c_hdmiphy);
>>>> }
>>>> +
>>>> +struct s5p_hdmi_platform_data s5p_hdmi_def_platdata;
>>>> +
>>>> +void __init s5p_hdmi_set_platdata(struct i2c_board_info *hdmiphy_info,
>>>> + struct i2c_board_info *mhl_info, int
>>> mhl_bus)
>>>> +{
>>>> + struct s5p_hdmi_platform_data *pd = &s5p_hdmi_def_platdata;
>>>> +
>>>> + if (soc_is_exynos4210() || soc_is_exynos4212() ||
>>>> + soc_is_exynos4412())
>>>> + pd->hdmiphy_bus = 8;
>>>> + else if (soc_is_s5pv210())
>>>> + pd->hdmiphy_bus = 3;
>>>> + else
>>>> + pd->hdmiphy_bus = 0;
>>>> +
>>>> + pd->hdmiphy_info = hdmiphy_info;
>>>> + pd->mhl_info = mhl_info;
>>>> + pd->mhl_bus = mhl_bus;
>>>> +
>>>> + s3c_set_platdata(pd, sizeof(struct s5p_hdmi_platform_data),
>>>> + &s5p_device_hdmi);
>>>> +}
>>>
>>> (Cc'ed Ayoung Sim and Jiun Yu in my team)
>>>
>>> Totally I wonder, do we really need s5p_i2c_hdmiphy_set_platdata and
>> this
>>> adding together? You updated s5p_i2c_hdmiphy_set_platdata in your 1/4
>> patch
>>> so I don't see why we should keep the bus number in duplicated...
>>>
>>
>> s5p_i2c_hdmiphy_set_platdata sets platform data for
>> s5p_device_i2c_hdmiphy. 'bus_num' assigned in that structure is not
>> accessible in s5p-tv driver. But s5p-tv driver needs the bus number to
>> get appropriate i2c adapter. Hence we need to update the bus number in
>> both the places.
>>
> 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.
> Thanks.
>
> Best regards,
> Kgene.
> --
> Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
> SW Solution Development Team, Samsung Electronics Co., Ltd.
>
--
Tushar Behera
next prev parent reply other threads:[~2012-07-20 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 8:48 [PATCH 1/4] ARM: SAMSUNG: Set HDMI platform data for Exynos4x12 SoCs Sachin Kamat
2012-07-02 8:48 ` [PATCH 2/4] ARM: SAMSUNG: Add API to set platform data for s5p-tv driver Sachin Kamat
2012-07-17 2:41 ` Kukjin Kim
2012-07-17 3:33 ` Tushar Behera
2012-07-19 22:56 ` Kukjin Kim
2012-07-20 8:28 ` Tushar Behera [this message]
2012-08-08 4:54 ` Kukjin Kim
2012-07-02 8:48 ` [PATCH 3/4] ARM: EXYNOS: Set HDMI platform data in SMDKV310 Sachin Kamat
2012-07-02 8:48 ` [PATCH 4/4] ARM: EXYNOS: Set HDMI platform data in Origen board Sachin Kamat
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=500916A7.7090803@linaro.org \
--to=tushar.behera@linaro.org \
--cc=a.sim@samsung.com \
--cc=jiun.yu@samsung.com \
--cc=june.bae@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=sachin.kamat@linaro.org \
/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.