From: Kukjin Kim <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: 'Tomasz Figa'
<tomasz.figa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
'Vivek Gautam'
<gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH v4 2/4] ARM: Exynos5250: Enabling ohci-exynos driver
Date: Thu, 31 Jan 2013 14:26:51 -0800 [thread overview]
Message-ID: <0b0001ce0002$12ecda90$38c68fb0$@samsung.com> (raw)
In-Reply-To: <2542030.a14I18dBkO@flatron>
Tomasz Figa wrote:
>
> Hi Vivek,
[...]
> > + usb@12120000 {
> > + 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@12120000 {
> 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
next prev parent reply other threads:[~2013-01-31 22:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 13:38 [PATCH v4 0/4] Enable ehci, ohci and dwc3 devices on exynos5250 Vivek Gautam
2013-01-15 13:38 ` [PATCH v4 1/4] ARM: Exynos5250: Enabling ehci-s5p driver Vivek Gautam
2013-01-16 5:21 ` Vivek Gautam
2013-01-16 5:45 ` [PATCH v5 " Vivek Gautam
2013-01-16 7:51 ` Tomasz Figa
2013-02-08 22:35 ` Kukjin Kim
2013-02-15 5:09 ` Vivek Gautam
2013-01-15 13:38 ` [PATCH v4 2/4] ARM: Exynos5250: Enabling ohci-exynos driver Vivek Gautam
2013-01-16 7:44 ` Tomasz Figa
2013-01-16 15:09 ` Vivek Gautam
2013-01-31 22:26 ` Kukjin Kim [this message]
2013-02-04 11:15 ` Vivek Gautam
[not found] ` <1358257112-19595-1-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-01-15 13:38 ` [PATCH v4 3/4] ARM: Exynos5250: Add clock information for dwc3-exynos Vivek Gautam
2013-01-16 7:49 ` Tomasz Figa
2013-01-16 15:05 ` Vivek Gautam
[not found] ` <CAFp+6iHd66_dvj_M5zOpJZ7sEy-pYa-CdWKUZBYc3Dfn3JHtfg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-23 13:15 ` Vivek Gautam
2013-01-30 6:54 ` Kukjin Kim
2013-01-29 7:07 ` Vivek Gautam
2013-01-15 13:38 ` [PATCH v4 4/4] ARM: Exynos5250: Enabling dwc3-exynos driver Vivek Gautam
2013-01-16 7:51 ` Tomasz Figa
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='0b0001ce0002$12ecda90$38c68fb0$@samsung.com' \
--to=kgene.kim-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tomasz.figa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).