Hi James,
[auto build test ERROR on mripard/sunxi/for-next]
[also build test ERROR on v4.8-rc5 next-20160825]
[cannot apply to robh/for-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --
On 26/08/16 22:18, maxime.ripard wrote:
> On Thu, Aug 25, 2016 at 12:55:44AM +0100, André Przywara wrote:
>> On 24/08/16 20:28, maxime.ripard wrote:
>>
>> Hi,
>>
>>> On Sun, Aug 14, 2016 at 06:16:16PM +0800, Icenowy Zheng wrote:
Hi,
I currently want to work on more peripherals on A64.
>>>
> "Maxime" == Maxime Ripard writes:
Hi,
> The A33 pipeline also has some new components called SAT and DRC. Even
> though their exact features and programming model is not known (or
> documented), they need to be clocked for the pipeline to carry the video
> signal all the way.
> Add m
I think there is a tool from Allwinner in their more recent releases
for mapping fex to device tree.
In here somewhere...
https://gitlab.com/pine64-android/tools/tree/master
when you go through the pack step it prints out a bunch of messages on
how it is doing the mapping. I have not looked at th
>
> > Is there a straightforward way to convert a script.bin file to a device
> tree file? Any HOWTO that maps the various options?
>
We at least need a HOWTO mapping script.bin options to device tree
constructs. I am going to start one... because an unanswered question is an
opportunity to d
Define the necessary nodes in the A23/A33 dtsi files to make the
SPI0 controller accessible.
The SoCs also have a secondary SPI controller (SPI1), but it
cannot be muxed to any available pins and therefore doesn't get
included in the dtsi.
Signed-off-by: Karsten Merker
---
arch/arm/boot/dts/sun
The Allwinner A23/A33 SoCs contain an SPI controller that is
largely identical to the one in the A31. The major differences
from A31 to A23/A33 are:
- The TX and RX FIFOs on the A23/A33 are only 64 Bytes deep
compared to 128 Bytes on the A31.
- On A23/A33, the SPI_INTCTL register provides an ad
Hello everybody,
during the mainlining discussion in the Olimex blog at
https://olimex.wordpress.com/2016/08/30/free-electrons-add-mainline-linux-kernel-support-for-the-a13-allwinner-vpu/#comments
the topic of A33 SPI support came up. Chen-Yu and Siarhei have
pointed out that the chances are good
Hi all,
I want to enable the pull-up resistors for some gpio pins on a BananaPi-R1
when the pins are accessed from user space through /sys/class/gpio/.
Therefore I have added the following to the pio node of the device tree:
&pio {
...
switch3: switch3@0 {
allwinner,pins = "PI20";
Hi,
On 04-09-16 14:48, Saurabh Jain wrote:
Is there a straightforward way to convert a script.bin file to a device tree
file? Any HOWTO that maps the various options?
Should I first be experimenting with the sunxi Uboot instead of Mainline?
My device has an AXP152 paired with an A20. Looking
Is there a straightforward way to convert a script.bin file to a device
tree file? Any HOWTO that maps the various options?
Should I first be experimenting with the sunxi Uboot instead of Mainline?
My device has an AXP152 paired with an A20. Looking at Mainline U-boot,
this is an unexpected com
11 matches
Mail list logo