linux-kernel - Re: [PATCH v9 1/2] ARM: EXYNOS: Change System MMU platform device definitions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <4F4DF2EF.1090505@samsung.com>
Date:	Wed, 29 Feb 2012 10:42:07 +0100
From:	Sylwester Nawrocki <s.nawrocki@...sung.com>
To:	KyongHo Cho <pullip.cho@...sung.com>
Cc:	Kyungmin Park <kyungmin.park@...sung.com>,
	linux-arm-kernel@...ts.infradead.org,
	linux-samsung-soc@...r.kernel.org,
	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	Kukjin Kim <kgene.kim@...sung.com>,
	Joerg Roedel <joro@...tes.org>,
	Subash Patel <subash.ramaswamy@...aro.org>,
	Younglak Kim <younglak1004.kim@...sung.com>,
	Sanghyun Lee <sanghyun75.lee@...sung.com>,
	Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH v9 1/2] ARM: EXYNOS: Change System MMU platform device
 definitions

Hello,

On 02/29/2012 01:25 AM, KyongHo Cho wrote:
>>>  static int exynos4_clk_hdmiphy_ctrl(struct clk *clk, int enable)
>>>  {
>>>       return s5p_gatectrl(S5P_HDMI_PHY_CONTROL, clk, enable);
>>> @@ -679,61 +684,55 @@ static struct clk exynos4_init_clocks_off[] = {
>>>               .enable         = exynos4_clk_ip_peril_ctrl,
>>>               .ctrlbit        = (1 << 14),
>>>       }, {
>>> -             .name           = "SYSMMU_MDMA",
>>> +             .name           = SYSMMU_CLOCK_NAME,
>>> +             .devname        = SYSMMU_CLOCK_DEVNAME(mfc_l, 0),
>>> +             .enable         = exynos4_clk_ip_mfc_ctrl,
>>> +             .ctrlbit        = (1 << 1),
>>> +     }, {
>>> +             .name           = SYSMMU_CLOCK_NAME,
>>> +             .devname        = SYSMMU_CLOCK_DEVNAME(mfc_r, 1),
>>> +             .enable         = exynos4_clk_ip_mfc_ctrl,
>>> +             .ctrlbit        = (1 << 2),
>>> +     }, {
>>> +             .name           = SYSMMU_CLOCK_NAME,
>>> +             .devname        = SYSMMU_CLOCK_DEVNAME(tv, 2),
>>> +             .enable         = exynos4_clk_ip_tv_ctrl,
>>> +             .ctrlbit        = (1 << 4),
>>> +     }, {
>>> +             .name           = SYSMMU_CLOCK_NAME,
>>> +             .devname        = SYSMMU_CLOCK_DEVNAME(jpeg, 3),
>>> +             .enable         = exynos4_clk_ip_cam_ctrl,
>>> +             .ctrlbit        = (1 << 11),
>>> +     }, {
>>> +             .name           = SYSMMU_CLOCK_NAME,
>>> +             .devname        = SYSMMU_CLOCK_DEVNAME(rot, 4),
>>>               .enable         = exynos4_clk_ip_image_ctrl,
>>> -             .ctrlbit        = (1 << 5),
>>> +             .ctrlbit        = (1 << 4),
>>>       }, {
>>> -             .name           = "SYSMMU_FIMC0",
>>> +             .name           = SYSMMU_CLOCK_NAME,
>>> +             .devname        = SYSMMU_CLOCK_DEVNAME(gsc0, 5),
>> It's exynos4 series clock and don't have gsc name. I don't know LSI
>> decides to use gsc instead of fimc for both exynos4 and exynos5. but
>> there's no name gsc at Spec..
> 
> gsc0 is just a name of the platform device of FIMC0 in Exynos4.

I think it's not right what you're saying. Gscalers first appeared only
in exynos5 (at least according to all specifications I have) and you already
have the corresponding change for clock-exynos5.c. FIMCs in exynos 4210, 4212
and 4412 are almost not changed, so please don't rename like this, which is 
confusing. If you need common clkdev entries for the exynos4 and exynos5 
devices, then the "devname"s above might need to be removed and required 
clock entries should be created through the CLKDEV_INIT() macro.

> It is also used for GSclaler0 in Exynos5.
> I wanted to reduce waste of platform device definitions that do not exist
> in an application processor.
> 
> If it looks confused, I will find another way.

Thanks,
-- 
Sylwester Nawrocki
Samsung Poland R&D Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/