debug mag3110 while magd did not run

jakiewen — Mon, 21 Aug 2017 10:27:06 GMT

My system is Android 7.1 with kernel 4.1.After mag3110 driver is porting,log as below:

2-000e supply vdd not found, using dummy regulator //启动log
2-000e supply vddio not found, using dummy regulator
mag3110 2-000e: check mag3110 chip ID
input: FreescaleMagnetometer as /devices/virtual/input/input2
input: eCompass as /devices/virtual/input/input3
mag3110 2-000e: mag3110 is probed

I found the input event lost while I use getevent to catch them.

sabresd_6dq:/ # getevent
add device 1: /dev/input/event3
name: "eCompass"
add device 2: /dev/input/event2
name: "FreescaleMagnetometer"
add device 3: /dev/input/event1
name: "goodix-ts"
could not get driver version for /dev/input/mice, Not a typewriter
add device 4: /dev/input/event0
name: "tw8834"

After that, I found magd did not run :

init: Starting service 'magd'... //magd start by init progress
init: Starting service 'gatekeeperd'...
type=1400 audit(4.500:5): avc: denied { getattr } for pid=176 comm="mediadrmserver" path="/vendor" dev="rootfs" ino=50
init: Starting service 'perfprofd'...
(stk) :ldisc_install = 1
type=1400 audit(4.550:6): avc: denied { getattr } for pid=170 comm="audioserver" path="/vendor" dev="rootfs" ino=55910
type=1400 audit(4.570:7): avc: denied { getattr } for pid=175 comm="mediacodec" path="/vendor" dev="rootfs" ino=5591 0
android_work: did not send uevent (0 0 (null))
configfs-gadget gadget: unbind function 'mtp'/d2bc9a00
configfs-gadget gadget: unbind function 'Function FS Gadget'/d2f4d024
android_work: did not send uevent (0 0 (null))
configfs-gadget gadget: unbind function 'mtp'/d2bc9a00
configfs-gadget gadget: unbind function 'Function FS Gadget'/d2f49924
type=1400 audit(4.580:8): avc: denied { getattr } for pid=171 comm="cameraserver" path="/vendor" dev="rootfs" ino=5590
type=1400 audit(4.710:9): avc: denied { getattr } for pid=180 comm="magd" path="/vendor" dev="rootfs" ino=5591 sconte0
wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
healthd: No battery devices found
wlcore: loaded
wlcore: driver version: R8.6_SP1
init: avc: denied { set } for property=telephony.lteOnCdmaDevice pid=168 uid=0 gid=1001 scontext=u:r:rild:s0 tconte0
init: sys_prop: permission denied uid:0 name:telephony.lteOnCdmaDevice
init: Service 'magd' (pid 180) exited with status 255 //magd exited

So can you give me some advice to fix this problem?

Re: debug mag3110 while magd did not run

diegoadrian — Thu, 24 Aug 2017 20:22:30 GMT

Hello,

Can you please use I2C tools, and see if you have a connection between the mag3110 and the i.MX6?

https://community.nxp.com/docs/DOC-1477

Best Regards,

Diego.

Re: debug mag3110 while magd did not run

jakiewen — Fri, 25 Aug 2017 02:13:32 GMT

Hello Diego,

Thanks for your reply.

The communication between mag3110 and the i.MX6 is normal，here is the start-up log：

mag3110 2-000e: check mag3110 chip ID
mag3110 2-000e: wjk.........read chip ID is 0xc4! //The chip id is read by i2c
input: FreescaleMagnetometer as /devices/virtual/input/input3
input: eCompass as /devices/virtual/input/input4
mag3110 2-000e: mag3110 is probed

Can you help me to judge why magd failed to run?

i.MX Processors中的主题 Re: debug mag3110 while magd did not run

debug mag3110 while magd did not run

Re: debug mag3110 while magd did not run

Re: debug mag3110 while magd did not run