<div dir="ltr"><div style="font-size:12.8000001907349px">>Thanks for the manual. Now I believe the client address of this chip should be set to either 0x4a or 0x4b. The only problem left is how do I >know what is the ADDR_SEL status? Since I see in the driver code there is no a line that is setting up this pin, so can I assume that the >ADDR_SEL is hard-wired on my board and I just need to ask my hardware engineer to do a measure on the pin, right?</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">You have to see the h/w schematic of the controller for this.Other way is i2c detect utility which I mentioned above.Run it and see if the address is 0x4a or 0x4b.</div><div style="font-size:12.8000001907349px">Yes you can definitely ask the hardware engineer.</div><div style="font-size:12.8000001907349px"> </div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">>Another not so related thing is that I also noticed that there are still other two addresses that can be used to do firmware upgrading. I just >read this from the driver code and also want to know if it is necessary in my case to concern about downloading a firmware to the chip? I >really hope things won't go such complicated and the chip should simplify work as long as I correctly setup and load the linux driver for it. >Do you also has an idea about this?</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">I think that means your controller has a bootloader (and hence other two address - may be one for ADDR_SEL - high and another for ADDR_SEL - low ) and the firmware can be updated via Host as well.Are you using any kernel firmware update interface?something like this : <a href="http://www.makelinux.net/ldd3/chp-14-sect-8">http://www.makelinux.net/ldd3/chp-14-sect-8</a> .n that case you must be having the bin file which needs to be placed in the /etc/firmware directory from which your host will pick the file and update the cntroller firmware.But be aware that you must know what protocol is being used by your hardware for this updation(ymodem,xmodem,etc).</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 8, 2015 at 7:59 PM, Woody Wu <span dir="ltr"><<a href="mailto:narkewoody@gmail.com" target="_blank">narkewoody@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Raul,<div><br></div><div>Thanks for the manual. Now I believe the client address of this chip should be set to either 0x4a or 0x4b. The only problem left is how do I know what is the ADDR_SEL status? Since I see in the driver code there is no a line that is setting up this pin, so can I assume that the ADDR_SEL is hard-wired on my board and I just need to ask my hardware engineer to do a measure on the pin, right?</div><div><br></div><div>Another not so related thing is that I also noticed that there are still other two addresses that can be used to do firmware upgrading. I just read this from the driver code and also want to know if it is necessary in my case to concern about downloading a firmware to the chip? I really hope things won't go such complicated and the chip should simplify work as long as I correctly setup and load the linux driver for it. Do you also has an idea about this?</div><div><br></div><div>Many thanks.</div><div><span class="HOEnZb"><font color="#888888">-woody </font></span><div><div class="h5"><br><br>On Saturday, 8 August 2015, Raul Piper <<a href="mailto:raulpblooper@gmail.com" target="_blank">raulpblooper@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Woody, <div>Form the attached datasheet section 4.3.2 the address seems to be : 0x4A and 0x4B depending upon the ADDR_SEL line(low or high respectively).</div><div>Please check in the driver code is the address is 7 bit or 8 bit before using the above address.</div><div>Also you can check the i2c utilities : <a href="http://www.lm-sensors.org/wiki/I2CTools" target="_blank">http://www.lm-sensors.org/wiki/I2CTools</a> to check the address of the devices connected with your SoC.on running i2c detect (with appropriate arguments) you will come to know about the address of the devices which you can verify with the address you put in the driver code.</div><div>Thanks and Rgds,</div><div>Rp</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 8, 2015 at 10:09 AM, Woody Wu <span dir="ltr"><<a>narkewoody@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am recently porting an i2c touchscreen to my board which runs ARM linux 3.1. I found I need to setup some device platform data for the i2c chip, among which there is an 'addr' field that I dont understand. I search the device driver code, then I know the address will be used when compositing some i2c messages. My question is that how do I know what the address I should fill in the field? The datasheet of the device doesn't provide an answer. By the way, the touchscreen is actually an Atmel mXT224 i2c multi-touch screen panel, which is wired to a Samsung S3C i2c controller in my SoC.<div><br></div><div>Thanks in advance!</div><span><font color="#888888"><div>-woody</div><br><br>-- <br>Sent from Gmail Mobile<br>
</font></span><br>_______________________________________________<br>
Kernelnewbies mailing list<br>
<a>Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div></div><div class="HOEnZb"><div class="h5"><br><br>-- <br>Sent from Gmail Mobile<br>
</div></div></blockquote></div><br></div>