Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
|
|
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
|
|
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
|
|
When booting from a device that's providing the rootfs via a
cape fragment, you face the following problem as it appears
on the beaglebone black.
The priority of the emmc cape is low (positive number) so that
any cape that is detected and uses the resources of the emmc
interface can work (for example the camera cape). This means that
we have to be booting from external sd card.
However if there is no conflict, and the cape dtbo is not included
in the kernel (via the firmware builtin configure option) the capemgr
will attempt to load the cape too early, at a time that the rootfs
cape hasn't been loaded yet.
In order to fix that an optional third parameter is added to
the specification of a cape in the eanble_partno option which allow
you to specify the priority.
so capemgr.enable_partno=[PART[:REV[:PRIO]]][,PART..]
To load the cape fragment after all the builtin capes have loaded
use a priority higher than 10; i.e. to load cape foo use:
capemgr.enable_partno=foo:00A0:10
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>
|
|
Signed-off-by: Daniel Nilsson <daniel@dnil.se>
|
|
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
|
|
|
|
|
|
|
|
|
This is the full Linux driver enable bacon cape definition.
|
|
|
|
Call to led_pwm_set() can happen inside atomic context, like triggers.
If the PWM call can sleep, defer using a worker.
Signed-off-by: Florian Vaussard <florian.vaussard@epfl.ch>
Reviewed-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Acked-by: Thierry Reding <thierry.reding@avionic-design.de>
Signed-off-by: Bryan Wu <cooloney@gmail.com>
|
|
The DT binding for the pwm-leds devices are similar to the gpio-leds type.
LEDs are represented as sub-nodes of the pwm-leds device.
The code for handling the DT boot is based on the code found in the
leds-gpio driver and adapted to use PWMs instead of GPIOs.
To avoid having custom cleanup code in case of DT boot the newly created
devm_of_pwm_get() API is used to get the correct PWM instance.
For usage see:
Documentation/devicetree/bindings/leds/leds-pwm.txt
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
Signed-off-by: Bryan Wu <cooloney@gmail.com>
|
|
The code looks more nicer if we use:
while (i--)
instead:
if (i > 0)
for (i = i - 1; i >= 0; i--)
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Signed-off-by: Bryan Wu <cooloney@gmail.com>
|
|
In order to be able to add device tree support for leds-pwm driver we need
to rearrange the data structures used by the drivers.
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Signed-off-by: Bryan Wu <cooloney@gmail.com>
|
|
Update the driver to use the new API for requesting pwm so we can take
advantage of the pwm_lookup table to find the correct pwm to be used for the
LED functionality.
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Signed-off-by: Bryan Wu <cooloney@gmail.com>
|
|
Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
Acked-by: Rodolfo Giometti <giometti@enneenne.com>
Signed-off-by: Matt Ranostay <mranostay@gmail.com>
|
|
Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
Acked-by: Rodolfo Giometti <giometti@enneenne.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Matt Ranostay <mranostay@gmail.com>
|
|
This removes some boilerplate code (no functional changes).
Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
Acked-by: Rodolfo Giometti <giometti@enneenne.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Matt Ranostay <mranostay@gmail.com>
|
|
Add support for the PMIC interrupt, supports power-button presses.
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>
|
|
Adaption of the original patch by Andrew Bradford <andrew.bradford@omni-id.com>
Some minor devm_* changes and DT support.
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>
|
|
Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
|
|
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
|
Added PPS input from SQW pin on the DS1307
Signed-off-by: Matt Ranostay <mranostay@gmail.com>
|
|
rename RTC protocape to a more consistent naming
Signed-off-by: Matt Ranostay <mranostay@gmail.com>
|
|
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
|
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
|
|
|
Signed-off-by: Bas Laarhoven <sjml@xs4all.nl>
|
|
|
|
In the 3.2 kernel using the da8xx lcdc fb, the HSW, HFP, and HBP are written to the lcdc registers directly as entered. i.e. if HSW=47 , then 47 is written to the register and the value that is generated is the register value plus one (total of 48 clocks).
with the 3.8 kernel using the DRM driver, the code subtracts one from the set value before writing it to the register, i.e. if HSW=47, then 46 is written to the register and the value that is generated is the register value plus one (total of 47 clocks).
specifically with the LCD3 board, the lcd panel does not use data enable as a timing signal. it specifically counts the number of vertical clocks and horizontal clocks to determine data start points. the lcd panel expects for the sum of the HSW and HBP to be 70 pixel clocks. currently it is 68. this is the root cause of the color shift and poor image quality....
the HSW, HFP, and HBP for all three lcd panels needs to be incremented by one.
|
|
|
|
LCD7 rev A3/A4 had some pins wrong
|
|
Added a few modes that are known not to work on my end.
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>
|
|
|
|
When a user cape hogs the audio, allow booting with a HDMI cape which
only supports video.
|
|
|
|
Add analogous option to disable_partno; this one doesn't require the presence of
a base dts override.
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>
|
|
|
|
Updated all the standard capes with their resource definitions.
|
|
Start adding the resource list of each cape.
|
|
Now each cape can declare an exclusive-use property which is
a string list of every resource it requires.
Attempting to load a cape that uses the same resource will fail.
|
|
Using the reset control framework, the camera works on the black.
I love it when a plan comes together...
|
|
|
|
|
|
This should make it work reliably for resolutions up to 1024x768
1280x960 and higher hang, or crash..
|
|
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>
|
|
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
|
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|