On Tue, Aug 8, 2017 at 7:13 AM, Andy Yan wrote:
> SFC stands for Serial Flash Controller on some
> rockchip platforms such as RV1108/RK3128.
>
> This patch add support for it with Standard,Dual,Quad
> mode.
What I found from the code and related kconfig, this sounds like
spi-nor flash driver try
On Wed, Aug 23, 2017 at 5:11 PM, Maxime Ripard
wrote:
> U-Boot itself might need to identify the boot device, for example to be
> able to tell where to load the kernel from when several options are
> possible.
>
> Remove the guard preventing it from being compiled.
>
> Signed-off-by: Maxime Ripard
Hello Wenyou,
We are looking at using one of the SAMA5D2 family in an upcoming design and
I have a couple of questions...
In a recent U-Boot patch set you mentioned the SAMA5D27 SOM1 SiP module. Is
this something that is available yet as I can't find it on the Microchip
website?
If we choose to
On Thu, Aug 24, 2017 at 8:41 AM, Chen-Yu Tsai wrote:
> On Wed, Aug 23, 2017 at 7:41 PM, Maxime Ripard
> wrote:
>> The driver-model rework changed, among other things, the way the private
>> data were moved around. It now uses the private field in the struct mmc.
>>
>> However, the mmc_create argu
> -Original Message-
> From: Tom Rini [mailto:tr...@konsulko.com]
> Sent: Thursday, August 24, 2017 12:50 AM
> To: Sumit Garg
> Cc: u-boot@lists.denx.de; Ruchika Gupta
> Subject: Re: [U-Boot] [PATCH] configs: SECURE_BOOT: Enable
> CONFIG_CMD_EXT4_WRITE
>
> On Wed, Aug 23, 2017 at 10:59:2
If 64-bit capability is supported, commandlistbase and fis base
should be split as lower32 and upper32. upper32 should be
written to PORT_(LST/FIS)_ADDR_HI.
Signed-off-by: Suneel Garapati
---
drivers/ata/ahci.c | 11 +--
include/ahci.h | 1 +
2 files changed, 10 insertions(+), 2 del
From: Tien Fong Chee
Report Coverity log:
The code uses a variable that has not
been initialized, leading to unpredictable
or unintended results.
Signed-off-by: Tien Fong Chee
---
lib/libfdt/fdt_wip.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/libfdt/fdt_wip.
On Wed, Aug 23, 2017 at 7:41 PM, Maxime Ripard
wrote:
> The current code, if there's both an eMMC and an MMC slot available on the
> board, will swap the MMC indices based on whether we booted from the eMMC
> or the MMC. This way, the MMC we're supposed to boot on will always have
> the index 0.
>
On Wed, Aug 23, 2017 at 7:41 PM, Maxime Ripard
wrote:
> U-Boot itself might need to identify the boot device, for example to be
> able to tell where to load the kernel from when several options are
> possible.
>
> Remove the guard preventing it from being compiled.
>
> Signed-off-by: Maxime Ripard
> -Original Message-
> From: Bin Meng [mailto:bmeng...@gmail.com]
> Sent: Wednesday, August 23, 2017 1:29 PM
> To: Y.b. Lu
> Cc: Qiang Zhao; York Sun; Grygorii Strashko; Michal Simek; Angelo
> Dureghello; Kever Yang; Jaehoon Chung; Albert Aribaud; Marcel Ziswiler;
> Markus Niebel; Z.q. Ho
On Wed, Aug 23, 2017 at 7:41 PM, Maxime Ripard
wrote:
> Our current board code duplicates a bit the spl_boot_device logic. Now that
> we can use that function in the full-flavoured U-Boot, remove that
> duplication and call the function instead.
>
> Signed-off-by: Maxime Ripard
> ---
> board/sun
On Thu, Aug 17, 2017 at 4:10 PM, Bin Meng wrote:
> CPU_INTEL_TURBO_NOT_PACKAGE_SCOPED must be turned on for Baytrail.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/x86/cpu/baytrail/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
applied to u-boot-x86, thanks!
Hi Tom,
This contains various fixes and a reworked version of serial RX buffer
support. Hopefully this is the last PR from x86 for v2017.09.
The following changes since commit 90ae53ce1ae665a1b43ecf5ccafc339839392427:
fastboot: Ensure we treat CONFIG_FASTBOOT_BUF_ADDR as long
(2017-08-22 08:20
On Thu, Aug 17, 2017 at 3:11 PM, Bin Meng wrote:
> On Wed, Aug 16, 2017 at 11:37 PM, Stefan Roese wrote:
>> Pasting longer lines into the U-Boot console prompt sometimes leads to
>> characters missing. One problem here is the small 16-byte FIFO of the
>> legacy NS16550 UART, e.g. on x86 platforms
On Wed, Aug 16, 2017 at 8:43 PM, Stefan Roese wrote:
> On 16.08.2017 14:46, Bin Meng wrote:
>>
>> Let's imply the 'pci' command to access the de facto interconnect
>> bus in an x86 system.
>>
>> Signed-off-by: Bin Meng
>
>
> Reviewed-by: Stefan Roese
applied to u-boot-x86, thanks!
_
On Thu, Aug 17, 2017 at 3:11 PM, Bin Meng wrote:
> On Wed, Aug 16, 2017 at 11:37 PM, Stefan Roese wrote:
>> To support more input characters (longer stings pasted into the U-Boot
>> prompt) without dropping, lets selects the recently added UART RX
>> buffer for these boards.
>>
>> Signed-off-by:
On Thu, Aug 17, 2017 at 4:10 PM, Bin Meng wrote:
> This converts CPU_INTEL_TURBO_NOT_PACKAGE_SCOPED to a Kconfig option.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/x86/Kconfig | 7 +++
> arch/x86/cpu/turbo.c | 2 +-
> scripts/config_whitelist.txt | 1 -
> 3 files changed,
On Mon, Aug 21, 2017 at 5:08 PM, Andy Shevchenko
wrote:
> On Sun, 2017-08-20 at 04:33 -0700, Bin Meng wrote:
>> These options should not be exposed to other platforms.
>>
>
> Fair enough.
> Thanks for taking care of this!
>
> Acked-by: Andy Shevchenko
applied to u-boot-x86, thanks!
_
On Sun, Aug 20, 2017 at 7:32 PM, Bin Meng wrote:
> Adjust VGA rom address to 0xfffb so that u-boot.rom image can be
> built again.
>
> Signed-off-by: Bin Meng
> ---
>
> configs/bayleybay_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
applied to u-boot-x86, thanks!
_
On Thu, Aug 17, 2017 at 3:11 PM, Bin Meng wrote:
> On Wed, Aug 16, 2017 at 11:37 PM, Stefan Roese wrote:
>> This reverts commit 6822cf3ec7c8768b8727573b8f4b2cb3d870b881.
>>
>> As Bin Meng has tested and pointed out, we don't need the RX interrupt
>> for the RX buffer support at all. Just reading
On Thu, Aug 17, 2017 at 3:11 PM, Bin Meng wrote:
> On Wed, Aug 16, 2017 at 11:37 PM, Stefan Roese wrote:
>> To support more input characters (longer stings pasted into the U-Boot
>> prompt) without dropping, lets selects the recently added UART RX
>> buffer for these boards.
>>
>> Signed-off-by:
On Wed, Aug 16, 2017 at 10:35 PM, Bin Meng wrote:
> With DM video, this is not used any more. Drop it.
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/pci/pci_rom.c | 41 -
> include/vbe.h | 2 --
> 2 files changed, 43 deletions(-)
>
applied to u-b
On Wed, Aug 16, 2017 at 2:19 PM, Stefan Roese wrote:
> On 16.08.2017 07:38, Bin Meng wrote:
>>
>> At present the ICH SPI opcode registers configuration is done in the
>> ich_spi_remove() routine, a little bit weird but that's how current.
>> Linux MTD driver works. This changes to move the opcode
On Wed, Aug 16, 2017 at 2:21 PM, Stefan Roese wrote:
> On 16.08.2017 07:38, Bin Meng wrote:
>>
>> Some Intel FSP (like Braswell) does SPI lock-down during the call
>> to fsp_notify(INIT_PHASE_BOOT). But before SPI lock-down is done,
>> it's bootloader's responsibility to configure the SPI controll
On Wed, Aug 16, 2017 at 2:19 PM, Stefan Roese wrote:
> On 16.08.2017 07:38, Bin Meng wrote:
>>
>> At present the ICH SPI controller driver reads the controller lock
>> status from its register in the probe routine and saves the lock
>> status to a member of priv. Later the driver uses the cached s
On Wed, Aug 16, 2017 at 2:18 PM, Stefan Roese wrote:
> On 16.08.2017 07:38, Bin Meng wrote:
>>
>> There is no need to do another assignment to ich7_spi.
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> drivers/spi/ich.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/spi/ich.c b/d
On Wed, Aug 16, 2017 at 2:18 PM, Stefan Roese wrote:
> On 16.08.2017 07:38, Bin Meng wrote:
>>
>> This routine is not called anywhere.
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> drivers/spi/ich.c | 50
>> --
>> 1 file changed, 50 deletions(-)
>>
On Tue, Aug 15, 2017 at 5:35 AM, Simon Glass wrote:
> Hi Chen-Yu,
>
> On 8 August 2017 at 21:27, Chen-Yu Tsai wrote:
>> Hi Simon,
>>
>> On Wed, Jul 5, 2017 at 3:31 AM, Simon Glass wrote:
>>> At present the driver-private data is obtained in various functions by
>>> various means. With driver mod
On Wed, Aug 23, 2017 at 7:41 PM, Maxime Ripard
wrote:
> The driver-model rework changed, among other things, the way the private
> data were moved around. It now uses the private field in the struct mmc.
>
> However, the mmc_create argument was changed in the process to always pass
> the array we
Hi Tom and other maintainers：
2017-07-13 2:25 GMT+08:00 Tom Rini :
> On Tue, Jul 11, 2017 at 03:56:03PM +1000, Bin Chen wrote:
>
> > The second area of android image was intended to put a 2nd stage
> > bootloader but in practice were rarely used (in my knowledge).
> >
> > An proposal was made to
On Wed, Aug 23, 2017 at 04:06:55PM +0200, Maxime Ripard wrote:
> We can create GPT partitions without a UUID, but we need to have
> RANDOM_UUID enabled to do that. Enable it.
>
> Signed-off-by: Maxime Ripard
> ---
> include/configs/sunxi-common.h | 4
> 1 file changed, 4 insertions(+)
>
>
On 08/18/2017 05:45 PM, Heinrich Schuchardt wrote:
> To understand what is happening in OpenProtocol or LocateProtocol
> it is necessary to know the protocol interface GUID.
> Let's write a debug message.
>
> Cc: Rob Clark
> Signed-off-by: Heinrich Schuchardt
> ---
> v4:
> use %pUl format
Now that include/config_fallbacks.h define a sane fallback for
CONFIG_SYS_MAXARGS, we can drop the definition of this constant in all
configurations that were using the default value.
Signed-off-by: Thomas Petazzoni
---
include/configs/10m50_devboard.h | 1 -
include/configs/3c120_devboard.
Hi Fabio,
On Wed, Aug 23, 2017 at 11:11 AM, Fabio Estevam wrote:
> Hi Vanessa,
>
> On Wed, Aug 23, 2017 at 11:05 AM, Vanessa Maegima
> wrote:
> > Add a new defconfig to enable secure boot on pico-imx7d.
>
> Please explain in the commit log why you are adding this new defconfig.
>
> Anyway, I un
This commit removes definitions of CONFIG_SYS_BARGSIZE defined to be
equal to CONFIG_SYS_CBSIZE in numerous configuration files.
We remove such definitions in two situations:
- CONFIG_SYS_CBSIZE is otherwise not defined in the board
configuration file, which means the default value of
CONF
CONFIG_SYS_BARGSIZE is already defined to 512 in common/image.c when
not defined. Therefore, there is no point in having board
configuration files define it to 512.
Signed-off-by: Thomas Petazzoni
---
include/configs/MigoR.h| 1 -
include/configs/ap325rxa.h | 2 --
include/co
CONFIG_SYS_MAXARGS contains the maximum number of arguments accepted
by U-Boot commands. Since the vast majority of the platforms define it
to 16, it makes sense to have a default definition to 16, which will
allow to remove this definition from a significant number of
platforms.
It will allow to
Most of the platforms are using CONFIG_SYS_CBSIZE +
sizeof(CONFIG_SYS_PROMPT) + 16 as their value for CONFIG_SYS_PBSIZE,
so let's adopt this for the fallback value of CONFIG_SYS_PBSIZE.
This will allow us to drop an explicit definition of CONFIG_SYS_PBSIZE
from a large number of platforms.
Signed
Now that include/config_fallbacks.h define a sane fallback for
CONFIG_SYS_CBSIZE, we can drop the definition of this constant in all
configurations that were using the default value.
Signed-off-by: Thomas Petazzoni
---
include/configs/10m50_devboard.h| 1 -
include/configs/3c120_devboard.h
CONFIG_SYS_CBSIZE contains the buffer size for input for the
console. The vast majority of platforms define them to some reasonable
value (256, 512 or 1024 bytes), and it is quite annoying to repeat
this definition for all platforms while it isn't really HW-related.
Therefore, let's provide a sane
Hello,
While adding support for new platforms, I found out that many, many
platforms define pretty much the same values for:
CONFIG_SYS_CBSIZE
CONFIG_SYS_PBSIZE
CONFIG_SYS_MAXARGS
CONFIG_SYS_BARGSIZE
with just a few platforms deviating from the values that have clearly
been copy/pasted over
I have never tried to use the USB in U-Boot, but it appears broken in
U-Boot 2017.09-rc2.
When I run 'usb start' I get
starting USB...
USB0: Port not available.
Is this the expected behavior?
adam
___
U-Boot mailing list
U-Boot@lists.denx.de
https:
On Thu, Aug 24, 2017 at 12:33 AM, Jagan Teki wrote:
> On Thu, Aug 24, 2017 at 12:28 AM, Dr. Philipp Tomsich
> wrote:
>>
>>> On 23 Aug 2017, at 20:44, Jagan Teki wrote:
>>>
>>> On Wed, Aug 23, 2017 at 6:22 PM, Dr. Philipp Tomsich
>>> wrote:
> On 23 Aug 2017, at 13:19, Jagan Teki wrote:
On Wed, Aug 23, 2017 at 8:20 PM, Stefano Babic wrote:
> Hi Peng,
>
> On 09/08/2017 07:09, Peng Fan wrote:
>> Add driver model support for mxc spi driver.
>> Most functions are restructured to be reused by DM and non-DM.
>> Tested on mx6slevk/mx6qsabresd board.
>>
>> Signed-off-by: Peng Fan
>> Cc:
On Mon, Aug 21, 2017 at 12:51:01PM +0530, Lokesh Vutla wrote:
> Add support for selecting proper dtb for
> dra76x u-boot from FIT.
>
> Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description: Digital signature
___
U-Boo
On Mon, Aug 21, 2017 at 12:50:59PM +0530, Lokesh Vutla wrote:
> Sync all dra7* specific dts files with the upstream
> kernel including changes queued for 4.14
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v4.14/dt-v3
>
> Signed-off-by: Lokesh Vutla
R
On Tue, Aug 22, 2017 at 01:52:58PM +0530, Lokesh Vutla wrote:
> From: Steve Kipisz
>
> AM571x supports DDR running at 666MHz. Right now it is
> clocked at 532MHz which is lower than what is supported.
> In order to have maximum performance on AM571-IDK,
> switch DDR to 666MHz.
>
> Signed-off-by
On Mon, Aug 21, 2017 at 12:51:00PM +0530, Lokesh Vutla wrote:
> Separate out u-boot specific compatibles from dts files.
> This will help in syncing dts files in future.
> Also these will get deleted eventually once respective drivers
> are capable of handling Linux dts files.
>
> Signed-off-by:
On Mon, Aug 21, 2017 at 12:50:51PM +0530, Lokesh Vutla wrote:
> LP87565 is present on dra76-evm. Select it for
> TARGET_DRA7XX_EVM.
>
> Signed-off-by: Lokesh Vutla
Reviewed-by: Tom Rini
--
Tom
signature.asc
Description: Digital signature
___
U-Bo
On Wed, Aug 23, 2017 at 10:59:21AM +0530, Sumit Garg wrote:
> As part of chain of trust with confidentiality along with distro
> boot, linux kernel image needs to be stored in encrypted form on
> ext4 boot partition. So enable CONFIG_CMD_EXT4_WRITE in all Secure
> Boot defconfigs.
>
> Signed-off-
On Thu, Aug 24, 2017 at 12:28 AM, Dr. Philipp Tomsich
wrote:
>
>> On 23 Aug 2017, at 20:44, Jagan Teki wrote:
>>
>> On Wed, Aug 23, 2017 at 6:22 PM, Dr. Philipp Tomsich
>> wrote:
>>>
On 23 Aug 2017, at 13:19, Jagan Teki wrote:
Hi Philipp,
On Tue, Aug 22, 2017 at 5:41 PM
> On 23 Aug 2017, at 20:44, Jagan Teki wrote:
>
> On Wed, Aug 23, 2017 at 6:22 PM, Dr. Philipp Tomsich
> wrote:
>>
>>> On 23 Aug 2017, at 13:19, Jagan Teki wrote:
>>>
>>> Hi Philipp,
>>>
>>> On Tue, Aug 22, 2017 at 5:41 PM, Dr. Philipp Tomsich
>>> wrote:
> On 22 Aug 2017, at 14:0
On Wed, Aug 23, 2017 at 6:22 PM, Dr. Philipp Tomsich
wrote:
>
>> On 23 Aug 2017, at 13:19, Jagan Teki wrote:
>>
>> Hi Philipp,
>>
>> On Tue, Aug 22, 2017 at 5:41 PM, Dr. Philipp Tomsich
>> wrote:
>>>
On 22 Aug 2017, at 14:05, Jagan Teki wrote:
Philipp and Kever - Thanks for the r
From: Stefan Agner
When using ISO partitions with a DMA enabled block device driver
reading the ISO partition leads to unaligned DMA operations:
CACHE: Misaligned operation at range [bffb7da8, bffb85a8]
Align the buffer to make sure we pass a buffer which works for
DMA operations.
Signed-off-
On 08/21/2017 08:42 PM, Bin Meng wrote:
> All these places seem to inherit the codes from the MMC driver where
> a FIXME was put in the comment. However the correct operation after
> read should be cache invalidate, not flush.
>
> The underlying drivers should be responsible for the cache operatio
On 08/22/2017 03:53 PM, Bin Meng wrote:
> Hi York,
>
> On Wed, Aug 23, 2017 at 12:49 AM, York Sun wrote:
>> On 08/21/2017 08:42 PM, Bin Meng wrote:
>>> All these places seem to inherit the codes from the MMC driver where
>>> a FIXME was put in the comment. However the correct operation after
>>>
Hi Peng,
On 09/08/2017 07:09, Peng Fan wrote:
> Add driver model support for mxc spi driver.
> Most functions are restructured to be reused by DM and non-DM.
> Tested on mx6slevk/mx6qsabresd board.
>
> Signed-off-by: Peng Fan
> Cc: Jagan Teki
> cc: Stefano Babic
> ---
>
Reviewed-by: Stefano
On 17/08/2017 11:48, Peng Fan wrote:
> Add copyright and license header.
>
> Signed-off-by: Peng Fan
> Cc: Stefano Babic
> ---
> arch/arm/mach-imx/mx7/psci-mx7.c | 7 +++
> arch/arm/mach-imx/mx7/psci.S | 7 +++
> 2 files changed, 14 insertions(+)
>
> diff --git a/arch/arm/mach-imx/
Hi Vanessa,
On Wed, Aug 23, 2017 at 11:05 AM, Vanessa Maegima
wrote:
> Add a new defconfig to enable secure boot on pico-imx7d.
Please explain in the commit log why you are adding this new defconfig.
Anyway, I understant that this could be useful if someone tries to
boot this board with NXP 4.1
We can create GPT partitions without a UUID, but we need to have
RANDOM_UUID enabled to do that. Enable it.
Signed-off-by: Maxime Ripard
---
include/configs/sunxi-common.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/configs/sunxi-common.h b/include/configs/sunxi-common.h
inde
Add a new defconfig to enable secure boot on pico-imx7d.
Signed-off-by: Vanessa Maegima
---
board/technexion/pico-imx7d/MAINTAINERS | 1 +
board/technexion/pico-imx7d/pico-imx7d.c | 9 +++-
configs/pico-imx7d_secure_defconfig | 35
3 files changed, 44
The gpt_fill_pte will need to access the device block size. Let's pass the
device descriptor as an argument.
Signed-off-by: Maxime Ripard
---
disk/part_efi.c | 7 ---
include/part.h | 6 --
2 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/disk/part_efi.c b/disk/part_efi.c
Both the config option and the DT options specify the offset to set the GPT
at in bytes, yet the code treats those values as block numbers.
Fix that.
Signed-off-by: Maxime Ripard
---
disk/part_efi.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/disk/part_efi.c b
The current code checks that no partitions overlap with the GPT partition
table using the offset of the first LBA usable for that partition.
This works fine, unless you have a partition entry that is further away
than it usually is and you want to create partitions in the gap between the
GPT heade
The start variable is only used inside a loop, and is never affected inside
it, so it's a purely local variable.
In the same way the partition size is accessed several times, so we can
store it in a variable.
Signed-off-by: Maxime Ripard
---
disk/part_efi.c | 14 --
1 file changed,
On Wed, Aug 23, 2017 at 5:01 PM, Maxime Ripard
wrote:
> All the new SoCs from Allwinner since the A33 have had the phy_ctl offset
> at 0x410 instead of 0x404 that was used on the previous SoCs.
>
> Instead of adding more and more special cases as the number of SoCs grow,
> let's invert the test to
> On 23 Aug 2017, at 13:19, Jagan Teki wrote:
>
> Hi Philipp,
>
> On Tue, Aug 22, 2017 at 5:41 PM, Dr. Philipp Tomsich
> wrote:
>>
>>> On 22 Aug 2017, at 14:05, Jagan Teki wrote:
>>>
>>> Philipp and Kever - Thanks for the response.
>>>
>>> Few comment below.
>>>
>>> On Thu, Aug 17, 2017 a
Hi Wilson,
On Wed, Aug 23, 2017 at 12:51 PM, Wilson Lee wrote:
> From: Keng Soon Cheah
>
> Some device the serial console's initialization cannot run early during
> the boot process. Hence, nulldev serial device is helpful on that
> situation.
>
> This commit is to adding nulldev serial driver.
On Wed, Aug 23, 2017 at 5:43 AM, Stefano Babic wrote:
> I have merged the whole series to u-boot-imx. Many thanks for your
> effort, this was in the TODO list for i.MX since a long time !
Yes, very nice job, Stefan!
I will be using it soon on mx6sabresd, thanks!
The driver-model rework changed, among other things, the way the private
data were moved around. It now uses the private field in the struct mmc.
However, the mmc_create argument was changed in the process to always pass
the array we used to have to store our private structures.
The basically mea
The current code, if there's both an eMMC and an MMC slot available on the
board, will swap the MMC indices based on whether we booted from the eMMC
or the MMC. This way, the MMC we're supposed to boot on will always have
the index 0.
However, this causes various issues, for example when using oth
Our current board code duplicates a bit the spl_boot_device logic. Now that
we can use that function in the full-flavoured U-Boot, remove that
duplication and call the function instead.
Signed-off-by: Maxime Ripard
---
board/sunxi/board.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-
U-Boot itself might need to identify the boot device, for example to be
able to tell where to load the kernel from when several options are
possible.
Remove the guard preventing it from being compiled.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-sunxi/board.c | 4 +---
1 file changed, 1 inse
Hi,
Here is an attempt at removing the hack in the sunxi code to switch
the MMC indices depending on the boot device.
It's based on Siarhei's suggestion to go through an environment
variable set by the code, and then having a script in our default
bootcmd to change the boot order in order to alwa
All the new SoCs from Allwinner since the A33 have had the phy_ctl offset
at 0x410 instead of 0x404 that was used on the previous SoCs.
Instead of adding more and more special cases as the number of SoCs grow,
let's invert the test to have 0x410 by default, and the (hopefully) fixed
number of old
Hi Philipp,
On Tue, Aug 22, 2017 at 5:41 PM, Dr. Philipp Tomsich
wrote:
>
>> On 22 Aug 2017, at 14:05, Jagan Teki wrote:
>>
>> Philipp and Kever - Thanks for the response.
>>
>> Few comment below.
>>
>> On Thu, Aug 17, 2017 at 2:02 PM, Dr. Philipp Tomsich
>> wrote:
>>> Jagan,
>>>
On 17 Aug
Hi,
On 08/23/2017 07:03 PM, Maxime Ripard wrote:
> Almost all of the newer Allwinner SoCs have a new operating mode for the
> eMMC clocks that needs to be enabled in both the clock and the MMC
> controller.
>
> Details about that mode are sparse, and the name itself (new mode vs old
> mode) doesn
From: Keng Soon Cheah
Some device the serial console's initialization cannot run early during
the boot process. Hence, nulldev serial device is helpful on that
situation.
This commit is to adding nulldev serial driver. This will allows the
default console to be specified as a nulldev.
Signed-of
Although Xilinx Zynq SoC was using MACB similar hardware. However,
U-boot MACB driver was not supporting Xilinx Zynq SoC. This patch is
to add support for the Xilinx Zynq SoC to the existing MACB network
driver.
This patch is to add Zynq GEM DMA Config, provide callback
function for different link
Hi,
no idea if this is the right place to mail about this, but i got
suggested this node is out-of-norm, and the diff below fixes that
for me on rk3188.
-Artturi
diff --git a/arch/arm/dts/rk3xxx.dtsi b/arch/arm/dts/rk3xxx.dtsi
index 6d9e36d235..21f2afc104 100644
--- a/arch/arm/dts/rk3xxx.dtsi
The eMMC controller for the A83T uses the new operating mode. Enable it.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-sunxi/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-sunxi/Kconfig b/arch/arm/mach-sunxi/Kconfig
index 94412bac0c1d..8d56d591d97a 100644
--- a/arch/a
Almost all of the newer Allwinner SoCs have a new operating mode for the
eMMC clocks that needs to be enabled in both the clock and the MMC
controller.
Details about that mode are sparse, and the name itself (new mode vs old
mode) doesn't give much details, but it seems that the it changes the
sam
Ping.. It's two weeks since sent out for review.
Thanks,
Peng.
On Wed, Aug 09, 2017 at 01:09:33PM +0800, Peng Fan wrote:
>Add driver model support for mxc spi driver.
>Most functions are restructured to be reused by DM and non-DM.
>Tested on mx6slevk/mx6qsabresd board.
>
>Signed-off-by: Peng Fan
On 14/08/2017 12:09, Peng Fan wrote:
> To i.MX7ULP, we need to create two info instances for
> iomux0 and iomux1 respectively, otherwise iomuxc0/1 will
> share one info instance and use one base, because imx_pinctrl_probe
> will use info to store base address and etc. But iomuxc0/1
> actually have
On 14/08/2017 12:09, Peng Fan wrote:
> when using SHARE_MUX_CONF_REG, wrong mask is used for
> writing config value, which causes mux value is cleared.
>
> Signed-off-by: Peng Fan
> Cc: Simon Glass
> Cc: Stefano Babic
> ---
> drivers/pinctrl/nxp/pinctrl-imx.c | 2 +-
> 1 file changed, 1 insert
Hi Stefan,
On 16/08/2017 20:00, Stefan Agner wrote:
> From: Stefan Agner
>
> This series adds NXP's Serial Download Protocol (SDP) support via
> USB for SPL/U-Boot. It allows to download U-Boot via USB from a
> (recovered) SPL using the same tools used to download SPL itself
> (specifically imx_
Hello Tom,
please pull from u-boot-i2c master
The following changes since commit 90ae53ce1ae665a1b43ecf5ccafc339839392427:
fastboot: Ensure we treat CONFIG_FASTBOOT_BUF_ADDR as long (2017-08-22
08:20:02 -0400)
are available in the git repository at:
git://git.denx.de/u-boot-i2c.git maste
Hello Peng Fan,
Am 14.08.2017 um 12:00 schrieb Peng Fan:
Add an i2c mux driver providing access to i2c bus segments using a
hardware MUX sitting on a master bus and controlled through gpio pins.
E.G. something like:
-- -- Bus segment 1 - - - - -
Hello Partrice,
Am 09.08.2017 um 14:45 schrieb patrice.chot...@st.com:
From: Patrice Chotard
Add i2c driver which can be used on both STM32F7 and STM32H7.
This I2C block supports the following features:
_ Slave and master modes
_ Multimaster capability
_ Standard-mode (up to 100 kHz)
_
Hi,
i make a little changes to
lcdc.h and sunxi_diplay.h to make dual channel LVDS interface working :
-lcdc.h
#define SUNXI_LCDC_TCON0_LVDS_INTF_CH(n) ((n) << 30) /* LVDS Dual channel
0=single 1=dual*/
and in
-sunxi_diplay.h (line 830).
#ifdef CONFIG_VIDEO_LCD_IF_LVDS
if (mode->yres
ping
On 2017年08月08日 09:43, Andy Yan wrote:
SFC stands for Serial Flash Controller on some
rockchip platforms such as RV1108/RK3128.
This patch add support for it with Standard,Dual,Quad
mode.
Signed-off-by: Andy Yan
---
Changes in v2:
- fix the wrong reference in Makefile, which should be
On 08/23/2017 08:09 AM, Lokesh Vutla wrote:
Now that we have synced DTS from Latest Linux kernel, add dt support
for BeagleBoard-X15 revC. Board detection support is already added for
this board.
Lokesh Vutla (2):
board: ti: am57xx: Add dt support for BeagleBoard-X15 revC
env: ti: boot: Sele
commit 4bebf94e8544("rockchip: clk: rk3368: do not change
CPLL/GPLL before returning to BROM") limits the pll can only
be setup in SPL stage, but there are still some rk3368 based
boards have not use SPL yet, so they need run rkclk_init to
setup the pll in full u-boot stage, otherwise the clk_set_r
93 matches
Mail list logo
