From: Marek Vasut <marek.vasut@gmail.com>
To: dylan cristiani <d.cristiani@idem-tech.it>
Cc: linux-arm-kernel@lists.infradead.org, linux-input@vger.kernel.org
Subject: Re: hi marek
Date: Tue, 9 Nov 2010 19:36:13 +0100 [thread overview]
Message-ID: <201011091936.13781.marek.vasut@gmail.com> (raw)
In-Reply-To: <20101109184220.00003433@unknown>
On Tuesday 09 November 2010 18:42:20 dylan cristiani wrote:
> We heard some month ago, about ucb1400 irq passing, via
> ucb1400_platform_data; then you wrote the patch, that is currently into
> mainline; i've a little problem, probably due to my infinite ignorance:
> i'm writing a sort of my_pm.c driver to check whether the ac line is
> plugged or not, check the main battery voltage and so on (similar to
> arch/arm/mach-pxa/sharpsl_pm.c and corgi_pm.c if you know it); the
> problem is that the battery voltages are tied to the ucb1400 ADC
> inputs, and in my_pm.c driver i don't know how to find the ucb1400_ts
> structure address to call the functions i need to read these ADC input
> i.e.:
1) CC lists
2) Can you post the driver source you have ?
without seeing the source, I can't help you
> unsigned long read_mainbattery_value(void){
> ....
> ucb1400_adc_enable(ucb->ac97);
> return ucb1400_adc_read(ucb->ac97, UCB_ADC_INP_AD0, adcsync);
> ucb1400_adc_disable(ucb->ac97);
> ....
> }
>
>
> Wwhere can i find info to set (into my_pm.c module) the
> struct ucb1400_ts *ucb = ???
>
> to be passed to the above function read_mainbattery_value()? the fact
> is that the "ucb1400_ts" device platform is already allocked, added and
> the driver registred by the driver/mfd/ucb1400_core.c module so i don't
> know how to find this structure...
>
> if it's too stupid question please sorry for the noise...
>
> thanks a million
>
> dylan
next parent reply other threads:[~2010-11-09 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101109184220.00003433@unknown>
2010-11-09 18:36 ` Marek Vasut [this message]
2010-11-10 9:07 ` hi marek dylan cristiani
2010-11-10 9:29 ` Haojian Zhuang
2010-11-10 9:52 ` Marek Vasut
2010-11-10 11:09 ` dylan cristiani
2010-11-10 9:29 ` 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=201011091936.13781.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=d.cristiani@idem-tech.it \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.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).