From: Tony Lindgren <tony@atomide.com>
To: andrzej zaborowski <balrogg@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] Palm TE Touchscreen and fixes
Date: Sun, 15 Jan 2006 12:19:50 -0800 [thread overview]
Message-ID: <20060115201949.GF5905@atomide.com> (raw)
In-Reply-To: <fb249edb0601141306o6eb43a9o@mail.gmail.com>
Hi,
Good to hear you got things working against the current git tree!
* andrzej zaborowski <balrogg@gmail.com> [060115 12:00]:
>
> - The first one fixes the compilation errors and some clock issues
> that made the kernel hang on boot on Palm Tungsten E. While these
> changes make the kernel boot and work well with the device, and
> hopefully don't affect other devices, I don't know how correct are my
> ways of fixing it, as I'm completely inexperienced in kernel insides.
Regarding changes to clock.[ch], we should have CLOCK_IN_OMAP1510 and
CLOCK_IN_OMAP3XX separate. At least the DSP clocks should not be on 310
because it does not have a DSP AFAIK. They may be also other clocks that
are not on 310.
Could you please redo the clock.[ch] patch so it adds CLOCK_IN_OMAP3XX,
and masks it only for the clocks you think you have on 310?
Or if you don't know which clocks are on both 310 and 1510, you could
just leave out DSP clocks for now, and enable all other 1510 clocks
also for 310.
Regards,
Tony
next prev parent reply other threads:[~2006-01-15 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 21:06 [PATCH] Palm TE Touchscreen and fixes andrzej zaborowski
2006-01-15 9:10 ` Komal Shah
2006-01-15 16:04 ` Juha Yrjölä
2006-01-16 6:05 ` Komal Shah
2006-01-15 17:14 ` andrzej zaborowski
2006-01-15 20:19 ` Tony Lindgren [this message]
2006-01-16 23:23 ` andrzej zaborowski
2006-01-20 19:53 ` tony
2006-01-21 0:41 ` andrzej zaborowski
-- strict thread matches above, loose matches on Subject: below --
2006-01-16 23:41 Woodruff, Richard
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=20060115201949.GF5905@atomide.com \
--to=tony@atomide.com \
--cc=balrogg@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