[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1440793833.2795.57.camel@toradex.com>
Date: Fri, 28 Aug 2015 20:30:35 +0000
From: Marcel Ziswiler <marcel.ziswiler@...adex.com>
To: "broonie@...nel.org" <broonie@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mporter@...aro.org" <mporter@...aro.org>,
"gnurou@...il.com" <gnurou@...il.com>,
"rafael.j.wysocki@...el.com" <rafael.j.wysocki@...el.com>,
"thierry.reding@...il.com" <thierry.reding@...il.com>,
"ttynkkynen@...dia.com" <ttynkkynen@...dia.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"khilman@...aro.org" <khilman@...aro.org>,
"ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"swarren@...dotorg.org" <swarren@...dotorg.org>,
"linux@....linux.org.uk" <linux@....linux.org.uk>
Subject: Re: [PATCH] arm: tegra: update default configuration
On Fri, 2015-08-28 at 16:51 +0000, Mark Brown wrote:
> Please fix your mailer to word wrap within paragraphs so that your
> mails
> are legible.
Sure, sorry. At times I forget that Android isn't sane in that respect
and can't be used to send mailing list compliant emails.
> > On 27 Aug 2015 16:55, Mark Brown <broonie@...nel.org> wrote:
>
> > > Does the system really have the wm9712 wired up as a battery
> > > monitor?
>
> > Well, remember we are talking about a system on module. Those
> > WM9712
> > pins all go to the 200 pin SODIMM edge connector and I know that
> > certain customers indeed have carrier boards that use it that way.
> > If
> > there is any opposition and considering this being rather optional
> > I
> > may also drop this one but audio/touch is definitely a standard
> > feature available on all or carrier boards.
>
> Does that actually work with mainline? The driver requires platform
> data to do anything useful (there's no DT bindings for it) and I
> can't
> see anything providing that on Tegra systems.
To be honest I have not really tried it resp. I did actually notice it
bailing out but haven't had time to look closer into it yet. We are
using it with NVIDIA's still platform data based downstream L4T R16.5
and I do know that it works there so I just kind of assumed there will
be a way to make it work in mainline as well. However rather than
adding such platform data I guess migrating it to DT would make more
sense. But until such a migration has been completed I guess we rather
just drop enabling it for now and I will send out a v2 in that respect.
Powered by blists - more mailing lists