On Wed, Jan 18, 2017 at 10:44 AM, Andre Przywara wrote:
> Any future SoCs could then just use that compatible and would describe
> the SoC details in the DT, like it's meant to be and like we do already,
> but extended by putting the mux value in there as well.
> So the only kernel contribution w
On Wed, Jan 18, 2017 at 10:53:29PM +0200, Priit Laes wrote:
> Hi!
>
> There have been multiple reports about MMC not working on 4.10-rc
> kernels for at least 3 different H3- and H2+-based devices.
>
> This issue seems to be related to the pinctrl rework and I eventually
> found a patch by Wens i
Tested on my nanopi-m1 with master branch, fix the mmc.
Regards,
Qiang
On Thu, Jan 19, 2017 at 9:37 PM, Corentin Labbe
wrote:
> On Wed, Jan 18, 2017 at 10:53:29PM +0200, Priit Laes wrote:
> > Hi!
> >
> > There have been multiple reports about MMC not working on 4.10-rc
> > kernels for at least
On 15 January 2017 at 05:17, Rask Ingemann Lambertsen wrote:
> On Fri, Jan 13, 2017 at 01:29:58AM +, Andre Przywara wrote:
>> Addresses passed on to readl and writel are expected to be of the same
>> size as a pointer. Change the parameter types of sunxi_spi0_read_data()
>> to make the compile
On Wed, Jan 18, 2017 at 04:09:32AM +0800, Chen-Yu Tsai wrote:
> Hi,
>
> On Wed, Jan 18, 2017 at 4:06 AM, Maxime Ripard
> wrote:
> > On Wed, Jan 18, 2017 at 12:57:08AM +0800, Icenowy Zheng wrote:
> >>
> >>
> >> 17.01.2017, 16:06, "Maxime Ripard" :
> >> > On Tue, Jan 17, 2017 at 03:14:46AM +0800, I
On Wed, Jan 18, 2017 at 01:02:03AM +0800, Icenowy Zheng wrote:
>
> 2017年1月17日 17:04于 Maxime Ripard 写道：
> >
> > Hi,
> >
> > On Tue, Jan 17, 2017 at 02:01:14AM +0800, Icenowy Zheng wrote:
> > > V3s has a similar but cut-down CCU to H3.
> > >
> > > Add support for it.
> > >
> > > Signed-off-by:
On Wed, Jan 18, 2017 at 01:08:14AM +0800, Icenowy Zheng wrote:
>
>
> 17.01.2017, 17:05, "Maxime Ripard" :
> > Hi,
> >
> > On Tue, Jan 17, 2017 at 02:01:14AM +0800, Icenowy Zheng wrote:
> >> V3s has a similar but cut-down CCU to H3.
> >>
> >> Add support for it.
> >>
> >> Signed-off-by: Icenowy
On Wed, Jan 18, 2017 at 06:48:35PM +0100, Ondřej Jirman wrote:
> Dne 18.1.2017 v 17:56 Maxime Ripard napsal(a):
> >>> What's your current plan to fix that? I guess the easiest (and most
> >>> likely to be reusable) would be to allow for clock tables, instead of
> >>> using the generic approach. We
On Wed, Jan 18, 2017 at 08:09:00AM +0100, Code Kipper wrote:
> I missed the binding documentation on the patch for the driver so I
> pushed it separately instead of pushing a new patch version.
> You can find it under the subject heading 'ASoC: sun4i-spdif: Add
> support for the H3 SoC' and Maxime
On Thu, Jan 19, 2017 at 09:11:49PM +0800, Icenowy Zheng wrote:
> 19.01.2017, 17:23, "Linus Walleij" :
> > On Wed, Jan 18, 2017 at 10:44 AM, Andre Przywara
> > wrote:
> >
> >> Any future SoCs could then just use that compatible and would describe
> >> the SoC details in the DT, like it's meant t
On Wed, Jan 18, 2017 at 09:44:37AM +, Andre Przywara wrote:
> Hi,
>
> On 16/01/17 16:31, Maxime Ripard wrote:
> > On Mon, Jan 09, 2017 at 12:16:00AM +, André Przywara wrote:
> >> On 05/01/17 22:42, Maxime Ripard wrote:
> >>> On Fri, Dec 30, 2016 at 01:55:44PM +0100, Linus Walleij wrote:
>
On 19 January 2017 at 18:03, Mark Brown wrote:
> On Wed, Jan 18, 2017 at 08:09:00AM +0100, Code Kipper wrote:
>
>> I missed the binding documentation on the patch for the driver so I
>> pushed it separately instead of pushing a new patch version.
>> You can find it under the subject heading 'ASoC:
Hi,
On Wed, Jan 18, 2017 at 10:53:29PM +0200, Priit Laes wrote:
> Hi!
>
> There have been multiple reports about MMC not working on 4.10-rc
> kernels for at least 3 different H3- and H2+-based devices.
Where?
> This issue seems to be related to the pinctrl rework and I eventually
> found a patc
From: Marcus Cooper
The H3 SoC uses the same SPDIF block as found in earlier SoCs, but the
transmit fifo is at a different address.
Signed-off-by: Marcus Cooper
---
Documentation/devicetree/bindings/sound/sunxi,sun4i-spdif.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/d
From: Marcus Cooper
The H3 SoC uses the same SPDIF block as found in earlier SoCs, but its
TXFIFO is mapped to another address.
Signed-off-by: Marcus Cooper
---
sound/soc/sunxi/sun4i-spdif.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/sound/soc/sunxi/sun4i-spdif.c b/sound/
From: Marcus Cooper
The H3 SoC uses the same SPDIF block as found in earlier SoCs, but the
transmit fifo is at a different address.
This has been tested on the Beelink X2.
BR,
CK
---
Changes since v1:
- Now a patch set with bindings and driver changes.
---
Marcus Cooper (2):
ASoC: sunxi: Add
So far we were not using the FIT image format to its full potential:
The SPL FIT loader was just loading the first image from the /images
node plus one of the listed DTBs.
Now with the refactored loader code it's easy to load an arbitrary
number of images in addition to the two mentioned above.
As
Currently the SPL FIT loader always looks only for the first image in
the /images node a FIT tree, which it loads and later executes.
Generalize this by looking for a "firmware" property in the matched
configuration subnode, or, if that does not exist, for the first string
in the "loadables" prope
Currently the FIT format is not used to its full potential in the SPL:
It only loads the first image from the /images node and appends the
proper FDT.
Some boards and platforms would benefit from loading more images before
starting U-Boot proper, notably Allwinner A64 and ARMv8 Rockchip boards,
whi
Currently the SPL FIT loader uses the spl_fit_select_fdt() function to
find the offset to the right DTB within the FIT image.
For this it iterates over all subnodes of the /configuration node in
the FIT tree and compares all "description" strings therein using a
board specific matching function.
If
At the moment we load two images from a FIT image: the actual U-Boot
image and the DTB. Both times we have very similar code to deal with
alignment requirement the media we load from imposes upon us.
Factor out this code into a new function, which we just call twice.
Signed-off-by: Andre Przywara
The Pine64 boards require an ARM Trusted Firmware (ATF) image to be
loaded and executes prior to the actual U-Boot proper.
Add a FIT image source file to describe the binaries, also add the
supported DTs to be able to boot multiple boards with one image. Use:
$ tools/mkimage -f boards/sunxi/pine64_
The sunxi-specific SPI load routine only knows how to load a legacy
U-Boot image.
Teach it how to handle FIT images as well, simply by providing the
existing SPL FIT loader with the right loader routine to access the SPI
NOR flash.
Signed-off-by: Andre Przywara
---
drivers/mtd/spi/sunxi_spi_spl.
Compiling the SPL in AArch64 results in bigger code, which exceeds the
pretty conservative default limits of mksunxiboot.
Use the newly introduced command line parameters to extend the file size
limit to the actual one, which is 32 KB.
Signed-off-by: Andre Przywara
---
scripts/Makefile.spl | 7 +
For a board or platform to support FIT loading in the SPL, it has to
provide a board_fit_config_name_match() routine, which helps to select
one of possibly multiple DTBs contained in a FIT image.
Provide a simple function to cover the two different Pine64 models,
which can be easily told apart by l
mksunxiboot limits the size of the resulting SPL binaries to pretty
conservative values to cover all SoCs and all boot media (NAND).
In preparation for supporting modern SoCs without NAND, which may
require a really large SPL, introduce comamnd line parameters to
push the possible SPL size to the l
The Pine64 (as all 64-bit Allwinner boards so far) need to load an
ARM Trusted Firmware image beside the actual U-Boot proper.
This can now be easily achieved by using the just extended SPL FIT
loading support, so enable it in the Pine64 defconfig.
Signed-off-by: Andre Przywara
---
configs/pine6
The SPL stack is usually located at the end of SRAM A1, where it grows
towards the end of the SPL.
For the really big AArch64 binaries the stack overwrites code pretty
soon, so move the SPL stack to the end of SRAM A2, which is unused at this
time.
Signed-off-by: Andre Przywara
---
include/confi
On Thu, 2017-01-19 at 19:26 +0100, Maxime Ripard wrote:
> Hi,
>
> On Wed, Jan 18, 2017 at 10:53:29PM +0200, Priit Laes wrote:
> > Hi!
> >
> > There have been multiple reports about MMC not working on 4.10-rc
> > kernels for at least 3 different H3- and H2+-based devices.
>
> Where?
IRC :(
>
>
29 matches
Mail list logo
