From: tony@atomide.com
To: Komal Shah <komal.shah802003@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH]: Workqueue changes for board-h3
Date: Tue, 2 Jan 2007 12:35:24 -0800 [thread overview]
Message-ID: <20070102203523.GD9733@atomide.com> (raw)
In-Reply-To: <3a5b1be00612281133p5c3e870eybd6a3eacccc2e859@mail.gmail.com>
* Komal Shah <komal.shah802003@gmail.com> [061228 11:43]:
> On 12/28/06, Felipe Balbi <felipebalbi@users.sourceforge.net> wrote:
> >Hello Komal,
> >>> -static void set_trans_mode(void *data)
> >>> +static void set_trans_mode(struct work_struct *data)
> >>> {
> >>> - int *mode = data;
> >>> + int *mode = (int *)data;
> >
> >>Did you tested this patch.? I am not sure this casting is the correct
> >>way to go for it.
> >
> >I'm wondering if that
> >>> + int *mode = (int *)data;
> >
> >shouldn't be
> >int *mode = (int *) data->data;
> >
> >the second data is a atomic_long_t witch is a volatile int...
> >
> >What does it mean these IrDA Flags??
> >
> >#define IR_SEL 1 /* Selects IrDA */
>
> Above is customized flag for H4/H3 EVM, as we need to select between
> the IrDA and aGPS module by programming through gpio expander. see
> board-h4.c and board-h3.c for its usage (for enabling/disabling the IR
> TX/RX).
>
> >#define IR_SIRMODE 2
> >#define IR_FIRMODE 4
> >#define IR_MIRMODE 8
> >
>
> Above three denotes the capabilities of the transeciver, meaning which
> speeds are supported by it.
Can you please try Dirk's patch for H3?
Tony
next prev parent reply other threads:[~2007-01-02 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31e679430612280750l77e590e4ice853ef8b4c3d05f@mail.gmail.com>
2006-12-28 19:33 ` [PATCH]: Workqueue changes for board-h3 Komal Shah
2007-01-02 20:35 ` tony [this message]
[not found] <20061228132843.6403.qmail@web33710.mail.mud.yahoo.com>
2006-12-28 13:31 ` Fwd: " Ragner N Magalhães
2006-12-28 14:48 ` Komal Shah
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=20070102203523.GD9733@atomide.com \
--to=tony@atomide.com \
--cc=komal.shah802003@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
/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