Send buglog mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:

   1. Openmoko Bug #2293: linux/andy-tracking: gps does not always
      honor     power_on (Openmoko Public Trac)
   2. Re: Openmoko Bug #2277: Wireless does not work with the
      2.6.29 kernel (Openmoko Public Trac)
   3. Re: Openmoko Bug #2293: linux/andy-tracking: gps does not
      always    honor power_on (Openmoko Public Trac)
--- Begin Message ---
#2293: linux/andy-tracking: gps does not always honor power_on
-----------------------------+----------------------------------------------
 Reporter:  lindi            |          Owner:  openmoko-kernel    
     Type:  defect           |         Status:  new                
 Priority:  normal           |      Milestone:                     
Component:  System Software  |        Version:  unspecified        
 Severity:  normal           |       Keywords:  kernel gps power_on
 Haspatch:  0                |      Blockedby:                     
Estimated:                   |    Patchreview:                     
 Blocking:                   |   Reproducible:  always             
-----------------------------+----------------------------------------------
 Steps to reproduce:
 1) echo 1 > /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.7/neo1973
 -pm-gps.0/power_on
 2) echo mem > /sys/power/state
 3) cat /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.7/neo1973-pm-
 gps.0/power_on
 4) echo 1 > /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.7/neo1973
 -pm-gps.0/power_on
 5) cat /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.7/neo1973-pm-
 gps.0/power_on

 Expected results:
 3) 1 or 0, both are ok to me
 5) 1

 Actual results:
 3) 0
 5) 0

 More info:
 6) I can start the GPS chip if I first write 0 to power_on and then write
 1 there.
 7) I am using andy-tracking 9ecc089861ab238e
 8) I think the bug is that neo1973_gps.power_was_on is updated only in
 power_gps_write() but gta01_pm_gps_suspend calls gps_pwron_set(0) directly
 and bypasses this.
 9) My understanding:
 * cat power_on returns 0
 * since gps_pwron_get returns 0
 * since regulator_is_enabled(neo1973_gps.regulator[GTA02_GPS_REG_RF_3V])
 returns 0

 * echo 1 > power_on does not enable regulator
 * since neo1973_gps.power_was_on is set

 * => power_was_on state is wrong.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2293>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2277: Wireless does not work with the 2.6.29 kernel
---------------------+------------------------------------------------------
 Reporter:  arhuaco  |          Owner:  openmoko-devel      
     Type:  defect   |         Status:  new                 
 Priority:  normal   |      Milestone:  stable-kernel-2009.1
Component:  unknown  |        Version:                      
 Severity:  normal   |       Keywords:                      
 Haspatch:  0        |      Blockedby:                      
Estimated:           |    Patchreview:                      
 Blocking:           |   Reproducible:  sometimes           
---------------------+------------------------------------------------------

Comment(by lindi):

 I did a rought git bisection plan:

  broken (lindi tested) 9ecc089861ab238e  Sat May 23 17:54:00 2009
  broken (nicola.mfb tested) 81c61a7d1abb03aecd13f5 Thu Apr 16 09:18:51
 2009
  broken (werner tested) 9029dff1f370018665a6e2999632a34fd Thu Feb 5
 17:01:56 2009
   suspicious commits:
    1184dc21448404d2e274ce5a5a95b98878a624f Mon Jan 19 01:18:06 2009 clean
 up GTA02 WLAN power control
    e2c0650efa751a6a2220618695fa41a2a5e7d23 Wed Jan 14 11:55:56 2009 WLAN:
 --power maxperf shot into the dark
    bd84864b5a4fdfbe927b827a215f325a8b25671 Mon Jan 12 09:04:48 2009 Change
 AR6k driver to module and remove CONFIG_MD
    4836494d233cd34fe194ff2040d62e4109067d7 Mon Jan 12 09:04:45 2009 AR6k:
 don't make a fuss if SIOCGIWSCAN returns no nodes
     I'll try to revert this and see if it changes anything
  working (lindi tested for 2+ months) b8b36e5ec3db71d5 Wed Jan 7 09:39:02
 2009

 However the problem is that I still don't have a reliable way to reproduce
 this bug and I can't make sense of the panic message.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2277#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2293: linux/andy-tracking: gps does not always honor power_on
-----------------------------+----------------------------------------------
 Reporter:  lindi            |          Owner:  openmoko-kernel    
     Type:  defect           |         Status:  new                
 Priority:  normal           |      Milestone:                     
Component:  System Software  |        Version:  unspecified        
 Severity:  normal           |       Keywords:  kernel gps power_on
 Haspatch:  0                |      Blockedby:                     
Estimated:                   |    Patchreview:                     
 Blocking:                   |   Reproducible:  always             
-----------------------------+----------------------------------------------

Comment(by PaulFertser):

 Lindi, afaict the intent of power_was_on is to keep information about
 power state during suspend (while GPS is actually unpowered). So
 power_was_on is correct here but ps_pwron_set should be able to power on
 the GPS regardless of its state (special care should be taken to not
 enable regulator twice, because regulators include reference counting).
 Sent to the ML is a tested patch that should solve the problem.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2293#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to