Author Topic: Kernel 3.4.91  (Read 21332 times)

Offline ratin

  • Jr. Member
  • **
  • Posts: 86
  • Karma: +0/-0
    • View Profile
Re: Kernel 3.4.91
« Reply #15 on: June 10, 2014, 11:57:51 pm »
I am using cubieboard2, I have been noticing an issue with the AXP 209 hanging on DRAM init if the board is abruptly shutdown and does not clear up until shutdown for 30 seconds or more before re-powering. I wonder if AXP209's timing is configured improperly or not. I do see this message regarding AXP209 config failed (uning is a typo I guess? :-)

(note that with old kernel 3.3..0+ I used to see AXP timing config data)

<6>axp_mfd 0-0034: AXP (CHIP ID: 0x41) detected
[    2.705090] axp_mfd 0-0034: AXP (CHIP ID: 0x41) detected
<6>axp_mfd 0-0034: AXP internal temperature monitoring enabled
[    2.716224] axp_mfd 0-0034: AXP internal temperature monitoring enabled
[AXP]axp driver uning configuration failed(342)
[    2.728043] [AXP]axp driver uning configuration failed(342)
[AXP]power_start = 0
[    2.735551] [AXP]power_start = 0
<4>i2c i2c-0: Invalid probe address 0x00
[    2.742456] i2c i2c-0: Invalid probe address 0x00
<6>I2C: i2c-0: AW16XX I2C adapter
[    2.750212] I2C: i2c-0: AW16XX I2C adapter
<4>i2c i2c-1: Invalid probe address 0x00
[    2.758360] i2c i2c-1: Invalid probe address 0x00
<6>I2C: i2c-1: AW16XX I2C adapter
[    2.766131] I2C: i2c-1: AW16XX I2C adapter
<4>i2c i2c-2: Invalid probe address 0x00
[    2.774267] i2c i2c-2: Invalid probe address 0x00
<6>I2C: i2c-2: AW16XX I2C adapter
[    2.782037] I2C: i2c-2: AW16XX I2C adapter
<6>usb 4-1: new low-speed USB device number 2 using sw-ohci
[    2.811112] usb 4-1: new low-speed USB device number 2 using sw-ohci
[cedar dev]: install start!!!
[    2.849151] [cedar dev]: install start!!!
[cedar dev]: install end!!!
[    2.856429] [cedar dev]: install end!!!
----- avs_dev driver load... ----
[    2.863684] ----- avs_dev driver load... ----
-----      register iomem      ----
[    2.871965] -----      register iomem      ----
--- avs_dev driver load ok!! -----
[    2.880516] --- avs_dev driver load ok!! -----
[ace_drv] start!!!
[    2.887068] [ace_drv] start!!!
[ace_drv] init end!!!
[    2.892513] [ace_drv] init end!!!
[pa_drv] start!!!
[    2.897510] [pa_drv] start!!!
[pa_drv] init end!!!
[    2.902720] [pa_drv] init end!!!
<6>axp20_ldo1: 1300 mV
[    2.908373] axp20_ldo1: 1300 mV
<6>axp20_ldo2: 1800 <--> 3300 mV at 3000 mV
[    2.916811] axp20_ldo2: 1800 <--> 3300 mV at 3000 mV
<6>axp20_ldo3: 700 <--> 3500 mV at 2800 mV
[    2.926959] axp20_ldo3: 700 <--> 3500 mV at 2800 mV
<6>axp20_ldo4: 1250 <--> 3300 mV at 2800 mV
[    2.937297] axp20_ldo4: 1250 <--> 3300 mV at 2800 mV
<6>axp20_buck2: 700 <--> 2275 mV at 1400 mV
[    2.947503] axp20_buck2: 700 <--> 2275 mV at 1400 mV
<6>axp20_buck3: 700 <--> 3500 mV at 1250 mV
[    2.957739] axp20_buck3: 700 <--> 3500 mV at 1250 mV
<6>axp20_ldoio0: 1800 <--> 3300 mV at 2800 mV
[    2.967703] axp20_ldoio0: 1800 <--> 3300 mV at 2800 mV
<6>input: axp20-supplyer as /devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/input/input0
[    2.982539] input: axp20-supplyer as /devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/input/input0
<4>axp20_ldo2: Failed to create debugfs directory
[    3.010698] axp20_ldo2: Failed to create debugfs directory
<6>sunxi_wdt: sunxi WatchDog Timer Driver v1.0

