From: Tomasz Figa <t.figa@samsung.com>
To: Kukjin Kim <kgene@kernel.org>
Cc: 'Mark Brown' <broonie@kernel.org>,
'Mark Rutland' <mark.rutland@arm.com>,
rob.herring@calxeda.com, 'Pawel Moll' <Pawel.Moll@arm.com>,
'Stephen Warren' <swarren@wwwdotorg.org>,
linux-samsung-soc@vger.kernel.org,
linaro-kernel@lists.linaro.org,
'devicetree' <devicetree@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: Disable Exynos5250 I2S controllers by default
Date: Thu, 12 Sep 2013 13:15:15 +0200 [thread overview]
Message-ID: <3071955.IukkWJSFK6@amdc1227> (raw)
In-Reply-To: <06ff01ceafa4$d81671d0$88435570$@org>
Hi Kukjin,
On Thursday 12 of September 2013 19:42:57 Kukjin Kim wrote:
> Mark Brown wrote:
> > On Tue, Sep 10, 2013 at 06:35:48PM +0100, Mark Rutland wrote:
> > > It seems far more sensible to me to mark devices disabled by default
> > > in
> > > shared dtsi files and then okay them as needed in particular dts
> > > files.
> > > I'd be happy with more of this.
> >
> > Yeah, me too - though only for devices that have an external impact,
> > for
> > things that are internal only (eg, a crypto engine) it makes sense to
> > enable them by default since they should normally be usable regardless
> > of the system configuration.
>
> (+ DT ML)
>
> Makes sense but I need to get the opinions from DT guys...
Yes, this patch should have been posted to the DT ML indeed, but it has
been already acked by Mark Rutland, one of DT binding maintainers.
Best regards,
Tomasz
prev parent reply other threads:[~2013-09-12 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1378491435-15624-1-git-send-email-broonie@kernel.org>
[not found] ` <20130910173548.GA18878@e106331-lin.cambridge.arm.com>
[not found] ` <20130910174113.GB4708@sirena.org.uk>
2013-09-12 10:42 ` [PATCH] ARM: dts: Disable Exynos5250 I2S controllers by default Kukjin Kim
2013-09-12 11:15 ` Tomasz Figa [this message]
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=3071955.IukkWJSFK6@amdc1227 \
--to=t.figa@samsung.com \
--cc=Pawel.Moll@arm.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.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).