Add an implementation of the ds1307 driver that uses the driver model
i2c APIs.
Signed-off-by: Chris Packham
---
Changes in v4:
- move #ifdef CONFIG_CMD_DATE inside the legacy block
- use driver data to identify specific chip
- terminate the #ifndef with a #endif
In preparation for the next change that adds a new option.
Signed-off-by: Chris Packham
---
This isn't strictly needed. I did this so the next patch only touched
CONFIG_CMD_DATE and I figured I may as well send this out so it can be
applied if desired.
Changes in v4:
On Sat, Apr 29, 2017 at 12:27 PM, Simon Glass wrote:
> Hi Chris,
>
> On 25 April 2017 at 23:19, Chris Packham wrote:
>> Add an implementation of the ds1307 driver that uses the driver model
>> i2c APIs.
>>
>> Signed-off-by: Chris Packham
add a simple readme to introduce rockusb and tell people how to use it
Signed-off-by: Eddie Cai
Changes in v3:
-fix checkpatch error
---
doc/README.rockusb | 37 +
1 file changed, 37 insertions(+)
create mode 100644
this patch add rockusb command. the usage is
rockusb
e.g. rockusb 0 mmc 0
Signed-off-by: Eddie Cai
Changes in v3:
-fix comment from Simon and Lukasz
-fix checkpactch error
---
cmd/Kconfig | 11 +
cmd/Makefile | 1 +
cmd/rockusb.c | 74
rockusb is a protocol run between host pc and device. it help people get device
info, flash image to device. this patch implement rockusb on device side
Changes in v3:
-switch back to use g_dnl code
-address comment from Lukasz and Simon
-fix checkpatch error
Changes in v2:
-switch to use usb
On 25 April 2017 at 01:52, Philipp Tomsich
wrote:
> The clocking of the designware MMC controller in the upstream
> (i.e. Linux) RK3399 has changed/does not match what the current DTS in
> U-Boot uses: the first clock entry now is HCLK_SDMMC instead of
>
all rk3288 based boards support rockusb, so enable it
Signed-off-by: Eddie Cai
Changes in v3:
-move to defconfig
---
configs/evb-rk3288_defconfig | 3 +++
configs/fennec-rk3288_defconfig | 2 ++
configs/firefly-rk3288_defconfig | 2 ++
On 26 April 2017 at 12:41, Adam Ford wrote:
> As requested, I added the CONFIG_TWL4030_POWER to Kconfig and made it
> the implied default when selecting OMAP34XX as a platform.
>
> Signed-off-by: Adam Ford
Reviewed-by: Simon Glass
On 26 April 2017 at 12:41, Adam Ford wrote:
> With the addition of Kconfig now having CONFIG_TWL4030_POWER and
> with that being the default when OMAP34XX is selected, this
> is no longer needed in include/configs and can be removed from the
> whitelist.
>
> This has only been
On 25 April 2017 at 22:57, Lokesh Vutla wrote:
>
>
> On Monday 17 April 2017 06:39 PM, Adam Ford wrote:
>> This patch changes the way DM_MMC calculates offset to the base register of
>> MMC. Previously this was through an #ifdef but that wasn't necessary for
>> OMAP3.
>>
>>
On 26 April 2017 at 16:36, Philipp Tomsich
wrote:
> With everything in place (i.e. the new efuse driver, the clk-support
> for the non-secure efuse block, and the board-specific functions to
> derive 'serial#' from the cpu-id within the efuses), enable this
On 24 April 2017 at 16:39, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v6: Several improvements:
> - Rename and shrink reset_cntl syscon to pll_cntl.
> - Reorder include config defines.
> v5: No changes.
> v4: No
On 25 April 2017 at 18:32, Andre Przywara wrote:
> SPL_FIT obviously requires libfdt in SPL, so let Kconfig express that by
> selecting SPL_OF_LIBFDT.
> Also make the actual options that users want (SPL signature and SPL FIT
> loading) visible in the menu and let them
this patch implement rockusb protocol on the device side. this is based on USB
download gadget infrastructure. the rockusb function implements the rd, wl, rid
commands. it can work with rkdeveloptool.
Signed-off-by: Eddie Cai
Changes in v3:
-split the macro to
On 26 April 2017 at 16:36, Philipp Tomsich
wrote:
> This adds a simple driver for reading the efuse block of the RK3399.
> It should be easy enough to add drivers for other devices (e.g. the
> RK3328, RK3368, etc.) by passing the device details via
On 24 April 2017 at 04:34, Kever Yang wrote:
> Hi Simon,
>
>
>
> On 04/24/2017 11:38 AM, Simon Glass wrote:
>>
>> On 19 April 2017 at 04:17, Kever Yang wrote:
>>>
>>> Firefly-rk3399 is a bord from T-Firefly, you can find detail about
>>> it
On 25 April 2017 at 01:39, Philipp Tomsich
wrote:
> Adding documentation on the new config properties:
>'u-boot,mmc-env-offset' - overrides CONFIG_ENV_OFFSET
>'u-boot,mmc-env-offset-redundant'
>- overrides
On 25 April 2017 at 19:30, Wenyou Yang wrote:
> Differentiate the generic clock source selection value from the parent
> clock index to fix the incorrect assignment of the generic clock
> source selection.
>
> Signed-off-by: Wenyou Yang
> ---
>
>
On 24 April 2017 at 16:39, Álvaro Fernández Rojas wrote:
> It is based on linux/drivers/tty/serial/bcm63xx_uart.c
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v6: Introduce changes suggested by Daniel Schwierzeck:
> - Use clr/set bits macros.
> -
On 26 April 2017 at 16:03, Jernej Skrabec wrote:
> This commit adds support for DM I2C on sunxi platform. It can coexist
> with old style sunxi I2C driver, because it is still used in SPL and
> by some SoCs.
>
> Because sunxi platform doesn't yet support DM clk, reset and
On 24 April 2017 at 16:39, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v6: Several improvements:
> - Rename reset_cntl syscon to pll_cntl.
> - Reorder include config defines.
> v5: No changes.
> v4: No changes.
> v3:
Hi Chris,
On 25 April 2017 at 23:19, Chris Packham wrote:
> Add an implementation of the ds1307 driver that uses the driver model
> i2c APIs.
>
> Signed-off-by: Chris Packham
>
> ---
>
> Changes in v2: None
>
> drivers/rtc/Kconfig | 7 ++
>
On 26 April 2017 at 16:36, Philipp Tomsich
wrote:
> The (non-secure) efuse node in the DTS requests PCLK_EFUSE1024NS.
> To allow us to add a efuse-driver (and more importantly, to allow
> probes of such a driver to succeed), we need need to accept requests
>
On 24 April 2017 at 16:39, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v6: Several improvements:
> - Rename and shrink reset_cntl syscon to pll_cntl.
> - Reorder include config defines.
> v5: No changes.
> v4: No
On 26 April 2017 at 16:36, Philipp Tomsich
wrote:
> With our efuse driver for the RK3399 ready, we can add the
> board-specific code that consumes the cpuid from the efuse block and
> postprocesses it into the system serial (using the same CRC32 based
>
On 24 April 2017 at 16:39, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v6:
> - Select CONFIG_BMIPS_BOOT_RAM and CONFIG_BAUDRATE in defconfig.
> - Simplify board name.
> v5: No changes.
> v4: No changes.
> v3: No
Hi,
On 26 April 2017 at 05:57, Sylvain Lemieux wrote:
> From: Liam Beguin
>
> Add DM support for i2c functions.
>
> Signed-off-by: Liam Beguin
> Signed-off-by: Sylvain Lemieux
> ---
> Changes from v2 to
Hi Andy,
On 20 April 2017 at 20:31, Andy Yan wrote:
> Add driver to setup the various PLLs and peripheral
> clocks on the RK3368.
Subject: clock
>
> Signed-off-by: Andy Yan
> ---
>
> arch/arm/include/asm/arch-rockchip/cru_rk3368.h | 110
Hi Jean-Jacques,
On 24 April 2017 at 02:55, Jean-Jacques Hiblot wrote:
> Hi Simon,
>
> On 24/04/2017 04:02, Simon Glass wrote:
>>
>> With driver model MMC is probed automatically when needed. We should not
>> re-init MMC each time.
>>
>> Signed-off-by: Simon Glass
Hi Stefan,
On 24 April 2017 at 01:48, Stefan Roese wrote:
> On my x86 platform I've noticed, that calling dm_uninit() or the new
> function dm_remove_devices_flags() does not remove the desired device at
> all. Debugging showed, that the serial uclass returns -EPERM in
>
On 22 April 2017 at 02:57, Jonas Karlman wrote:
> Set ethernet mac address in late init for Tinker Board,
> prevents getting a random mac address each boot.
>
> Read mac address from eeprom, first 6 bytes from m24c08@50.
> Same as /etc/init.d/rockchip.sh on Tinker OS.
>
>
On 24 April 2017 at 16:39, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v6:
> - Select CONFIG_BMIPS_BOOT_RAM and CONFIG_BAUDRATE in defconfig.
> - Simplify board name.
> v5: No changes.
> v4: No changes.
> v3: Add
On 24 April 2017 at 01:48, Stefan Roese wrote:
> On my x86 platform I've noticed, that calling dm_uninit() or the new
> function dm_remove_devices_flags() does not remove the desired device at
> all. Debugging showed, that the serial uclass returns -EPERM in
> serial_pre_remove().
On 22 April 2017 at 02:57, Jonas Karlman wrote:
> Signed-off-by: Jonas Karlman
> ---
>
> Changes in v3:
> - Add i2c_eeprom_{read,write} functions
>
> Changes in v2: None
>
> drivers/misc/i2c_eeprom.c | 32 ++--
> include/i2c_eeprom.h
On 24 April 2017 at 16:39, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v6:
> - Select CONFIG_BMIPS_BOOT_RAM and CONFIG_BAUDRATE in defconfig.
> - Simplify board name.
> v5: No changes.
> v4: No changes.
> v3: No
On 22 April 2017 at 04:27, Lokesh Vutla wrote:
> Add debug UART functions to permit omap specific ns16550 to
> provide an early debug UART. This is mostly in common with
> DEBUG_UART_NS16550 except for Mode definition register which
> is required for selecting UART mode(16x
On 20 April 2017 at 21:34, Jacob Chen wrote:
> Using mask is more flexible than bits.
>
> Signed-off-by: Jacob Chen
> ---
>
> drivers/power/regulator/rk808.c | 39 ++-
> 1 file changed, 22 insertions(+), 17
On 24 April 2017 at 16:39, Álvaro Fernández Rojas wrote:
> CFE checks CPU Thread in a different way (using register $22):
> mfc0t1, C0_BCM_CONFIG, 3 # $22
> li t2, CP0_CMT_TPID # (1 << 31)
> and t1, t2
> bnezt1, 2f # if we are running on thread 1, skip init
>
On 23 April 2017 at 21:58, Kever Yang wrote:
> The file is from evb-rk3399_defconfig with changes:
> - use rk3399-firefly dtb
> - re-order by make savedefconfig
>
> Signed-off-by: Kever Yang
> ---
>
> configs/firefly-rk3399_defconfig | 65
>
On 20 April 2017 at 20:32, Andy Yan wrote:
> Add sysreset driver to reset rk3368 SOC.
>
> Signed-off-by: Andy Yan
> ---
>
> drivers/sysreset/Makefile | 1 +
> drivers/sysreset/sysreset_rk3368.c | 58
>
On 20 April 2017 at 21:34, Jacob Chen wrote:
> Add support for the rk818 regulator. The regulator module consists
> of 4 DCDCs, 9 LDOs, 1 switch and 1 BOOST converter which is used to
> power OTG and HDMI5V.
>
> TODO: I don't know how to deal with BOOST and LDO9,
> so just
On 20 April 2017 at 21:34, Jacob Chen wrote:
> Both RK808 and RK818 chips are using a similar register map,
> so we can reuse them.
>
> I have also add reg prefix to exist registers, to keep them same style.
>
>
> Signed-off-by: Jacob Chen
> ---
>
>
On 20 April 2017 at 20:33, Andy Yan wrote:
> PX5 EVB is designed by Rockchip for automotive field
> with integrated CVBS (TP2825) / MIPI DSI / CSI / LVDS
> HDMI video input/output interface, audio codec ES8396,
> WIFI / BT (on RTL8723BS), Gsensor BMA250E and light
>
On 20 April 2017 at 20:33, Andy Yan wrote:
> Sheep board is designed by Rockchip as a EVB for rk3368.
> Currently it is able to boot a linux kernel and system
> to console with the miniloader run as fist level loader.
>
> Signed-off-by: Andy Yan
Hi Andy,
On 20 April 2017 at 20:31, Andy Yan wrote:
>
> Add driver to support iomux setup for the most commonly
> used peripherals on rk3368.
>
> Signed-off-by: Andy Yan
> ---
>
> arch/arm/include/asm/arch-rockchip/grf_rk3368.h | 443
>
Hi Andy,
On 20 April 2017 at 20:31, Andy Yan wrote:
> From: Andreas Färber
>
> The RK3368 is an octa-core Cortex-A53 SoC from Rockchip.
> This adds basic support to chain-load U-Boot from Rockchip's
> miniloader.
>
> Signed-off-by: Andreas Färber
Hi Andy,
On 20 April 2017 at 20:31, Andy Yan wrote:
> Add driver to setup the various PLLs and peripheral
> clocks on the RK3368.
Subject: clock
>
> Signed-off-by: Andy Yan
> ---
>
> arch/arm/include/asm/arch-rockchip/cru_rk3368.h | 110
Hi Alex,
On 16 April 2017 at 13:34, Simon Glass wrote:
> Hi Alex,
>
> On 16 April 2017 at 04:08, Alexander Graf wrote:
>>
>>
>> On 16.04.17 04:09, Heinrich Schuchardt wrote:
>>>
>>> On 04/15/2017 11:51 PM, Andreas Färber wrote:
Am 15.04.2017 um 23:16
Hi Jagan,
On Sun, Apr 9, 2017 at 4:12 PM, Jagan Teki wrote:
>> Do you have a git tree with this series applied? I would like to test it.
>
> http://git.denx.de/?p=u-boot-spi.git;a=shortlog;h=refs/heads/sabresd
I have tested imx6dl spl defconfig and it does not boot.
From: Suniel Mahesh
.probe method has been assigned twice when declaring a
a driver with U_BOOT_DRIVER(). Removed one of them.
Signed-off-by: Suniel Mahesh
---
Note:
Tested on latest u-boot mainline tree and maintainers u-boot-spi
tree, no
On Fri, Apr 28, 2017 at 12:43 PM, Tom Rini wrote:
> On Fri, Apr 28, 2017 at 12:40:30PM -0500, Adam Ford wrote:
>> On Wed, Apr 26, 2017 at 6:58 AM, Tom Rini wrote:
>> > On Wed, Apr 26, 2017 at 01:37:08PM +0530, Lokesh Vutla wrote:
>> >
>> >> Signed-off-by:
On Fri, Apr 28, 2017 at 12:40:30PM -0500, Adam Ford wrote:
> On Wed, Apr 26, 2017 at 6:58 AM, Tom Rini wrote:
> > On Wed, Apr 26, 2017 at 01:37:08PM +0530, Lokesh Vutla wrote:
> >
> >> Signed-off-by: Lokesh Vutla
> >
> > Reviewed-by: Tom Rini
On Wed, Apr 26, 2017 at 6:58 AM, Tom Rini wrote:
> On Wed, Apr 26, 2017 at 01:37:08PM +0530, Lokesh Vutla wrote:
>
>> Signed-off-by: Lokesh Vutla
>
> Reviewed-by: Tom Rini
>
> --
> Tom
>
Tom - Do you know if his series and/or my OMAP3
This commit enables RK3399 support for HDMI through the following
changes:
- adds a driverdata structure to mirror some subtle version
differences between the RK3399 VOPs and those in the RK3288
(e.g. the pin-polarity configuration)
- configures the VOP to output 32bpp for HDMI
- handles
This commit enables HDMI output in the DTS by adding the necessary
nodes to vopl/vopb and by adding the HDMI node.
Signed-off-by: Philipp Tomsich
---
Changes in v2: None
arch/arm/dts/rk3399.dtsi | 110 +++
1
This series provides HDMI enablement for the RK3399 and will support
video console on the RK3399 either with VOP-lit or VOP-big:
- pinctrl and clk support for the hdmi node
- a refactoring of rk_vop.c and rk_hdmi.c to allow for the minor
differences between the RK3288 and RK3399 VOP and HDMI
To add HDMI support for the RK3399, this commit provides the needed
pinctrl functionality to configure the HDMI I2C pins (used for reading
the screen's EDID).
Signed-off-by: Philipp Tomsich
---
Changes in v2: None
This commit enables the RK3399 HDMI TX, which is very similar to the
one found on the RK3288. The differences between the two SoCs (mainly
the input VOP selection) is abstracted away through the driverdata.
Note that the I2C communication for reading the EDID works well with
the default settings,
This allows requests (via the DTS) for PCLK_HDMI_CTRL/PCLK_VIO_GRF,
which are clock gates in the HDMI output path for the RK3399.
As these are enabled by default (i.e. after reset), we don't implement
any logic to actively open/close these clock gates and simply assume
that their reset-default
On 28 April 2017 at 10:14, Chris Packham wrote:
> After moving to KConfig and removing from all headers options should be
> removed from config_whitelist.txt so the build starts complaining if
> someone adds them back.
>
> Acked-by: Masahiro Yamada
After moving to KConfig and removing from all headers options should be
removed from config_whitelist.txt so the build starts complaining if
someone adds them back.
Acked-by: Masahiro Yamada
Signed-off-by: Chris Packham
---
Simon asked for
2017-04-28 10:13 GMT+09:00 Chris Packham :
> After moving to KConfig and removing from all headers options should be
> removed from config_whitelist.txt so the build starts complaining if
> someone adds them back.
>
> Signed-off-by: Chris Packham
Hi Philipp,
Dne petek, 28. april 2017 ob 17:53:11 CEST je Philipp Tomsich napisal(a):
> This commit enables the RK3399 HDMI TX, which is very similar to the
> one found on the RK3288. The differences between the two SoCs (mainly
> the input VOP selection) is abstracted away through the
Hi Philipp,
Dne petek, 28. april 2017 ob 17:53:10 CEST je Philipp Tomsich napisal(a):
> This commit enables RK3399 support for HDMI through the following
> changes:
> - adds a driverdata structure to mirror some subtle version
> differences between the RK3399 VOPs and those in the RK3288
>
On 04/28/2017 12:14 AM, Santan Kumar wrote:
This patch adjusts memory map for images on LS2080ARDB,
LS2080AQDS as per below memory map for NOR flash:
Image Flash Offset
RCW+PBI 0x
Boot firmware (U-Boot) 0x0010
Boot firmware
On 04/28/2017 01:01 AM, Sumit Garg wrote:
Unify memory map for Layerscape based platforms as per DASH SDK
Do not mention internal project code name.
memory map. This patch includes changes in bootscript, bootscript
header and PPA header addresses change as per unified memory map.
This commit enables the RK3399 HDMI TX, which is very similar to the
one found on the RK3288. The differences between the two SoCs (mainly
the input VOP selection) is abstracted away through the driverdata.
Note that the I2C communication for reading the EDID works well with
the default settings,
This commit enables HDMI output in the DTS by adding the necessary
nodes to vopl/vopb and by adding the HDMI node.
Signed-off-by: Philipp Tomsich
---
arch/arm/dts/rk3399.dtsi | 110 +++
1 file changed, 110
This commit enables RK3399 support for HDMI through the following
changes:
- adds a driverdata structure to mirror some subtle version
differences between the RK3399 VOPs and those in the RK3288
(e.g. the pin-polarity configuration)
- configures the VOP to output 32bpp for HDMI
- handles
This series provides HDMI enablement for the RK3399 and will support
video console on the RK3399 either with VOP-lit or VOP-big:
- pinctrl and clk support for the hdmi node
- a refactoring of rk_vop.c and rk_hdmi.c to allow for the minor
differences between the RK3288 and RK3399 VOP and HDMI
To add HDMI support for the RK3399, this commit provides the needed
pinctrl functionality to configure the HDMI I2C pins (used for reading
the screen's EDID).
Signed-off-by: Philipp Tomsich
---
arch/arm/include/asm/arch-rockchip/grf_rk3399.h | 2 ++
This allows requests (via the DTS) for PCLK_HDMI_CTRL/PCLK_VIO_GRF,
which are clock gates in the HDMI output path for the RK3399.
As these are enabled by default (i.e. after reset), we don't implement
any logic to actively open/close these clock gates and simply assume
that their reset-default
On 04/27/2017 09:34 PM, Priyanka Jain wrote:
-Original Message-
From: York Sun [mailto:york@nxp.com]
Sent: Thursday, April 27, 2017 10:25 PM
To: Priyanka Jain ; u-boot@lists.denx.de
Cc: Suresh Gupta
Subject: Re: [u-boot-release] [PATCH
With the RK3399 DRAM controller (DMC) driver providing all the
infrastructure, retrieve the DRAM size from the DMC init in the
board-specific code (instead of hard-coding) for the RK3399-Q7 (Puma).
Signed-off-by: Philipp Tomsich
---
On 04/25/2017 06:50 PM, york sun wrote:
Commit 3f66149 dropped fdt_fixup_ethernet() from common/image-fdt.c,
presuming this function is called by ft_cpu_setup(). Add such call
in the mentioned function for Freescale ARMv8 Layerscape SoCs.
Signed-off-by: York Sun
---
On 04/28/2017 05:50 AM, Tom Rini wrote:
With 3f66149d9fb4 we no longer have a common call fdt_fixup_ethernet.
This was fine to do on PowerPC as they largely had calls already in
ft_cpu_fixup. On ARM however we largely relied on this call. Rather
than introduce a large number of changes to
Due to a typo, the 24 bit-per-pixel configuration ends in 24BMP
instead of 24BPP. This change renames it throughout the source tree
for consistency and to make moving these options into Kconfig easier
and less error-prone.
Signed-off-by: Philipp Tomsich
---
As the RK3399-Q7 (Puma) differs from our previous modules in how we
can force an external boot (on the RK3399-Q7 this holds the eMMC and
SPI in reset, until an external signal is removed) through the 'BIOS
disable'-signal of the Qseven specification, we can't derive the
unique board id reliably
From: Klaus Goger
Generate a MAC address based on the cpuid available in the efuse
block: Use the first 6 byte of the cpuid's SHA256 hash and set the
locally administered bits. Also ensure that the multicast bit is
cleared.
The MAC address is only generated
The (non-secure) efuse node in the DTS requests PCLK_EFUSE1024NS.
To allow us to add a efuse-driver (and more importantly, to allow
probes of such a driver to succeed), we need need to accept requests
for PCLK_EFUSE1024NS and return a non-error result.
As PCLK_EFUSE1024NS is enabled by default
With everything in place (i.e. the new efuse driver, the clk-support
for the non-secure efuse block, and the board-specific functions to
derive 'serial#' from the cpu-id within the efuses), enable this in
the RK3399-Q7 defconfig.
Signed-off-by: Philipp Tomsich
This adds a simple driver for reading the efuse block of the RK3399.
It should be easy enough to add drivers for other devices (e.g. the
RK3328, RK3368, etc.) by passing the device details via driver_data.
Unlike the kernel driver (using the nvmem subsystem), we don't expose
the efuse as multiple
With our efuse driver for the RK3399 ready, we can add the
board-specific code that consumes the cpuid from the efuse block and
postprocesses it into the system serial (using the same CRC32 based
derivation as in Linux).
We expose the cpuid via two distinct environment variables:
serial# - the
Instead of having drivers/video/rockchip/Kconfig point outside of its
hierarchy for dw_hdmi.o, we should use a configuration-option to
include the Designware HDMI support.
This change introduces a new config option (not to be selected via
menuconfig, but to be selected from a dependent video
On Fri, Apr 21, 2017 at 10:01:28AM -0500, Andrew F. Davis wrote:
> Almost all TI defconfigs enable this already, add this as a default
> and remove the explicit assignment.
>
> Signed-off-by: Andrew F. Davis
> Reviewed-by: Tom Rini
Applied to u-boot/master,
On Wed, Apr 26, 2017 at 11:35:19AM +0530, Lokesh Vutla wrote:
> Update Keystone2 secure device configs under
> "TI SYSTEM SECURITY". Without this buildman keeps complaining
> about the status of these boards.
>
> Signed-off-by: Lokesh Vutla
> Reviewed-by: Tom Rini
On Wed, Apr 19, 2017 at 04:46:37PM +0200, Philipp Tomsich wrote:
> This originally started out as
> "pinctrl: Kconfig: reorder to keep Rockchip options together"
> and tried to keep the Rockchip-related config options together.
>
> However, we now rewrite all chip-specific driver selections
On Wed, Apr 26, 2017 at 04:58:22PM +0530, Lokesh Vutla wrote:
> In file ext4fs.c funtion ext4fs_read_file() compares an
> unsigned expression with < 0 like below
>
> lbaint_t blknr;
> blknr = read_allocated_block(&(node->inode), i);
> if (blknr < 0)
> return -1;
>
On Tue, Apr 18, 2017 at 10:09:10PM +0300, Alexey Brodkin wrote:
> These were reminders that somehow slipped through the cracks
> or were erroneously introduced after previous clean-ups.
>
> Getting rid of then once again. Hopefully for good now :)
>
> Where missing and appropriate replace with
On Wed, Apr 19, 2017 at 03:09:04PM +0200, Philipp Tomsich wrote:
> An assignment (of a value to itself) was left over (after removing and
> addition from the line) from moving the common padding code into
> rkcommon_vrec_header.
>
> This change removes this to avoid a spurious warning in static
On Tue, Apr 25, 2017 at 11:07:46AM +0200, Patrice Chotard wrote:
> From: Patrice Chotard
>
> On ARM v7M, the processor will return to ARM mode when executing
> a blx instruction with bit 0 of the address == 0. Always set it
> to 1 to stay in thumb mode.
>
> Tested on
On Tue, Apr 25, 2017 at 01:10:11PM +0900, Masahiro Yamada wrote:
> In Linux, CONFIG_ARCH_OMAP2PLUS is used for OMAP2 or later SoCs.
> Rename CONFIG_ARCH_OMAP2 to CONFIG_ARCH_OMAP2PLUS to follow this
> naming.
>
> Move the OMAP2+ board/SoC choice down to mach-omap2/Kconfig to slim
> down the
On Sun, Apr 16, 2017 at 11:21:28AM +0530, Lokesh Vutla wrote:
> Standardise U-Boot prompt on all keystone2 platforms
> instead of platform specific prompt.
>
> Signed-off-by: Lokesh Vutla
> Reviewed-by: Tom Rini
Applied to u-boot/master, thanks!
--
On Fri, Apr 21, 2017 at 01:35:43PM +0300, Alexey Brodkin wrote:
> Finally adding support for ARC boards in TravisCI.
>
> To build for ARC boards we need to install Synopsys prebuilt toolchain
> which we do here.
>
> Signed-off-by: Alexey Brodkin
> Cc: Tom Rini
On 28.04.2017 14:51, Tom Rini wrote:
With 3f66149d9fb4 we no longer have a common call fdt_fixup_ethernet.
This was fine to do on PowerPC as they largely had calls already in
ft_cpu_fixup. On ARM however we largely relied on this call. Rather
than introduce a large number of changes to
On Thu, Apr 20, 2017 at 02:07:52PM +0530, Lokesh Vutla wrote:
> As per the DM[1] Dated June 2016–Revised February 2017, Table 5-3,
> DRA71 supports the following OPPs for various voltage domains:
>
> VDD_MPU: OPP_NOM
> VDD_CORE: OPP_NOM
> VDD_GPU: OPP_NOM
> VDD_DSPEVE: OPP_NOM,
On Mon, Apr 24, 2017 at 10:10:45AM +0200, Josua Mayer wrote:
> CONFIG_CMD_FS_UUID was neither whitelisted, nor was it declared in
> Kconfig.
> Now it can be enabled in .config and defconfig as expected.
>
> Signed-off-by: Josua Mayer
Applied to u-boot/master, thanks!
On Sun, Apr 16, 2017 at 09:01:11PM -0600, Simon Glass wrote:
> Unfortunately a test for the PWM uclass was not included when it was
> submitted. This was noticed when trying to add more functionality:
>
>http://patchwork.ozlabs.org/patch/748172/
>
> Add a simple test to get us started.
>
>
On Mon, Apr 17, 2017 at 09:18:00AM -0400, Tom Rini wrote:
> There are more and more cases where if we do not use gcc-6.0 or later we
> run into problems where our binaries are too large for the targets.
> Given the prevalence of gcc-6.0 or later toolchains at this point in
> time, we give notice
1 - 100 of 136 matches
Mail list logo