Anybody else see this?





On 3.3.0+ kernel I used to see these:
===============================================================================

[    0.243001] axp config [pmu_para] [pmu_used] : 1

[    0.243015] axp config [pmu_para] [pmu_twi_id] : 0

[    0.243026] axp config [pmu_para] [pmu_irq_id] : 32

[    0.243037] axp config [pmu_para] [pmu_twi_addr] : 52

[    0.243048] axp config [pmu_para] [pmu_battery_rdc] : 120

[    0.243060] axp config [pmu_para] [pmu_battery_cap] : 2100

[    0.243071] axp config [pmu_para] [pmu_init_chgcur] : 300

[    0.243082] axp config [pmu_para] [pmu_suspend_chgcur] : 1000

[    0.243094] axp config [pmu_para] [pmu_resume_chgcur] : 300

[    0.243106] axp config [pmu_para] [pmu_shutdown_chgcur] : 1000

[    0.243117] axp config [pmu_para] [pmu_init_chgvol] : 4200

[    0.243129] axp config [pmu_para] [pmu_init_chgend_rate] : 15

[    0.243141] axp config [pmu_para] [pmu_init_chg_enabled] : 1

[    0.243152] axp config [pmu_para] [pmu_init_adc_freq] : 100

[    0.243163] axp config [pmu_para] [pmu_init_adc_freqc] : 100

[    0.243175] axp config [pmu_para] [pmu_init_chg_pretime] : 50

[    0.243187] axp config [pmu_para] [pmu_init_chg_csttime] : 720

[    0.243200] axp config [pmu_para] [pmu_bat_para1] : 0

[    0.243211] axp config [pmu_para] [pmu_bat_para2] : 0

[    0.243222] axp config [pmu_para] [pmu_bat_para3] : 0

[    0.243233] axp config [pmu_para] [pmu_bat_para4] : 0

[    0.243244] axp config [pmu_para] [pmu_bat_para5] : 5

[    0.243255] axp config [pmu_para] [pmu_bat_para6] : 11

[    0.243266] axp config [pmu_para] [pmu_bat_para7] : 13

[    0.243278] axp config [pmu_para] [pmu_bat_para8] : 15

[    0.243289] axp config [pmu_para] [pmu_bat_para9] : 19

[    0.243300] axp config [pmu_para] [pmu_bat_para10] : 32

[    0.243311] axp config [pmu_para] [pmu_bat_para11] : 50

[    0.243322] axp config [pmu_para] [pmu_bat_para12] : 58

[    0.243334] axp config [pmu_para] [pmu_bat_para13] : 71

[    0.243346] axp config [pmu_para] [pmu_bat_para14] : 81

[    0.243357] axp config [pmu_para] [pmu_bat_para15] : 89

[    0.243368] axp config [pmu_para] [pmu_bat_para16] : 100

[    0.243379] axp config [pmu_para] [pmu_usbvol_limit] : 1

[    0.243391] axp config [pmu_para] [pmu_usbvol] : 4000

[    0.243402] axp config [pmu_para] [pmu_usbcur_limit] : 0

[    0.243415] axp config [pmu_para] [pmu_usbcur] : 0

[    0.243427] axp config [pmu_para] [pmu_pwroff_vol] : 3300

[    0.243438] axp config [pmu_para] [pmu_pwron_vol] : 2900

[    0.243449] axp config [target] [dcdc2_vol] : 1400

