On Wed, Oct 21, 2009 at 03:44:51, Linus Walleij wrote:
2009/10/20 Chaithrika U S chaithr...@ti.com:
Add cpufreq support to MMC driver. The clock divider value has to be
modified according to the controller input frequency.
(...)
@@ -1040,6 +1052,52 @@ static struct mmc_host_ops
I want to compile a library of algorithms that providing for Codec Server in
the linux environment.
However, the compilation of this library need to use other libraries.
How can I build passed?
thanks!
2009-10-21
北京闻亭泰科技术发展有限公司
姓名：林法宝
Email:li...@dspchina.com
地址:北京市海淀区上地三街9号嘉华大厦B811
网址:
I want to compile a library of algorithms that providing for Codec Server in
the linux environment.
However, the compilation of this library need to use other libraries.
How can I build passed?
2009-10-21
北京闻亭泰科技术发展有限公司
姓名：林法宝
Email:li...@dspchina.com
地址:北京市海淀区上地三街9号嘉华大厦B811
网址:
On the DA830, AEMIF and MMC/SD pins are shared. On the EVM, when
the mux_mode signal is low MMC/SD works and when mux_mode signal
is high, NAND works.
When MMC/SD driver is configured in the kernel, do not let NAND
get registered and drive mux_mode high. Instead, print a warning
for user to
Get rid of DA850_UI_EXP config option since it is not used anywhere
else in code.
Instead make the UI expander choice menu dependent on the EVM
selection itself.
Also add help text indicating that UI board is actually detected
automatically.
Signed-off-by: Sekhar Nori nsek...@ti.com
---
This patch supports runtime detection of DA830 UI card and
eliminates the need for DA830_UI config option. Successful
probe of GPIO expander present on the UI card is used to
detect its presence. For this reason, GPIO_PCF857X is auto-
selected when DA830 EVM is configured. In case the UI card
is
Implement autodetection of RMII PHY by shifting the decision
to use the RMII PHY to da850_evm_ui_expander_setup() from
da850_evm_init() earlier.
Without this patch, selecting RMII PHY in the UI expander menu
will make the MII PHY unusable even though UI board is not
connected.
The actual
There are multiple steps in configuring the EMAC to MII or RMII mode.
Current code implements them using multiple checks.
Consolidate the multiple checks into a single if construct.
Signed-off-by: Sekhar Nori nsek...@ti.com
---
arch/arm/mach-davinci/board-da850-evm.c | 35
On Thu, Oct 15, 2009 at 20:27:40, Kevin Hilman wrote:
Sekhar Nori nsek...@ti.com writes:
This patch supports runtime detection of DA830 UI card and
eliminates the need for DA830_UI config option. Successful
probe of GPIO expander present on the UI card is used to
detect its presence. For
Hello.
Sekhar Nori wrote:
On the DA830, AEMIF and MMC/SD pins are shared. On the EVM, when
the mux_mode signal is low MMC/SD works and when mux_mode signal
is high, NAND works.
When MMC/SD driver is configured in the kernel, do not let NAND
get registered and drive mux_mode high. Instead,
A compilation of source code does not require any libraries, just header
files. Libraries are used only by a linker, usually for linking the final app.
You could pre-link your library of algorithms with the other libraries by doing
a partial link, which would bring the needed library code into
I believe many of you have likely seen the new Sitara ARM product family
announcement[1] as part of broadening our ARM product portfolio[2]. This
family draws processing cores from the DaVinci family of DSP/multimedia devices
and OMAP family of low-power devices and focuses on markets like
From: Muralidharan Karicheri m-kariche...@ti.com
This is the initial version of the digital video timings APIs implementation.
This adds the above APIs to the v4l2 core. This is based on version v1.2
of the RFC titled V4L - Support for video timings at the input/output
interface
Following new
Hi Murali,
From: Muralidharan Karicheri m-kariche...@ti.com
This is the initial version of the digital video timings APIs
implementation.
This adds the above APIs to the v4l2 core. This is based on version v1.2
of the RFC titled V4L - Support for video timings at the input/output
On Wed, Oct 21, 2009 at 21:36:40, Sergei Shtylyov wrote:
Hello.
Sekhar Nori wrote:
On the DA830, AEMIF and MMC/SD pins are shared. On the EVM, when
the mux_mode signal is low MMC/SD works and when mux_mode signal
is high, NAND works.
When MMC/SD driver is configured in the kernel, do
hello everyone,I am trying to write a character driver for SPI on Dm355
evm, LSP 1.2 , MV-4..Can I get any help ?? eg. example codes or anything ??
I am not able to call __devinit tagged function.Because of that I am
getting error in retrieving platform data.
-Digant Desai
16 matches
Mail list logo
