| Age | Commit message (Collapse) | Author |
|---|
|
F4t discovered that his freerunner panics on connect to his windows box.
This crude hack workarounds the problem.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Clean up debugging messages so that we don't see any output with loglevel=4
(default for Qi). This avoids slowing down suspend/resume by slow fb
output.
Checkpatch barks on this patch but i guess most of that debugging would
have to be changed prior to upstream submission anyway.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
This is because of commit
1f06c28eaa6e77384a366c3d2ab1ccdbb8a807e0
The BQ27000 Battery requires HDQ.
Otherwise the battery is not available at all.
Signed-off-by: Luca Capello <luca@pca.it>
|
|
As discussed on the ML, currently headset button reports "KEY_PAUSE
released" on press and "pressed" on release. For "pause" semantics it makes
sense but if someone thinks of that as of just another button, it'd be good
to have "pressed/released" events consistent with button press/release.
Luca Capello <luca@pca.it> suggested to change the button event to KEY_PLAY
and to invert the state to make it more consistent.
This trivial patch inverts button events for GTA03 KEY_PLUS and KEY_MINUS,
i'm not sure how undesirable that is. I can prepare an alternative that
preserves current behaviour on GTA03 per request.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Using HAL for E's battery gadget highlighted an oddity: the kernel exposed
last full charge property but didn't expose current charge property. This
resulted in the wrong computation of current battery capacity by E's gadget
(and probably other programs as well).
This patch exposes a corresponding bq27000 register to make E battery
gadget happy (it is still not showing correct values because of bugs in HAL
resulting in 3 batteries (apm emulation and usb supply being bogus here)
instead of one).
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
This patch adds a call to cancel_delayed_work before a call
to schedule_delayed_work.
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
Signed-off-by: Daniel Willmann <daniel@totalueberwachung.de>
|
|
Machines that do not route the USB vbus signal to a GPIO can use this
mechanism as an alternate way for the udc driver to detect the usb
connect/disconnect state, which is useful (for example) to enable the
link up/down state to be determined for the g_ether gadget.
Signed-off-by: Mike Westerhof <mwester@dls.net>
|
|
The g_ether USB gadget driver currently decides whether or not there's a
link to report back for eth_get_link based on if the USB link speed is
set. The USB gadget speed is however often set even before the device is
enumerated. It seems more sensible to only report a "link" if we're
actually connected to a host that wants to talk to us. The patch below
does this for me - tested with the PXA27x UDC driver.
Signed-off-by: Jonathan McDowell <noodles@earth.li>
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
Avoid a kernel panic during an early call
to the pcf50633_mbc_get_status function.
|
|
This patch fixes a linking failure in the Glamo GPIO SPI bitbang support.
Signed-off-by: Rask Ingemann Lambertsen <rask@sygehus.dk>
|
|
This patch fixes some indentation which was off by one and converts
spaces to tabs.
Signed-off-by: Rask Ingemann Lambertsen <rask@sygehus.dk>
|
|
Small patch to add /sys/class/power_supply/battery/present.
You must not run a GTA01 without battery thus it is always 1.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
resources
Call unbind() hook of the gadget so that it can properly release its
resources. This fixes bug http://docs.openmoko.org/trac/ticket/2240
("removing/reloading g_ether not working"). All other instances of
usb_gadget_unregister_driver in Linux already call unbind() so it is
bit odd s3c2410_udc.c did not do so.
Signed-off-by: Timo Juhani Lindfors <timo.lindfors@iki.fi>
|
|
This patch adds the call to the worker in
bq27000_battery_external_power_changed. Now (un)plugging the USB cable
effects the battery status soon. I don't know if it is possible call
the status change directly.
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
Signed-off-by: Daniel Willmann <daniel@totalueberwachung.de>
|
|
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Distributions that use Xorg will not need the workaround at
all and now they can disable it.
Updated configurations to enable it by default.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
~ Cleanup of a redundant call I introduced before.
~ Removed useless assignation.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
To disable the workaround at run-time run:
echo 0 > /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.9/glamo3362.0/glamo-fb.0/xglamo_hack
I guess I should add a compile option now to completely disable the workaround but let's call
this an enhancement and let's close the bug now.
By default the workaround is enabled.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
Reported-by: Timo Juhani Lindfors <timo.lindfors@iki.fi>
|
|
issue""
This reverts commit aa2dbc74bed8cf60e591c654ba1882011b9a8ece.
Reverting the revert. Sorry for the noise.
Check:
http://lists.openmoko.org/pipermail/openmoko-kernel/2009-April/010023.html
|
|
This reverts commit bd4b7e8e84ab43a13a4620b001d52d373c2122b3 which brought
WSOD back for some devices.
It was reported that the problem does not happen with Qi and it
seem it is good news. See:
https://docs.openmoko.org/trac/ticket/2274
Conflicts:
drivers/video/display/jbt6k74.c
|
|
Disabled additional debugging introduced
in 70b36104ab8c03f5be6d03344214d09447d9d4a8
|
|
Changing dev_info => dev_dbg.
Signed-off-by: Tim Niemeyer <tim.niemeyer@mastersword.de>
|
|
This closes bug #2267.
Signed-off-by: Mike Westerhof <mwester@dls.net>
|
|
Cleaned unnecessary debugging output.
Signed-off-by: Nicolas Dufresne <nicolas.dufresne@gmail.com>
|
|
Re-enable usbmode attribute.
It was disabled by 70b36104ab8c03f5be6d03344214d09447d9d4a8.
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Cleanup code of ohci-s3c2410.
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Space transition between sleep-in and sleep-out of at least
120 ms as mentionned in the spec. Also, made sure the LCM
is moved into sleep state before the pixel clock is turned off.
To do so, I've modified glamo-fb to send FB_BLANK_POWERDOWN before
turning off the pixel clock. Also fixed various violation of coding
style. This patch should reduce the risk of white screen.
Signed-off-by: Nicolas Dufresne <nicolas.dufresne@gmail.com>
|
|
A network device is supposed to disable its internals in the "close"
function. Doing so affords us protection against various races,
including the ioctl vs. rfkill conflict reported by Michael.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Reported-by: Michael Trimarch <michael@panicking.kicks-ass.org>
|
|
According to the PCF50606 manual, the issues resoved by commit
cc1663fc922c03feb0d7bbb8b18d62fbac0128de also exists there.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Reported-by: Rask Ingemann Lambertsen <rask@sygehus.dk>
|
|
This is loosely based on a patch by Ivan Petrov.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Reported-by: Ivan Petrov <ivan_p@hotbox.ru>
|
|
"pdata" is NULL on GTA01 and you oops.
Revised patch, this time with if(..) instead of #ifdef
Signed-off-by: Tim Niemeyer <tim.niemeyer@mastersword.de>
|
|
IDs 0 and 1 are AR6002, not AR6001. This is based on a patch by
Ivan Petrov, but it differs in leaving the IDs in
include/linux/mmc/sdio_ids.h
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Reported-by: Ivan Petrov <ivan_p@hotbox.ru>
|
|
e2c0650efa751a6a2220618695fa41a2a5e7d23c introduced a platform-specific
hack to check if the MMC driver and hardware handle busy signaling from
the device properly.
Since this seems to be the case, we can revert this hack now.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch cleans up a little after Ivan's netif_queue_stop fix.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch resolves the following issue:
http://lists.openmoko.org/pipermail/openmoko-kernel/2009-March/009643.html
Changed: prevent rescheduling network queue at interface opened/connected.
Removed: wake network queue at transmit complete.
Added: wake network queue at packet queue limit not reached.
Signed-off-by: Ivan Petrov <ivan_p@hotbox.ru>
|
|
... and check the return value in ar6000_activate.
[ Werner: changed ___FUNCTION__ to __func__ ]
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
platform_device_add_data copies the data, so no need for
kmalloc.
Signed-off-by: Tim Niemeyer <reddog@mastersword.de>
|
|
Watchdog and RTC entries were missing.
Signed-off-by: Tim Niemeyer <reddog@mastersword.de>
|
|
Signed-off-by: Tim Niemeyer <reddog@mastersword.de>
|
|
Signed-off-by: Werner Almesberger <werner@openmoko.org>
Reported-by: Tim Niemeyer <tim.niemeyer@mastersword.de>
|
|
[ Werner: Documentation/CodingStyle lines 166 and 448, put blank line after
local variables. ]
Signed-off-by: Tim Niemeyer <reddog@mastersword.de>
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Tim Niemeyer <reddog@mastersword.de>
|
|
Get resume by AUX to work.
Signed-off-by: Tim Niemeyer <reddog@mastersword.de>
|
|
The kernel would fail to link because cfb_fillrect, cfb_copyarea and
cfb_imageblit weren't build. This patch fixes it.
Signed-off-by: Rask Ingemann Lambertsen <rask@sygehus.dk>
|
|
This patch fixes the issues of RNDIS on the Openmoko Freerunner (and
subsequently Windows networking with the Freerunner). It arises from the
case where a stall is being issued by the upper level RNDIS driver to
the s3c2410_udc.c in the 2.6.28 series driver and it not being handled
correctly. This patch changes the RNDIS driver to send zero-length
packets instead of a stall, a condition that allowed the udc driver to
function correctly in 2.6.24 series kernels.
Further investigation into the udc driver is recommended. I am currently
looking into it to be able to use the Android ADB gadget driver, which
currently has stability issues using the underlying udc on both Linux
and Windows (although, it's possible that the Android ADB gadget has
problems).
Traces and logs of the USB traffic are available upon request. Thanks to
Aric at SDG Systems for all of his work on this matter.
Regards,
Brian Code
From de386af349bbfe1ad6d45c810185123975888d8d Mon Sep 17 00:00:00 2001
From: Aric D. Blumer <aric@sdgsystems.com>
Date: Mon, 16 Mar 2009 16:04:02 -0600
Subject: [PATCH] Zero packet length detection for RNDIS fix. Migrated from 2.6.24 series kernel
Signed-off-by: Aric D. Blumer <aric@sdgsystems.com>
Signed-off-by: Brian Code <Brian.Code@koolu.com>
|
|
If no battery is connected, we periodically get a burst of HDQ error
messages (at least on 3D7K), interrupting whatever we're doing on
the console.
This patch reduces this to only one message per sequence of errors,
and one more message if communication with HDQ is successful later.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch explicitly enabled to "camif" clock, to make the driver
work again with Qi commit a24b5fcf84d2cf633a3f660edd23fa4c2a3da231.
Note that this is not fully tested since the Qi change also broke
the LCM driver.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This dirty hack adds camera activation/deactivation on open/close.
This code will have to move to a machine/platform area later. The
general driver is the wrong place for it.
It also removes the unconditional activation and moves the domain
setting to the rest of the power control code. (Thanks, Andy !)
Note that opening the camera now always takes about 20 seconds
until the settings are downloaded, not just on the first open.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