[    0.243460] axp config [target] [dcdc3_vol] : 1250

[    0.243470] axp config [target] [ldo2_vol] : 3000

[    0.243481] axp config [target] [ldo3_vol] : 2800

[    0.243492] axp config [target] [ldo4_vol] : 2800

[    0.243503] axp config [pmu_para] [pmu_pekoff_time] : 6000

[    0.243514] axp config [pmu_para] [pmu_pekoff_en] : 1

[    0.243525] axp config [pmu_para] [pmu_peklong_time] : 1500

[    0.243537] axp config [pmu_para] [pmu_pwrok_time] : 64

[    0.243551] axp config [pmu_para] [pmu_pwrnoe_time] : 2000

[    0.243562] axp config [pmu_para] [pmu_intotp_en] : 1

[    0.243574] axp config [pmu_para] [pmu_pekon_time] : 1000


And these :
===========================================================================


[  2.447684] pmu_pekoff_time = 6000

[    2.451117] pmu_pekoff_en = 1

[    2.454081] pmu_peklong_time = 1500

[    2.457567] pmu_pekon_time = 1000

[    2.461096] pmu_pwrok_time = 64

[    2.464239] pmu_pwrnoe_time = 2000

[    2.467638] pmu_intotp_en = 1

[    2.471259] [AXP]POWER20_OFF_CTL:2044-->0x42

[    2.476123] POWER20_PEK_SET:2061-->0x9d

[    2.480598] POWER20_PEK_SET:2072-->0x9d

[    2.485033] POWER20_PEK_SET:2081-->0x9d

[    2.489460] POWER20_PEK_SET:2092-->0x9d

[    2.493905] POWER20_PEK_SET:2104-->0x9d

[    2.498333] POWER20_HOTOVER_CTL:2113-->0xad

[    2.507069] [AXP]last_rest_vol = 0, now_rest_vol     = 100

[    2.510076] usb 5-1: new low-speed USB device number 2 using sw-ohci

[    2.520643] [AXP]Cur_CoulombCounter  = 0

[    2.524479] [AXP]charger->rest_vol = 100




« Last Edit: June 11, 2014, 12:22:06 am by ratin »

Offline ratin

  • Jr. Member
  • **
  • Posts: 86
  • Karma: +0/-0
    • View Profile
Re: Kernel 3.4.91
« Reply #16 on: June 11, 2014, 12:18:26 am »
Also in /proc/cpuinfo , Serial is set to 0000000000000000
but it used to be a valid cpu ID on 3.3.0+ kernel

Offline rose28357

  • Hero Member
  • *****
  • Posts: 567
  • Karma: +28/-0
    • View Profile
Re: Kernel 3.4.91
« Reply #17 on: June 11, 2014, 05:41:05 am »
I have updated my base to Kernel 3.4.92.

