public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Chris Desjardins
	<chris.desjardins-8HJrC8Or5ylBDgjK7y7TUQ@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] ARM: tegra: Add basic support for carma devkit
Date: Tue, 27 Aug 2013 12:56:29 +0200	[thread overview]
Message-ID: <20130827105628.GA17877@ulmo> (raw)
In-Reply-To: <CAGjquTQe0_+oEtyuF0Q0T8rZnQmz1h45T18zePe+BHVTjVQW_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3221 bytes --]

On Tue, Aug 27, 2013 at 11:15:12AM +0200, Chris Desjardins wrote:
> Thierry, I have looked at the comments, and I have also talked to SECO, and
> they aren't willing to give me the docs necessary to really do the job
> correctly (even if they did give me the docs, I am not 100% sure I would be
> able to do it correctly without a direct line to their hardware engineers),
> they also are unwilling to do it themselves. They did say that they will
> give me feedback on a dts file, but the feedback I got from them on the
> original one was little more than: this doesn't appear to be correct. To be
> honest, we have decided to go with another platform with better support in
> the mainline kernel (4th gen x86, because it is powerful, low power, and
> well supported), and as a result my seco board is collecting dust.

I'm sorry to hear that.

> For reference here is the full "technical" feedback I got from seco:
> 
> we noticed some inconsistencies on dts file you provided: with respect to
> pcie-controller, ldo2 usage is not correct and PCIe lanes declaration
> doesn't look coeherent with actual hardware.
> 
> Not really enough for me to make changes with confidence... I think I have
> already mentioned this, but just to be sure, comparing and contrasting the
> regulator/pci settings from kernel they provide (pre-device tree) and the
> mainline is like comparing apples and oranges. Most of the names have
> changed, and even in the few cases where names seem to correlate it would
> still take me a huge amount of time to really figure out what I am looking
> at in their source/sysfs/etc and translate it to .dts from with
> confidence... and I really have no idea how I would verify it (other than
> looking at sysfs or something, but to me, looking at what sysfs says about
> regulator configuration and verifying that a regulator is configured
> correctly are two different things).

Indeed. It takes quite a bit of effort to successfully correlate the two
datasets.

> Thanks for following up on this, sorry I won't be able to help, feel free
> to take my .dts file and run with it if you want, or pressure seco into
> updating it correctly if you can.

I doubt that I'll be able to exert any more pressure than you did. Given
my lack of hardware I won't be able to drive that effort myself, but
perhaps someone else will pick it up.

Thanks for investigating!

Thierry

> On 27 August 2013 09:56, Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> > On Sun, Jun 23, 2013 at 03:38:05PM +0200, Chris Desjardins wrote:
> > >
> > > Signed-off-by: Chris Desjardins <chris.desjardins-8HJrC8Or5ylBDgjK7y7TUQ@public.gmane.org>
> > > ---
> > >  arch/arm/boot/dts/tegra30-carma.dts |  461
> > +++++++++++++++++++++++++++++++++++
> > >  1 file changed, 461 insertions(+)
> > >  create mode 100644 arch/arm/boot/dts/tegra30-carma.dts
> >
> > Hi Chris,
> >
> > The new PCIe driver is going to be merged in 3.12, so it would be nice
> > to see this patch merged as well as given that it is one of the few
> > users of PCIe.
> >
> > Have you had a chance to look at the comments you received?
> >
> > Thierry
> >

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2013-08-27 10:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-23 13:38 [PATCH 1/1] ARM: tegra: Add basic support for carma devkit Chris Desjardins
2013-06-23 13:54 ` Chris Desjardins
     [not found] ` <1371994685-4997-1-git-send-email-chris.desjardins-8HJrC8Or5ylBDgjK7y7TUQ@public.gmane.org>
2013-06-24 17:19   ` Stephen Warren
2013-06-25 15:47     ` Chris Desjardins
     [not found]       ` <loom.20130625T165829-570-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2013-06-25 16:06         ` Stephen Warren
2013-06-27 16:59   ` Eric Brower
     [not found]     ` <51CC6F83.2010606-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-27 17:51       ` Stephen Warren
     [not found]         ` <51CC7B98.5090103-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-27 18:23           ` Thierry Reding
2013-08-27  7:56   ` Thierry Reding
     [not found]     ` <CAGjquTQe0_+oEtyuF0Q0T8rZnQmz1h45T18zePe+BHVTjVQW_Q@mail.gmail.com>
     [not found]       ` <CAGjquTQe0_+oEtyuF0Q0T8rZnQmz1h45T18zePe+BHVTjVQW_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-27  9:19         ` Fwd: " Chris Desjardins
2013-08-27 10:56         ` Thierry Reding [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=20130827105628.GA17877@ulmo \
    --to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=chris.desjardins-8HJrC8Or5ylBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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