linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX28 die temperature
Date: Thu, 28 Jun 2012 05:05:41 +0200	[thread overview]
Message-ID: <201206280505.41201.marex@denx.de> (raw)
In-Reply-To: <201206271433.15303.jbe@pengutronix.de>

Dear Juergen Beisert,

[...]

So, I've been thinking about mapping channels and delay slots at runtime. Is it 
really necessary? I know it's really cool and all, but it adds a lot of 
complexity. For starters, I was thinking we should try to do static mapping. And 
when that's all perfected, go further and try doing it dynamically. What do you 
think about the following DT binding:

lradc at 80050000 {
        compatible = "fsl,imx28-lradc";
        reg = <0x80050000 2000>;
        interrupts = <10 14 15 16 17 18 19
                        20 21 22 23 24 25>;
        fsl,delay-freq = <10 100 50 60>;
        fsl,delay-repeat = <3 10 5 6>;
        fsl,delay-channels = <
                0 2 0 3 0 4 0 5
                1 8 1 9 2 12 3 13>;
        status = "disabled";
};

fsl,delay-freq would be an array (for all four delay channels) of their sampling 
frequencies.

fsl,delay-repeat would be an array (for all four delay channels) of the 
oversampling count.

fsl,delay-channels would be an array (for all four delay channels) of touples of 
delay channel, adc channel. In the above example, it's ADC channels 2,3,4,5 
mapped to delay channel 0, ADC channels 8,9 mapped to delay channel 1 etc.

Now, it might be dumb, advice is welcome!

> > [...]
> 
> Regards,
> Juergen

Best regards,
Marek Vasut

  parent reply	other threads:[~2012-06-28  3:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 15:13 i.MX28 die temperature Randle, Bill
2012-03-29  2:37 ` Shawn Guo
2012-03-29 15:52   ` Randle, Bill
2012-04-04 23:51     ` Marek Vasut
2012-04-05  0:07       ` Randle, Bill
2012-04-05  0:36         ` Fabio Estevam
2012-06-22 11:49           ` Juergen Beisert
2012-06-22 17:19             ` Marek Vasut
2012-06-26  8:12               ` Juergen Beisert
2012-06-26 19:02                 ` Marek Vasut
2012-06-27  7:21                   ` Jonathan Cameron
2012-06-27 12:00                     ` Marek Vasut
2012-06-27 12:06                       ` Jonathan Cameron
2012-06-27 12:25                         ` Marek Vasut
2012-06-27 12:33                         ` Juergen Beisert
2012-06-27 22:58                           ` Marek Vasut
2012-06-28  8:00                             ` Jonathan Cameron
2012-06-28  3:05                           ` Marek Vasut [this message]
2012-06-28 15:42                             ` Marek Vasut
2012-10-23  8:48                       ` Peter Turczak
2012-10-23  8:52                         ` Marek Vasut
2012-10-23 10:22                           ` Peter Turczak
2012-10-23 10:32                             ` Marek Vasut

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=201206280505.41201.marex@denx.de \
    --to=marex@denx.de \
    --cc=linux-arm-kernel@lists.infradead.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).