(It's all added to my site ( http://www.danand.de ) and in the binary sections at http://dl.danand.de/ )
Is it a A20 Kernel ? Maybe you should extend the Download-Filename of your Kernel.

Offline D_NRW

  • Jr. Member
  • **
  • Posts: 65
  • Karma: +3/-0
    • View Profile
    • Dan-And
Re: Kernel 3.4.91
« Reply #18 on: June 11, 2014, 05:44:27 am »
Good point! Yes, it is A20 only.

Offline db260179

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: Kernel 3.4.91
« Reply #19 on: June 12, 2014, 05:29:42 pm »
Hi All,

I've created a sunxi patch against a vanilla 3.4.92 linux kernel - this is if you dont want to use git to clone the kernel repo (plus it is outdated)

http://multiupload.biz/gy8rn6mrbji6/sunxi-patch-92.tar_MultiUpload.biz.gz.html

It has various extra patches applied - axp20 human readable power readings, ax881879 usb 3.0 nic driver, builddeb(create an automated debian kernel package) that understands uImage files and modifies /boot/uEnv.txt with correct kernel name.

Download the above patch and https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.4.92.tar.gz

Extract both into the same folder - then cd into the kernel directory i.e.

cd linux-3.4.92
then
patch -p1 < ../sunxi-92.patch

Follow http://linux-sunxi.org/Linux_Kernel#Compilation - skip the git clone part

Voila! you linux kernel with the latest patches and compatible with Cubieboard2,Cubietruck!

Let me you know what you think?
« Last Edit: June 12, 2014, 05:38:41 pm by db260179 »

Offline D_NRW

  • Jr. Member
  • **
  • Posts: 65
  • Karma: +3/-0
    • View Profile
    • Dan-And
Re: Kernel 3.4.91
« Reply #20 on: June 12, 2014, 05:40:21 pm »
I have updated my base to Kernel 3.4.92.

(It's all added to my site ( http://www.danand.de ) and in the binary sections at http://dl.danand.de/ )

The Kernel devs are busy at the moment ... Updated (again) to 3.4.93.

You can see and downlooad the sources at: https://github.com/dan-and/linux-sunxi/tree/dan-3.4.93
Binaries as usual: http://dl.danand.de/
« Last Edit: June 13, 2014, 06:24:59 am by D_NRW »

Offline db260179

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: Kernel 3.4.91
« Reply #21 on: June 13, 2014, 07:10:34 am »
Indeed they are!

3.4.92 at least has the tty vulnerability fixed.

Offline ratin

  • Jr. Member
  • **
  • Posts: 86
  • Karma: +0/-0
    • View Profile
Re: Kernel 3.4.91
« Reply #22 on: June 13, 2014, 09:59:39 pm »
any patch for /proc/cpuinfo serial number fix?

Offline D_NRW

  • Jr. Member
  • **
  • Posts: 65
  • Karma: +3/-0
    • View Profile
    • Dan-And
Re: Kernel 3.4.91
« Reply #23 on: June 27, 2014, 02:52:05 am »
I have updated my kernel sources and binary build to 3.4.95 (see http://www.danand.de/ )

Offline D_NRW

  • Jr. Member
  • **
  • Posts: 65
  • Karma: +3/-0
    • View Profile
    • Dan-And
Re: Kernel 3.4.91
« Reply #24 on: July 01, 2014, 10:32:24 am »
And again updated to 3.4.96

Offline cubieplayer

  • Full Member
  • ***
  • Posts: 177
  • Karma: +22/-1
    • View Profile
Cubian:http://cubian.org/ Cubian  Helpdesk:https://github.com/cubieplayer/Cubian/issues

Offline D_NRW

  • Jr. Member
  • **
  • Posts: 65
  • Karma: +3/-0
    • View Profile
    • Dan-And
Re: Kernel 3.4.91
« Reply #26 on: July 07, 2014, 07:32:48 am »
3.4.97 done :)

Offline epierre

  • Newbie
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: Kernel 3.4.91
« Reply #27 on: July 25, 2014, 01:22:44 am »
Hello,

  I am currently have an issue while updating to Debian Sid about some kernel flags, see: http://www.cubieforums.com/index.php?topic=2828.0

  It appears that only one is missing from your kernel. Would it be possible to have it included so everyone could benefit from it ?

  Thanks in advance,

    Emmanuel

P.S. I'm still compiling from your repository to see if it solves  my issue,

Offline epierre

  • Newbie
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: Kernel 3.4.91
« Reply #28 on: July 25, 2014, 05:17:59 pm »
Hello,

  the ap6210 firmware is missing, so compilation of modules cannot be done.

  when added from another version, the nvram_apxxx.txt must be renamed to nvram_ap6210.txt

Offline D_NRW

  • Jr. Member
  • **
  • Posts: 65
  • Karma: +3/-0
    • View Profile
    • Dan-And
Re: Kernel 3.4.91
« Reply #29 on: July 29, 2014, 05:49:51 am »
epierre:
Where is the ap6210 firmware missing ? Please be a bit more precise.

Cheers,
Daniel