| Commit message (Collapse) | Author | Age |
| |
|
|
| |
Change-Id: I554641ab318ab7b6952ea6cbe3ac04f39431deae
|
| |
|
|
| |
Change-Id: I5d1d79949fe9da2fd97d0711e1d1a19b7a966cea
|
| |\
| |
| |
| | |
Change-Id: Iad54233a3575c0117f88ce7a1e89bfa639760f63
|
| | |
| |
| |
| | |
Change-Id: I7b1e5e87921ae0770f7783680c3dbcdbf6f257f3
|
| | |
| |
| |
| |
| |
| | |
This should fix some errors, panics in some individual cases.
Change-Id: I27ce41f0563378e03371724f8b044404c6e69b76
|
| | |
| |
| |
| | |
Change-Id: I74f0450e8f42032265b980b95f17b0b05d9dffa5
|
| | |
| |
| |
| | |
Change-Id: Ib67385354b1d6529d41198bfdcb1ecd092e9b98b
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This clearly fixes recording on targets where the bias pin was wrong. It may
also improve recording on targets where the bias voltage was wrong. I was unable
to find those parameters on the ZEN Mozaic, which fallback to default values.
Change-Id: Ifb5f823c9cbd01f0d9a80fa5d49d93972c8b7cfe
|
| | |
| |
| |
| |
| |
| |
| |
| | |
For some reason, there was a mismatch between the setting (decibel) and the
audiohw code (centicel). This resulted in a gain divided by 10. This may
explain why some people experienced low volume with the mic on the fuze+.
Change-Id: I138ac18dd93c36f43a7dfce735efc826405c598c
|
| | |
| |
| |
| |
| |
| | |
Hopefully this can help debugging alarm problems.
Change-Id: Id8c5603a6372744dfc62890443a37de2dd92a7c0
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- NOR driver (based on emCORE)
- read/write IM3 images
- read 'flsh' files
Change-Id: Ie0654e0d298affc0f47ed64b823767118bd1aa3f
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Based on emCORE.
Low level functions that do not depend on Rockbox kernel,
intended to be used by the bootloader, dualboot-installer,
RB drivers or other .dfu tools.
Change-Id: I3c616ded42260c6626bda23b7e580791981df61d
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Based on emCORE.
Low level functions that do not depend on Rockbox kernel,
intended to be used by the bootloader, dualboot-installer,
RB drivers or other .dfu tools.
Change-Id: Iad369627b55bf1778eab437424072f1a653e4db6
|
| | |
| |
| |
| |
| |
| | |
Targets: sansaclipplus, samsaclipv2, sansaclipzip, sansafuzev2.
Change-Id: I7773528a4e26707dd33fe9cb8948750d49570701
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Some rewrite with the intent to get ride of these random errors
appearing on some builds/devices (not much noticeable on RB but
can ruin bootloader builds).
- Error handling (ACK).
- IIC clock increased to be the same as in OF.
Change-Id: Idf8cfa3c230a0a61ec9c879bf6f0ea8b061a4607
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Add code to read USB D+/D- and accessory ADCs, it is shown in HW
debug menu, might be useful in future for RB and/or the bootloader
to identify external USB chargers.
Change-Id: Ia48ca5e06bb7ddc52bb55abedde6734653ce8dba
|
| | |
| |
| |
| | |
Change-Id: I839ba2191a5c52ef6f58fd4a273db628b690a05c
|
| | |
| |
| |
| | |
Change-Id: I0424d02196a6c5fb6d0185b007df5ece24b10b82
|
| | |
| |
| |
| | |
Change-Id: I8d1561bf4e239b55617a8d5075457a668e0c312c
|
| | |
| |
| |
| | |
Change-Id: I36aabb5cb9cfe2d8c4f8fbcea944efec58ef9671
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Based on g#844 and g#949, it is intended as a replacement for the
current s3c6400x USB driver.
The DesignWare USB OTG core is integrated into many SoC's, however
HW core version and capabilities (mainly DMA mode, Tx FIFO mode,
FIFO size and number of available IN/OUT endpoins) may differ:
CPU targets HW ver DMA NPTX FIFO FIFO sz #IN/OUT
-------- ------------- ------ --- --------- ------- -------
as3525v2 sansaclipplus 2.60a Yes Dedicated 0x535 4/4
sansaclipv2
sansaclipzip
sansafuzev2
s5l8701 ipodnano2g 2.20a Yes Shared 0x500 4/5
s5l8702 ipod6g 2.60a Yes Dedicated 0x820 7/7
ipodnano3g
s5l8720 ipodnano4g ? ? ? ? ?
Functionality supported by this driver:
- Device mode, compatible with USB 1.1/2.0 hosts.
- Shared FIFO (USB_DW_SHARED_FIFO) or dedicated FIFOs.
- No DMA (USB_DW_ARCH_SLAVE) or internal DMA mode.
- Concurrent transfers: control, bulk (usb_storage, usb_serial) and
interrupt (usb_hid).
Actually this driver is not used by any CPU, it will be enabled for
each individual CPU/target in next patches.
Change-Id: I74a1e836d18927a31f6977d71115fb442477dd5f
|
| | |
| |
| |
| | |
Change-Id: I8322c834a8c83761d995fc1cfb5c76b45d62893f
|
| | |
| |
| |
| | |
Change-Id: Iacb1ac768741f40a7b3ed39eb820bb228bbabd0a
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Based on emCORE.
Low level functions that do not depend on Rockbox kernel,
intended to be used by the bootloader, dualboot-installer,
RB drivers or other .dfu tools.
Change-Id: I3c616ded42260c6626bda23b7e580791981df61d
|
| |\ \
| | |
| | |
| | | |
Change-Id: I79f5a5dcfbe3ef7531558abac02fca129e9fb161
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Patch Set 1:
This bundle includes:
- USBOTG_DESIGNWARE driver based on g#844 and g#949
- USBOTG_DESIGNWARE for s5l8702 (Classic)
- USBOTG_DESIGNWARE for s5l8701 (Nano2G)
- USBOTG_DESIGNWARE for as3525v2 (enabled on Sansa Zip Clip)
- ALIGNED_BUFFER_QUICK_PATCH (usb_serial.c)
Preliminary version, needs to adjust some things and rework to
optimize in size.
Tested on Linux (USB_STORAGE, USB_HID and USB_SERIAL).
Known issues:
- n2g: panics when USB is extracted and then re-inserted quickly. This
only happens when "Error accessing playlist control file" is shown
(RB bug?).
Patch Set 2:
- Enable USBOTG_DESIGNWARE for sansaclipplus, sansaclipv2 and sansafuzev2,
these targets have never been tested.
- First round of optimizations, mainly tries to homogenize the names of
the endpoints and other small changes, functionality should be the same
as in the previous patch set.
Patch Set 3:
- Some rewrite/optimizations, functionality should be the same as in the
previous patch set.
Patch Set 4:
- n2g: enable EPROTO workaround, EPROTO errors are produced while the
device is receiving bulk data, they are highly mitigated running the
PHY @60 MHz. but it seems that occasionally the problem still persists.
This workaround tries to solve the issue by flushing the Rx FIFO/queue
that were corrupted by the received data.
- Some minor miscellaneous changes, previous functionality should not be
affected.
Patch Set 5:
- Changes in commit message.
Patch Set 6:
- Small rewrite/optimizacions including some minor changes, previous
functionallity should not be affected.
- Add usb_drv_recv_blocking(), not tested.
Change-Id: Iecf21dacc458ba2bdfc93782d3e08b3acdf0720d
|
| | |
| |
| |
| |
| |
| |
| | |
Apparently I simply forgot to calibrate it when the port was done and the
current values are just plain wrong, especially for the charging curve.
Change-Id: Ied3cafa52f31f182f953714e28edc4c5e891255f
|
| | |
| |
| |
| |
| |
| |
| | |
Fixes some ROLO issues after commit 9a4cd2e. Note that other ROLO
issues still persist.
Change-Id: I8e0c60519902013694c5a473dcb9fc62a6ff079c
|
| | |
| |
| |
| | |
Change-Id: I36bf75218e8e032e6dbb67792c4f2ff40ceaadc3
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Patch Set 1:
This bundle includes:
- USBOTG_DESIGNWARE driver based on g#844 and g#949
- USBOTG_DESIGNWARE for s5l8702 (Classic)
- USBOTG_DESIGNWARE for s5l8701 (Nano2G)
- USBOTG_DESIGNWARE for as3525v2 (enabled on Sansa Zip Clip)
- ALIGNED_BUFFER_QUICK_PATCH (usb_serial.c)
Preliminary version, needs to adjust some things and rework to
optimize in size.
Tested on Linux (USB_STORAGE, USB_HID and USB_SERIAL).
Known issues:
- n2g: panics when USB is extracted and then re-inserted quickly. This
only happens when "Error accessing playlist control file" is shown
(RB bug?).
Patch Set 2:
- Enable USBOTG_DESIGNWARE for sansaclipplus, sansaclipv2 and sansafuzev2,
these targets have never been tested.
- First round of optimizations, mainly tries to homogenize the names of
the endpoints and other small changes, functionality should be the same
as in the previous patch set.
Patch Set 3:
- Some rewrite/optimizations, functionality should be the same as in the
previous patch set.
Patch Set 4:
- n2g: enable EPROTO workaround, EPROTO errors are produced while the
device is receiving bulk data, they are highly mitigated running the
PHY @60 MHz. but it seems that occasionally the problem still persists.
This workaround tries to solve the issue by flushing the Rx FIFO/queue
that were corrupted by the received data.
- Some minor miscellaneous changes, previous functionality should not be
affected.
Patch Set 5:
- Changes in commit message.
Change-Id: Iecf21dacc458ba2bdfc93782d3e08b3acdf0720d
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| | |
XXX explain why this is useful
Change-Id: I680fc8daf3b97e311dcb05baac8628cee2abf70e
|
| |\ \
| |/
|/|
| | |
Change-Id: Ifff00687264e942201d1f47212e07c45b6197eba
|
| | |
| |
| |
| | |
Change-Id: I3e51cc2ac3f408994f690ed6c24da33bf26a0608
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There are two very suspicious things in the power off code:
- it does not properly unlock the power register, so it should fail (!)
- it does not disable sw/hw watchdog so if register fails, the device will
most probably crash horribly because of the watchdog
I don't even understand how it worked before.
Change-Id: I9f3f94bd012e52c3b50cd5b658d68b5eb907f79b
|
| | |
| |
| |
| | |
Change-Id: Ie18d7f83ba3e7293d4cd110429e1578930d35d99
|
| | |
| |
| |
| | |
Change-Id: Ife43543d6eee6522f4016f37479a20a0db39240d
|
| | |
| |
| |
| |
| |
| | |
The new driver uses an asynchronous architecture for touch status reading.
Change-Id: Ic75a8b91bc47ee16c3af873afde178cd70186376
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The old driver was bad in many respect, it had some race conditions, it was
using a thread to serialize transfers because of the legacy i2c interface.
It also had huge latency (typically 50ms but delays up to 300ms can happen),
thus some presses were missed.
The new driver takes advantage of the new i2c driver to do everything
asynchronously. It also does not need a thread anymore because queueing
ensures proper serialization. It provides much better and reliable latency
(typically ~2ms).
Also fix the debug screen which was horribly broken. The new screen also
displays the deadzones.
Change-Id: I69b7f99b75053e6b1d3d56beb4453c004fd2076e
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The new driver provides several new features:
- asynchronous transfer
- transactions (several transfers executed at once)
- queueing
The style still provides the legacy interface.
Change-Id: I6d8ecc89d1f7057847c9b2dc69b76cd45c9c8407
|
| | |
| |
| |
| | |
Change-Id: Ia9c1e924c84772205472289494c62a63a3433727
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Always enable support for SET_BLOCK_COUNT on mmc: it is mandatory. For some
reason (probably a mistake) it was disabled unconditionaly on mmc.
Also deselect sd card after init. Although it is unlikely to make a difference,
it is already done for mmc so stay consistent.
Change-Id: I276f0d95f5bb6a0bf431c2fff4589d3dfb15f8c7
|
| | |
| |
| |
| |
| |
| |
| | |
The screen currently displays for each device the bus width, set_block_count
support, HS capability and whether it is enabled for not.
Change-Id: I6b1c3b1019e55ef1097a23c1f54fb07f5c7aa3b0
|
| | |
| |
| |
| |
| |
| |
| | |
Some players like the ZEN X-Fi have a wide but not tall screen, it is
thus better to display everything on one line for each button
Change-Id: Ided3d4ff689cc5d3bcc2bdba4c7e046cf7dc0954
|
| | |
| |
| |
| |
| |
| | |
stop pretending that stmp3600 and stmp3700 have a 4.2V power rail
Change-Id: If2506ed3e7c5db96dedc668f0931d59a5197dd88
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This screen allows to put the device in a special mode where:
- charging is disabled
- device only draws power from 5V (thus battery is untouched)
This is useful to measure the device consumption by measuring directly
the usb power consumption.
Change-Id: I2716ced0a5bb33c3c9a2607f2d17a0ce02f5689c
|
| | |
| |
| |
| |
| |
| | |
The code was very primitive and did not handle release events properly.
Change-Id: I1c56005282a9fb6608f79ff3b483ba614d635fdb
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Per Freescale recommandation, we need to ramp up the 4.2V rail before enabling
charging. Ramping should be done at 1 step/10ms, but the old code did 1 step/1s
because the powermgmt_step() function is called once every second. Use a tick
task to ramp up much faster.
Change-Id: I9a52bdd0c2ba5426d83ed42db8db7ecce2fea1f7
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The old code used button_get() to read the button status and wait for a
key to leave the panic screen. This is broken since when IRQ are disable,
the button mask is not updated anymore for touchpad and adc buttons. For
now, only use pswitch: this should be good enough for all targets.
Change-Id: I0ae179e24555ac20c3d2bf2d267c1bb0e2ceded0
|