linux-kernel - RE: [PATCH v4 2/4] ARM: Exynos5250: Enabling ohci-exynos driver

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]

Date:	Thu, 31 Jan 2013 14:26:51 -0800
From:	Kukjin Kim <kgene.kim@...sung.com>
To:	'Tomasz Figa' <tomasz.figa@...il.com>,
	'Vivek Gautam' <gautam.vivek@...sung.com>
Cc:	linux-samsung-soc@...r.kernel.org,
	devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org, grant.likely@...retlab.ca,
	dianders@...omium.org, jg1.han@...sung.com
Subject: RE: [PATCH v4 2/4] ARM: Exynos5250: Enabling ohci-exynos driver

Tomasz Figa wrote:
> 
> Hi Vivek,

[...]

> > +	usb@...20000 {
> > +		compatible = "samsung,exynos4210-ohci";
> > +		reg = <0x12120000 0x100>;
> > +		interrupts = <0 71 0>;
> 
> For Samsung platforms we decided per board enabling of nodes and so this
> node should also contain:
> 
> 		status = "disabled";
> 
> while in dts file of board using ohci there would be an overriding entry:
> 
> 	usb@...20000 {
> 		status = "okay";
> 	};
> 
> I know that Exynos5250 has not been yet converted into this convention,
> but using it when adding new devices will simplify the process.
> 
Well, I have another opinion on this...

Let's see, yeah, we are using following method in EXYNOS4 DT...
- disabling IPs in SoC DT source and enabling IPs in board DT source

But as I said, in EXYNOS5440 DT, I want to use following, because most of
them should be enabled/used.
- enabling IPs in SoC DT source and no need enabling in board DT source.

I mean, it depends on each SoC's situation.

Thanks.

- Kukjin

--
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/