Hi,
I started working on snowball v8 development board to
investigate usb otg. My initial effort didn't gave me any result.
I started investigating otg driver it seems that it starts in idle
mode and then update its status to peripheral mode based on
line status. Which in this case should go into host mode as per
cable Mini-A. I manually put the driver into host mode and using
debug messages in driver. It started to detect memory stick
being plugged in and plugged out but it wasn't appearing as
block device. As AB8500 interface chip documentation for usb is
not in public domain makes it nearly impossible to debug the driver
further.
As usb otg is bus power so only low power device can be used.
Thanks
Adnan
Hi there. Over the next three months both GCC 4.7 and Ubuntu 12.04
'Precise' are coming out. We'll switch over to these pretty quickly
which will affect our internal testing and anyone using the binary
toolchain.
The changeover plan including dates, details of what's happening, and
backwards compatibility is at:
https://wiki.linaro.org/MichaelHope/Sandbox/BinariesMigration
Comments and concerns are welcome,
-- Michael
From: Mike Turquette <mturquette(a)ti.com>
The common clock framework defines a common struct clk as well as an
implementation of the clk api that unifies clock operations on various
platforms and devices.
The net result is consolidation of many different struct clk definitions
and platform-specific clock framework implementations.
I consider this version merge-worthy pending ACKs from the relevant
maintainers; namely Russell, Thomas and the platform folks interested in
porting to this framework.
I would like to thank everyone who participated in the common clk
sessions at Linaro Connect and ELC; the feedback was invaluable.
Also I would like to thank Shawn Guo, Richard Zhao, Saravana Kannan and
Magnus Damm for tirelessly updating their platforms for the last few
revisions of this patch series and providng excellent feedback each
time.
Major changes since v4:
* rolled in TGLX's comments on overall design. We now have,
* proper handling of root clocks and orphan clocks
* multi-parent clocks are handled in the core
* struct clk is shielded from struct clk_foo and vice versa
* this is a return to the previous struct clk_hw design
* split basic clock types out into separate files
* split headers up by purpose
* clk.h remains the driver-level interface
* declarations for rate change notifiers are the only additions
* clk-provider.h is primary header for implementing clock operations
* clk-private.h allows for static initialization of clock data
* validation and bug fixes
* rebased onto Linus' v3.3-rc5 tag
Patches can be pulled from:
git://git.linaro.org/people/mturquette/linux.git v3.3-rc5-clkv5
v4 can be found at,
http://article.gmane.org/gmane.linux.linaro.devel/8896/
v3 can be found at,
http://article.gmane.org/gmane.linux.kernel/1218622
Mike Turquette (4):
Documentation: common clk API
clk: Kconfig: add entry for HAVE_CLK_PREPARE
clk: introduce the common clock framework
clk: basic clock hardware types
Documentation/clk.txt | 201 +++++++
drivers/clk/Kconfig | 31 +
drivers/clk/Makefile | 2 +
drivers/clk/clk-divider.c | 199 +++++++
drivers/clk/clk-fixed-rate.c | 81 +++
drivers/clk/clk-gate.c | 121 ++++
drivers/clk/clk-mux.c | 114 ++++
drivers/clk/clk.c | 1323 ++++++++++++++++++++++++++++++++++++++++++
include/linux/clk-private.h | 192 ++++++
include/linux/clk-provider.h | 294 ++++++++++
include/linux/clk.h | 68 ++-
11 files changed, 2621 insertions(+), 5 deletions(-)
create mode 100644 Documentation/clk.txt
create mode 100644 drivers/clk/clk-divider.c
create mode 100644 drivers/clk/clk-fixed-rate.c
create mode 100644 drivers/clk/clk-gate.c
create mode 100644 drivers/clk/clk-mux.c
create mode 100644 drivers/clk/clk.c
create mode 100644 include/linux/clk-private.h
create mode 100644 include/linux/clk-provider.h
Cc: Jeremy Kerr <jeremy.kerr(a)canonical.com>
Cc: Thomas Gleixner <tglx(a)linutronix.de>
Cc: Arnd Bergman <arnd.bergmann(a)linaro.org>
Cc: Paul Walmsley <paul(a)pwsan.com>
Cc: Shawn Guo <shawn.guo(a)freescale.com>
Cc: Richard Zhao <richard.zhao(a)linaro.org>
Cc: Saravana Kannan <skannan(a)codeaurora.org>
Cc: Magnus Damm <magnus.damm(a)gmail.com>
Cc: Rob Herring <rob.herring(a)calxeda.com>
Cc: Mark Brown <broonie(a)opensource.wolfsonmicro.com>
Cc: Linus Walleij <linus.walleij(a)stericsson.com>
Cc: Stephen Boyd <sboyd(a)codeaurora.org>
Cc: Amit Kucheria <amit.kucheria(a)linaro.org>
Cc: Deepak Saxena <dsaxena(a)linaro.org>
Cc: Grant Likely <grant.likely(a)secretlab.ca>
Cc: Andrew Lunn <andrew(a)lunn.ch>
--
1.7.5.4
Sent from Samsung MobileAndy Green <andy.green(a)linaro.org> wrote:On 03/16/2012 10:46 PM, Somebody in the thread at some point said:
> If you look at tilt-android-tracking, there is a complete 1.8 SGX
> (usable on ICS) on fairly recent basis which includes its own rpmsg
> stack as part of the SGX port. The matching userlands are available via
> google AOSP.
>
> http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git;a=shortl…
>
> We also have what's currently only working on
>
>
> I was a bit unclear. Sorry. First, we are thinking of using Linux for
> this task instead of Android. We want rpmsg support to get access to the
> m3 devices for h264 encoding and decoding. with pvr I basically meant a
> dss which can be used to compile rsalvetis pvr omap 4 kernel module.
Bit unclear is an understatement in this case ^^ rpmsg is a complete red
herring then.
1.7 SGX as currently used in Ubuntu does not use rpmsg. All the
currently available mm decode solutions for Ubuntu don't use it yet
either, they use its predecessor "syslink".
If you check out tilt-3.1 branch from our repo that has working syslink
+ tiler pieces needed by the mm decode pieces in Ubuntu and will build
against SGX dkms.
-Andy
--
Andy Green | TI Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
So what you are basically saying is forget rpmsg for the time being? Do you know if gst-ducati works with syslink then?
thank you so much for your help so far.
Hi,
I am currently playing with a couple of the development boards for which
there are Linaro hwpacks and LEBs. Since what I am trying to do requires
a lot of disk and network I/O, I've been paying special attention to the
data transfer rates I can get out of these boards.
Below is a brief summary of my findings.
1) i.MX 53
* disk I/O using an external SSD drive is very good; good enough to
not require further measurements
* network I/O is approximately 9-10 MByte/s (perhaps more) which
seems ok given the 100 MBit/s Ethernet interface
2) Snowball (PDK, version 8)
* it seems to be impossible to get the USB OTG host mode to work,
therefore I could not test disk I/O with a USB drive; it appears
the OTG port on the version 8 board does not even have enough power
for a powered USB to actually go online (I am unaware of the
details of how this works unfortunately)
* performing network I/O with netcat casues netcat, ksoftirqd and
kworker to use ~33% of the CPU each, resulting in 100% CPU usage
only to handle the network data transfer
* the resulting network transfer rate is about 5.5 MByte/s, which
is significantly less than what the 100 MBit/s Ethernet interface
should be able to produce
3) Origen
* the internal USB hub runs at Full Speed (12 MBit/s), resulting in a
maximum USB disk I/O of 1.5 MByte/s
* since the board does not feature Ethernet itself, I tried to attach
a USB Ethernet controller to it, but of course the transfer rate
through that is by the I/O upper limit of the USB hub
* I did not test wireless but it is not feasible for what I am trying
to do anyway
I guess not all of this is surprising. The i.MX performs quite well but
unfortunately the CPU is quite slow compared to the others. However, I
wonder whether the USB OTG host mode issue on the Snowball is a known
problem? Also, network I/O occupying all of the CPU seems to be a bug or
at least a dodgy driver. About the Origen: I assume there is nothing
that can be done to have High Speed USB on it?
Thanks in advance! If anyone needs me to provide more information, I'll
gladly try to do that.
Regards,
Jannis
This is the first announcement on upcoming changes to the supported
Linaro GCC versions.
GCC 4.7 is expected out in the next two weeks. We plan to switch to
4.7 for the Linaro GCC 2012.04 release and, as part of that, will put
Linaro GCC 4.6 into maintenance and retire Linaro GCC 4.5. While in
maintenance we will continue to update, fix bugs, and do releases on
4.6. No further changes or releases will be made to 4.5. All
historical releases and branches will stay available.
For more informatio, please see the flyer at:
https://wiki.linaro.org/WorkingGroups/ToolChain/Flyer
especially the section on Lifecycle:
https://wiki.linaro.org/WorkingGroups/ToolChain/Flyer#Lifecycle
The formal change notes will be sent after the 2012.04 release.
-- Michael