I have no concrete proposal but it really sounds like a common RTC interface would be needed here – if it doesn’t exist already. In the command list you should see a line that looks like this:. I am relatively new to Linux, so any help would be much appreciated. If the “invalid argument” error only occurs the first time you use the RTC then I think you are going to have to go through a commissioning process that sets the clock. I had to do similar thing for Ethernet controller in u-boot script, but this was to enable external PHY through gpio:. There is no reason why it can’t be initialised during the normal driver initialisation – which is how we do it on a number of ARM platforms. It’s both conceptually wrong and actually unnecessary.
|Date Added:||3 December 2004|
|File Size:||63.86 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The problem is that Linux is not loading the driver.
[PATCH] ds driver works also with ds chip [Linux ] – Linux Kernels
Linux kernel is Linux 4. If so, the module will be called ds But it’s in linux-next and Linus has pulled it into his tree, so should be out soon. But still after I2C probing there was nothing on oscilloscope. I have played around with u-boot, and noticed that I2C was held in reset.
I’m not sure if adding yet another driver specific header is a good idea.
I’ve added this code to the dts file i2c-rtc-overlay. It’s here if you want to cherry-pick it and build your own kernel: I’m probably doing something wrong so any pointers would be nice Select all hwclock -r hwclock: You can check the driver source in the kernel tree and see.
Adding a new RTC to i2c-rtc-overlay. Hold down a key during boot from power-up or reset, and at the u-boot prompt enter help to see if there are I2C tools built-in.
Do you have the devices listed in the tree on your board: I had to do similar thing for Ethernet controller in u-boot script, but linjx was to enable external PHY through gpio:. Maybe I need to enable something extra in I2C controller during boot? And scan is finished instantly. On Wed, May 04, at Probably, they are init values for the RTC, but I couldn’t find any documentation about that: Can’t say more unfortunately, as I never had to use a RTC myself.
In the meantime you posted reply with pre-loader issue, and after re-compiling the pre-loader, now I can see transmission on scope, as well as: I had to do similar thing linus Ethernet controller in u-boot script, but this was to enable external PHY through gpio: So, to sum up: Then I manually de-asserted it, and got good values in registers. I submitted a small patch to the driver to enable this when the “wakeup-source” property is specified along with “m41t62”.
I am having troubles with I2C driver.
How to configure the Linux kernel/drivers/i2c/chips
Hello Tim, this is the entry for I2C in my device tree. Thank you again for your time and help! Anyway, exporting that function shouldn’t hurt: Board index All times are UTC.
If hwclock at the linux prompt works, your I2C bus pinux working. A Gossamer Threads company. Do you know what means this part of the.
In the command list you should see a line that looks like this:.