2012/4/19 Tuwuh S <tuw...@potensi.net>:
> Any updates on this? Does anyone also encounter the same issue?
>
>
> ---
> Tuwuh S
>
> -- To join: http://beagleboard.org/discuss
> To unsubscribe from this group, send email to:
> beagleboard...@googlegroups.com
> Frequently asked questions: http://beagleboard.org/faq
2012/4/21 Lars Poulsen <larsop...@gmail.com>:
2012/4/23 Tuwuh S <tuw...@potensi.net>:
from u-boot you set bootargs for the kernel. There you can use this
argument: i2c_bus=3,100
This means: i2c bus 3, freq=100kHz
2012/4/23 Tuwuh S <tuw...@potensi.net>:
> Actually, I'm curious why this inconsistency occurs (between dmesg reported
> i2c frequency and the actual bus frequency).
> The other question is, is it possible to change the i2c bus frequency from
> userland? Or boot option?
>
> Any pointers are welcomed...
>
>
> ---
> Tuwuh S
>
> -- To join: http://beagleboard.org/discuss
> To unsubscribe from this group, send email to:
21.3.15.3
How to Program I2C
Module Configuration Before Enabling the Module
Program the prescaler to obtain an approximately 12-MHz I2C module clock (I2C_PSC = x; this value is to be calculated and is dependent on the System clock frequency).
i2cspeed=3,400 mmcargs=setenv bootargs console=${console} i2c_bus=${i2cspeed} ${optargs} vram=${vram} omapfb.mode=${defaultdisplay}:${dvimode} omapdss.def_disp=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype} ${device_args}
Frequently asked questions: http://beagleboard.org/faq
<uEnv.txt>
I have said before, if someone can point me at concise instructions for generating an appropriate patch then I'm happy to do it. I put the time into working out at least some of what was wrong, but I don't have the time to noodle around right now figuring out how to submit this. I suspect if I knew the process it's probably only a few minutes of work; is there a tutorial anywhere that walks through the steps?Thanks,
Steve
On May 4, 2012, at 5:43 AM, Klemen Živkovič wrote:
Steve and Koen,
can you two work out his specific format for patch issue - to allow also others to get this update?Thanks to both of you,
Klemen
On Fri, May 4, 2012 at 2:21 PM, Koen Kooi <ko...@beagleboard.org> wrote:
Op 4 mei 2012, om 14:12 heeft Zhivko het volgende geschreven:
No, it needs to be in the git-format-patch format with a signed-off-by line before I can take it.
> Could we expect this to be patch that we could get it from "opkg update" ?
> Trying to use i2c and the it seems reading bytes from i2c device seems to be unstable. Could somebody push this patch ?
-- To join: http://beagleboard.org/discuss
To unsubscribe from this group, send email to:
git clone git://github.com/beagleboard/kernel.gitpushd kernel/git checkout origin/beaglebone-3.2 -b beaglebone-3.2./patch.sh
ls -1
exportkernelpatchespatch_script.shpatch.shREADME.mdsrc-uri.txt
git branch i2c-prescaler-fixgit checkout i2c-prescaler-fix
scite kernel/arch/arm/mach-omap2/omap_hwmod_33xx_data.c kernel/drivers/i2c/busses/i2c-omap.c kernel/include/linux/i2c-omap.h &
[alberto@caboto kernel]$ git status# On branch i2c-prescaler-fixnothing to commit (working directory clean)[alberto@caboto kernel]$ pushd kernel~/Development/oe/kernel/kernel ~/Development/oe/kernel ~/Development/oe ~/Development ~[alberto@caboto kernel]$ git branchmastertmp-patching-branch* tmp-patching-branch-sha[alberto@caboto kernel]$ git status# On branch tmp-patching-branch-sha# Changes not staged for commit:# (use "git add <file>..." to update what will be committed)# (use "git checkout -- <file>..." to discard changes in working directory)## modified: arch/arm/mach-omap2/omap_hwmod_33xx_data.c# modified: drivers/i2c/busses/i2c-omap.c# modified: include/linux/i2c-omap.h#no changes added to commit (use "git add" and/or "git commit -a")[alberto@caboto kernel]$
When used as a development tree i usually run "./patch.sh" to generate
a fresh kernel dir, then apply/tweak my patch to that directory, then
run "git add/git commit -a -m" and with the output of "git
format-patch -1", copy that new "git am'ble" patch to the patches
directory into the appropriate subfolder.. Modifing patch.sh
directory listing if it's something unrelated and thus a new dir..
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
I think it's supposed to be like so:optargs=run_hardware_tests i2c_bus=2,400
However, it appears that nothing I'm putting in uEnv.txt is getting read on boot using the latest Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.06.18.img. Also, my info.txt is not getting updated with any system info. Perhaps these two issues are related?
I can however stop the boot process at the uBoot prompt and edit the env variables there, but saveenv isn't working.
What pins is the /dev/i2c-2 bus exposed at, if any? My current impression is that /dev/i2c-1 (I2C1 in the SRM) is at pins 17&18, and /dev/i2c-3 (SRM I2C2) is at pins 19&20. Is this correct?
T
On Friday, July 27, 2012 6:45:55 PM UTC-7, tcmichals wrote:I'm using 3.2.23 kernel, ie the standard sdcard image. I'm trying to se the i2c speed to 400khz, dmsg[ 0.099945] omap_i2c.1: alias fck already exists[ 0.110961] omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 100 kHz[ 0.234252] omap_i2c.3: alias fck already exists[ 0.234497] omap_i2c omap_i2c.3: bus 3 rev2.4.0 at 100 kHz[ 0.525878] i2c /dev entries driverroot@beaglebone:~# uname -aroot@beaglebone:/boot# more uEnv.txtoptargs=run_hardware_testsi2c_bus=2400root@beaglebone:/boot#I tried changing i2c_bus 4200, etc, but nothing changes. Any suggestions?
--
--