Hi Benoit
On Thu, Jan 25, 2018 at 10:48:42PM +0100, Benoît Thébaudeau wrote:
> Hi Michael,
>
> On Thu, Jan 25, 2018 at 2:06 PM, Michael Trimarchi
> wrote:
> > SION bit should be used in the situation that we need
> > to read back the value of a pin and should not
The call to hash_block in passwd_abort fails with error ENOSPC on some
systems. The reason is that the variable which specifies the size of the
buffer to contain the computed hash does not get initialized.
This patch initializes the variable with the size of the buffer.
Signed-off-by: Martin
Hi Heinrich,
On 01/26/2018 12:28 PM, Jaehoon Chung wrote:
> Hi,
>
> On 01/26/2018 04:37 AM, Heinrich Schuchardt wrote:
>> With git master HEAD the Odroid C2 hangs after the command line countdown.
>>
>> Bisecting teaches that this is the patch causing the problem:
>>
>>
Hi Tom,
Please pull this PR.
Changes for v2:
- Fixed patches on wait_bit
- Collected new patches.
thanks!
Jagan.
The following changes since commit 98691a60abffb44303d7dae6e9e699d0daded930:
Merge git://git.denx.de/u-boot-rockchip (2018-01-09 13:28:51 -0500)
are available in the git
Now that we have %pD support in vsprintf we should avoid separate
logic for printing device paths in other places.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_bootmgr.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
On Tue, Jan 23, 2018 at 9:44 PM, Álvaro Fernández Rojas
wrote:
> BCM63xx SPI controller is a bit tricky since it doesn't allow keeping CS
> active between transfers, so I had to modify the spi_flash driver in order
> to allow limiting reads.
>
> v10: Introduce changes reported
On Wed, Jan 24, 2018 at 10:44 AM, Vignesh R wrote:
> This series reverts use of bounce_buf.c for non-DMA related alignment
> restriction and replaces it with local bounce buffer to handle problems
> with non 32 bit aligned writes on TI platforms.
> Based on top of Jason's series:
On Wed, Jan 24, 2018 at 4:43 AM, Jason Rush wrote:
> Adopt the Linux DT bindings. This also fixes an issue
> with the indaddrtrig register on the Cadence QSPI
> device being programmed with the wrong value for the
> socfpga arch.
>
> Tested on TI K2G platform:
> Tested-by:
On Thu, Jan 25, 2018 at 10:01 PM, Tom Rini wrote:
> On Thu, Jan 25, 2018 at 06:37:20PM +0530, Jagan Teki wrote:
>> On Thu, Jan 25, 2018 at 6:15 PM, Alexey Brodkin
>> wrote:
>> > Hi Jagan,
>> >
>> > On Fri, 2018-01-19 at 14:17 +0100, Eugeniy
Hi Joe,
> -Original Message-
> From: Joe Hershberger [mailto:joe.hershber...@ni.com]
> Sent: Wednesday, December 06, 2017 1:44 AM
> To: Calvin Johnson
> Cc: u-boot ; Joe Hershberger
> ; Anji Jagarlmudi
When printing '%pD' with a value of NULL we want to output
''. But this requires copying to buf. Leave this
to string16.
A unit test is supplied which relies on EFI support in the sandbox.
The development for EFI support in the sandbox is currently in branch
u-boot-dm/efi-working. The branch
On 01/26/2018 12:53 AM, Alexander Graf wrote:
There is a typo in the subject "efi_laoder".
When a UEFI payload just returns instead of calling the Exit() callback,
we handle that in efi_do_enter() and call Exit on its behalf, so that
the loaded_image->exit_status value is correct.
We were
Hi,
On 01/26/2018 04:37 AM, Heinrich Schuchardt wrote:
> With git master HEAD the Odroid C2 hangs after the command line countdown.
>
> Bisecting teaches that this is the patch causing the problem:
>
> 9546eb92cb648a8bba0aa9d5930ac751e6e5b9a4
> mmc: fix the wrong disabling clock
When you
Hi Vincenzo,
On Fri, Jan 26, 2018 at 2:58 AM, vnktux wrote:
> Hi all,
>
> This patch contain a working implementation of Broadwell-DE for U-Boot, and
> support memory down with external SPD binary file. However there is only one
> issue that I couldn't solve, the booting
Hi Mark,
On 26/01/2018 10:12, "Mathew McBride" wrote:
On 26/01/2018 8:01 AM, Bishop, Mark (STRT) wrote:
> Is it possible to specify squashFS images in an .its file? If so, anyone
> have an example or a pointer to the docs I've been searching for?
> Hi Mark,
>
It is
This patch adds a sec_init call into board_init. Doing so in conjunction
with the patch "drivers/crypto/fsl: assign job-rings to non-TrustZone"
enables use of the CAAM in Linux when OPTEE/TrustZone is active.
u-boot will initialise the RNG and assign ownership of the job-ring
registers to a
After enabling TrustZone various parts of the CAAM silicon become
inaccessible to non TrustZone contexts. The job-ring registers are designed
to allow non TrustZone contexts like Linux to still submit jobs to CAAM
even after TrustZone has been enabled.
The default job-ring permissions after the
V2:
- Add an explicit assignment of JRMID when setting job-ring ownership
Required on my reference part where the JRMID field is not set on the
third job-ring
V1:
This series is the u-boot fix to a problem we encountered when enabling
OPTEE/TrustZone on the WaRP7. The symptom is once
On 25/01/18 13:11, Lukas Auer wrote:
Extend the instantiate_rng() function and the corresponding CAAM job
descriptor to instantiate all RNG state handles. This moves the RNG
instantiation code in line with the CAAM kernel driver.
Previously, only the first state handle was instantiated. The
Hi Daniel,
2018-01-26 2:21 GMT+09:00 Daniel Schwierzeck :
> Extend the Kbuild's W=N option with an optional 'err' value. This
> will pass -Werror to the compiler to treat all warnings as errors.
> This is useful to enforce a zero-warnings policy.
>
> The 'err' value
Hi Boris,
On Wed, 24 Jan 2018 09:16:19 +0100
Boris Brezillon wrote:
> On Wed, 24 Jan 2018 01:44:51 +0100
> Miquel Raynal wrote:
>
> > Because using DMA implementation is not generic and was not developped
> > to work on
When a UEFI payload just returns instead of calling the Exit() callback,
we handle that in efi_do_enter() and call Exit on its behalf, so that
the loaded_image->exit_status value is correct.
We were missing that logic in StartImage(). Call it there too.
Reported-by: Heinrich Schuchardt
Hi Boris,
On Wed, 24 Jan 2018 09:06:38 +0100
Boris Brezillon wrote:
> On Wed, 24 Jan 2018 01:44:50 +0100
> Miquel Raynal wrote:
>
> > Do some cleaning in sunxi NAND SPL driver like adding helpers and
> > clearing flags at
On 26/01/2018 8:01 AM, Bishop, Mark (STRT) wrote:
Is it possible to specify squashFS images in an .its file? If so, anyone have
an example or a pointer to the docs I've been searching for?
Hi Mark,
It is possible, here is an example I have used on an NXP LS1043 board:
/dts-v1/;
/ {
Hi
On Thu, Jan 25, 2018 at 10:48 PM, Benoît Thébaudeau
wrote:
> Hi Michael,
>
> On Thu, Jan 25, 2018 at 2:06 PM, Michael Trimarchi
> wrote:
>> SION bit should be used in the situation that we need
>> to read back the value of a pin
Hi Michael,
On Thu, Jan 25, 2018 at 2:06 PM, Michael Trimarchi
wrote:
> SION bit should be used in the situation that we need
> to read back the value of a pin and should not be set by
> default macro.
>
> We get some malfunction as raised by following thread
>
>
Hi Folks,
This is a follow through on the discussion we have had in [1].
This itself is'nt a complete solution and is based on recommendation
This from Arm[2] for variant 2 CVE-2017-5715
The Linux kernel discussions are spread out in [3], ATF and OPTEE
status are available in [4].
This is just
As recommended by Arm in [1], ACR needs to be set[2] to enable
invalidation of BTB. This has to be enabled unconditionally for
ICIALLU to be functional on Cortex-A15 processors. Provide a config
option for platforms to enable this option based on impact analysis
for products.
NOTE: This patch in
As recommended by Arm in [1], IBE[2] has to be enabled unconditionally
for BPIALL to be functional on Cortex-A8 processors. Provide a config
option for platforms to enable this option based on impact analysis
for products.
NOTE: This patch in itself is NOT the final solution, this requires:
a)
On 01/25/2018 06:47 PM, Alexander Graf wrote:
> On 01/22/2018 07:34 PM, Heinrich Schuchardt wrote:
>> The appended README explains how U-Boot and iPXE can be used
>> to boot a diskless system from an iSCSI SAN.
>>
>> The maintainer for README.efi and README.iscsi is set.
>>
>> Signed-off-by:
On 01/25/2018 08:39 PM, Duncan Hare wrote:
>> - Forwarded Message -
>> From: Alexander Graf
>> To: Heinrich Schuchardt
>
>>> The appended README explains how U-Boot and iPXE can be used
>>> to boot a diskless system from an iSCSI SAN.
>>>
>>> The
Is it possible to specify squashFS images in an .its file? If so, anyone have
an example or a pointer to the docs I've been searching for?
Mark Bishop
Sr. Firmware/Software Engineer - Microwave Subsystems
[cid:image001.png@01D281ED.A45F0A90]
4726 Eisenhower Blvd.
Tampa, FL 33634
USA
T +1
The SOM has external pull-up resistors, so let's turn these off.
It was helping reduce some errors when running I2C1 @ 2.6MHz.
Signed-off-by: Adam Ford
diff --git a/board/logicpd/omap3som/omap3logic.h
b/board/logicpd/omap3som/omap3logic.h
index 22d7760..7376119 100644
---
For various peripherals on Rockchip SoCs (e.g. for the Ethernet GMAC),
the parent-clock needs to be set via the DTS. This adds the required
plumbing and implements the GMAC case for the RK3399.
Changes in v2:
- Fixed David's email address.
Philipp Tomsich (5):
clk: add clk_set_parent()
Linux uses the properties 'assigned-clocks', 'assigned-clock-parents'
and 'assigned-clock-rates' to configure the clock subsystem for use
with various peripheral nodes.
This implements clk_set_defaults() and hooks it up with the general
device probibin in drivers/core/device.c: when a new device
This implements the (newly added) set_parent() operation for the
RK3399 with a focus on allowing the RGMII clock parent to be
configured via the assigned-clock-parents property of the GMAC node.
This implementation supports only the GMAC (in fact only the RGMII
clock parent) and allows to set
The RK3399 CRU-node assigns rates to a number of clocks that are not
implemented in the RK3399 clock-driver (but which have been
sufficiently initialised from rkclk_init()): for these clocks, we
simply ignore the set_rate() operation and return 0 to signal success.
Signed-off-by: Philipp Tomsich
The logic in clk_get_by_index() may be useful for other properties
than 'clocks': e.g. 'assigned-clocks' and 'assigned-clock-parents'
follows the same model.
This commit refactors clk_get_by_index() by introducing an internal
function clk_get_by_indexed_prop() that allows to specify the name
of
Clocks may support multiple parents: this change introduces an
optional operation on the clk-uclass to set a clock's parent.
Signed-off-by: Philipp Tomsich
Tested-by: David Wu
---
Changes in v2:
- Fixed David's email address.
ehci_writel() swaps the arguments for address and value. One call
in ehci-mxs ignores that.
This fixes the warning:
drivers/usb/host/ehci-mxs.c: In function ?ehci_hcd_stop?:
drivers/usb/host/ehci-mxs.c:159:19: error: initialization makes integer from
pointer without a cast
> - Forwarded Message -
> From: Alexander Graf
> To: Heinrich Schuchardt
> > The appended README explains how U-Boot and iPXE can be used
> > to boot a diskless system from an iSCSI SAN.
> >
> > The maintainer for README.efi and README.iscsi is set.
With git master HEAD the Odroid C2 hangs after the command line countdown.
Bisecting teaches that this is the patch causing the problem:
9546eb92cb648a8bba0aa9d5930ac751e6e5b9a4
mmc: fix the wrong disabling clock
Please, revert the patch.
I could not find the patch in
From: Alexey Brodkin
Disabling relocation might be useful on ARC for 2 reasons:
a) For advanced debugging with Synopsys proprietary MetaWare debugger
which is capable of accessing much more specific hardware resources
compared to gdb. For example it may show
Finally GCC's garbage collector works on ARC so let's use it.
That's what I may see for HSDK:
Before:
textdata bss dec hex filename
290153 10068 222616 522837 7fa55 u-boot
After:
textdata bss dec hex filename
2619999460 222360 493819 788fb
This commit basically reverts two previous commits:
1. cf628f772ef2 ("arc: arcv1: Disable master/slave check")
2. 6cba327bd96f ("arcv2: Halt non-master cores")
With mentioned commits in-place we experience more trouble than
benefits. In case of SMP Linux kernel this is really required as
we
U-Boot is a bit special piese of software because it is being
only executed once on power-on as compared to operating system
for example. That's why we don't care much about performance
optimizations instead we're more concerned about size. And up-to-date
compilers might produce much smaller code
In case of no relocation we'll just waste some paceat the very end
of usable memory area. If U-Boot is huge and we cannot use a lot of memory this
loss will be pretty inconvenient.
Signed-off-by: Alexey Brodkin
Cc: Simon Glass
Cc: Bin Meng
On 01/22/2018 07:34 PM, Heinrich Schuchardt wrote:
The appended README explains how U-Boot and iPXE can be used
to boot a diskless system from an iSCSI SAN.
The maintainer for README.efi and README.iscsi is set.
Signed-off-by: Heinrich Schuchardt
---
MAINTAINERS |
Hi Philipp,
> > On 25 Jan 2018, at 18:37, Lukasz Majewski wrote:
> >
> > From: Anatolij Gustschin
> >
> > Selecting this option will reduce SPL boot time by approx. 6 ms
> > (e. g. with 70 bytes long banner string at 115200 baud).
> >
> > Signed-off-by: Anatolij
From: Anatolij Gustschin
Selecting this option will reduce SPL boot time by approx. 6 ms
(e. g. with 70 bytes long banner string at 115200 baud).
Signed-off-by: Anatolij Gustschin
Tested-by: Lukasz Majewski
Reviewed-by: Philipp Tomsich
> On 25 Jan 2018, at 18:37, Lukasz Majewski wrote:
>
> From: Anatolij Gustschin
>
> Selecting this option will reduce SPL boot time by approx. 6 ms
> (e. g. with 70 bytes long banner string at 115200 baud).
>
> Signed-off-by: Anatolij Gustschin
>
From: Anatolij Gustschin
Selecting this option will reduce SPL boot time by approx. 6 ms
(e. g. with 70 bytes long banner string at 115200 baud).
Signed-off-by: Anatolij Gustschin
Tested-by: Lukasz Majewski
---
common/spl/Kconfig | 7 +++
This implements the (newly added) set_parent() operation for the
RK3399 with a focus on allowing the RGMII clock parent to be
configured via the assigned-clock-parents property of the GMAC node.
This implementation supports only the GMAC (in fact only the RGMII
clock parent) and allows to set
The RK3399 CRU-node assigns rates to a number of clocks that are not
implemented in the RK3399 clock-driver (but which have been
sufficiently initialised from rkclk_init()): for these clocks, we
simply ignore the set_rate() operation and return 0 to signal success.
Signed-off-by: Philipp Tomsich
Linux uses the properties 'assigned-clocks', 'assigned-clock-parents'
and 'assigned-clock-rates' to configure the clock subsystem for use
with various peripheral nodes.
This implements clk_set_defaults() and hooks it up with the general
device probibin in drivers/core/device.c: when a new device
For various peripherals on Rockchip SoCs (e.g. for the Ethernet GMAC),
the parent-clock needs to be set via the DTS. This adds the required
plumbing and implements the GMAC case for the RK3399.
Philipp Tomsich (5):
clk: add clk_set_parent()
clk: refactor clk_get_by_index() into
Clocks may support multiple parents: this change introduces an
optional operation on the clk-uclass to set a clock's parent.
Signed-off-by: Philipp Tomsich
Tested-by: David Wu
---
drivers/clk/clk-uclass.c | 12
The logic in clk_get_by_index() may be useful for other properties
than 'clocks': e.g. 'assigned-clocks' and 'assigned-clock-parents'
follows the same model.
This commit refactors clk_get_by_index() by introducing an internal
function clk_get_by_indexed_prop() that allows to specify the name
of
Le 24/01/2018 à 15:00, Adam Ford a écrit :
Many boards are setting NAND parameters if/when CMD_NAND is set
when in reality they should probably be doing it it CONFIG_NAND
is set. Previuos attempts to make CMD_NAND select CONFIG_NAND
resulted in some recursive selections, so I think this
It may happen that the MXC serial IP block is performing some ongoing
transmission (started at e.g. board_init()) when the "initr_serial" is
called.
As a result the serial port IP block is reset, so transmitted data is
corrupted:
I2C: ready
DRAM: 1 GiB
jSS('HH��SL_SDHC: 04 rev 0x0
This patch
This forces all compiler warnings to be treated as errors.
Signed-off-by: Daniel Schwierzeck
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index 1e55e1b7f1..59d1dd99e8 100644
--- a/.travis.yml
+++
Add a new option '-E' for treating all compiler warnings as errors.
Eventually this will pass 'W=err' to Kbuild.
Signed-off-by: Daniel Schwierzeck
---
tools/buildman/builder.py | 5 -
tools/buildman/builderthread.py | 2 ++
tools/buildman/cmdline.py
The build script should not manipulate shell flags (especially '-e').
A non-zero exit value can also be catched with 'cmd || ret=$?'.
Signed-off-by: Daniel Schwierzeck
---
.travis.yml | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
Extend the Kbuild's W=N option with an optional 'err' value. This
will pass -Werror to the compiler to treat all warnings as errors.
This is useful to enforce a zero-warnings policy.
The 'err' value can also be combined with the numerical values
like this:
make W=1
make W=err
make
To enforce a zero-warnings policy (e.g. in CI builds), all compiler
warnings have to be treated as errors.
Extend Kbuild and buildman with according options to achieve this.
Enable these new options in all Travis CI builds. All builds with
compiler warnings will now fail. Only DTC warnings are
For the last return of function get_ram_size(),
when size=maxsize, restore the base address (*base)
content.
Add comment for the remaining case to avoid regression:
this case is already correctly handled.
Signed-off-by: Patrick Delaunay
---
Changes in v2:
- Solve issue
Save the content of the base address in a new variable
in stack (save_base) to prepare restore this content.
This patch don't modified code behavior and stack usage.
Signed-off-by: Patrick Delaunay
---
Changes in v2:
- Split patch in 2 part to more easily understood
Hi Wolfgang,
> From: Wolfgang Denk [mailto:w...@denx.de]
> Subject: Re: [U-Boot] [PATCH] common/memsize.c: restore content of the base
>
> Dear Patrick,
>
> In message <94c2391ea4e943fb9f65e7b0943c9...@sfhdag6node3.st.com>
> you wrote:
>
> > Ok, I will do it but only in background...
> > I
On 01/25/2018 04:53 PM, Bryan O'Donoghue wrote:
>
>
> On 25/01/18 13:11, Lukas Auer wrote:
>> Extend the instantiate_rng() function and the corresponding CAAM job
>> descriptor to instantiate all RNG state handles. This moves the RNG
>> instantiation code in line with the CAAM kernel driver.
>>
On Thu, Jan 25, 2018 at 06:37:20PM +0530, Jagan Teki wrote:
> On Thu, Jan 25, 2018 at 6:15 PM, Alexey Brodkin
> wrote:
> > Hi Jagan,
> >
> > On Fri, 2018-01-19 at 14:17 +0100, Eugeniy Paltsev wrote:
> >> Hi Jagan,
> >>
> >> Could you please pull these patches to your
On Thu, 2018-01-25 at 15:53 +, Bryan O'Donoghue wrote:
>
> On 25/01/18 13:11, Lukas Auer wrote:
> > Extend the instantiate_rng() function and the corresponding CAAM
> > job
> > descriptor to instantiate all RNG state handles. This moves the RNG
> > instantiation code in line with the CAAM
On 25/01/18 15:53, Bryan O'Donoghue wrote:
On 25/01/18 13:11, Lukas Auer wrote:
Extend the instantiate_rng() function and the corresponding CAAM job
descriptor to instantiate all RNG state handles. This moves the RNG
instantiation code in line with the CAAM kernel driver.
Previously, only
Hi Jagan,
El 24/01/2018 a las 7:57, Jagan Teki escribió:
On Tue, Jan 23, 2018 at 3:58 PM, Daniel Schwierzeck
wrote:
On 22.01.2018 21:55, Álvaro Fernández Rojas wrote:
Hi Daniel,
El 22/01/2018 a las 21:26, Daniel Schwierzeck escribió:
On 22.01.2018 18:14, Tom
On 25/01/18 13:11, Lukas Auer wrote:
Extend the instantiate_rng() function and the corresponding CAAM job
descriptor to instantiate all RNG state handles. This moves the RNG
instantiation code in line with the CAAM kernel driver.
Previously, only the first state handle was instantiated. The
On 24.01.2018 18:47, Alexey Brodkin wrote:
> Only ARM and in some configs MIPS really implement arch_fixup_fdt().
> Others just use the same boilerplate which is not good by itself,
> but what's worse if we try to build with disabled CONFIG_CMD_BOOTM
> and enabled CONFIG_OF_LIBFDT we'll hit an
On 01/25/18 09:27, Maxime Ripard wrote:
> On Wed, Jan 24, 2018 at 07:13:54AM -0600, Samuel Holland wrote:
>> On 01/24/18 02:38, Maxime Ripard wrote:
>>> Hi!
>>>
>>> On Tue, Jan 23, 2018 at 04:18:13PM -0600, Samuel Holland wrote:
If raw mode is disabled, CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR
On Wed, Jan 24, 2018 at 07:13:54AM -0600, Samuel Holland wrote:
> On 01/24/18 02:38, Maxime Ripard wrote:
> > Hi!
> >
> > On Tue, Jan 23, 2018 at 04:18:13PM -0600, Samuel Holland wrote:
> >> If raw mode is disabled, CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR is not
> >> defined, which breaks
On Thu, Jan 25, 2018 at 7:48 AM, Marek Behún wrote:
> Hi Alberto,
> Thanks. I just forwarded this to Robert Nelson who encountered this
> issue.
> You can add Reviewed-by: Marek Behun
Weird, wonder how my email failed to go thru.
Tested-by: Robert Nelson
On Thu, Jan 25, 2018 at 7:47 PM, Jason Rush wrote:
> On 1/23/2018 5:13 PM, Jason Rush wrote:
>> Adopt the Linux DT bindings. This also fixes an issue
>> with the indaddrtrig register on the Cadence QSPI
>> device being programmed with the wrong value for the
>> socfpga arch.
>>
On 1/23/2018 5:13 PM, Jason Rush wrote:
> Adopt the Linux DT bindings. This also fixes an issue
> with the indaddrtrig register on the Cadence QSPI
> device being programmed with the wrong value for the
> socfpga arch.
>
> Tested on TI K2G platform:
> Tested-by: Vignesh R
>
>
Hi,
Le mercredi 24 janvier 2018 à 15:21 -0600, Adam Ford a écrit :
> This converts the following to Kconfig:
>CONFIG_SYS_OMAP24_I2C_SLAVE
>CONFIG_SYS_OMAP24_I2C_SPEED
Thanks again for working on Kconfig'ing OMAP support, it is greatly
appreciated!
Reviewed-by: Paul Kocialkowski
Hi Alberto,
Thanks. I just forwarded this to Robert Nelson who encountered this
issue.
You can add Reviewed-by: Marek Behun
Marek
On Sat, 20 Jan 2018 09:17:57 +0200
Alberto Sánchez Molero wrote:
> Loading files stored with lzo compression from a btrfs
Hi Robert,
I just forwarded a patch by Alberto Mollero which should solve this
issue, could you test it and than maybe reply with Tested-by:?
Thanks.
Marek
On Fri, 15 Dec 2017 12:02:07 -0600
Robert Nelson wrote:
> Hi Marek,
>
> On Fri, Dec 15, 2017 at 11:43 AM, Marek
Extend the instantiate_rng() function and the corresponding CAAM job
descriptor to instantiate all RNG state handles. This moves the RNG
instantiation code in line with the CAAM kernel driver.
Previously, only the first state handle was instantiated. The second one
was instantiated by the CAAM
On Thu, Jan 25, 2018 at 6:15 PM, Alexey Brodkin
wrote:
> Hi Jagan,
>
> On Fri, 2018-01-19 at 14:17 +0100, Eugeniy Paltsev wrote:
>> Hi Jagan,
>>
>> Could you please pull these patches to your tree?
>> It would be really nice to see this patch in the nearest release.
SION bit should be used in the situation that we need
to read back the value of a pin and should not be set by
default macro.
We get some malfunction as raised by following thread
https://www.spinics.net/lists/linux-usb/msg162574.html
As reported by this application note:
On Fri, Jan 5, 2018 at 9:45 PM, Jun Nie wrote:
> Add fifo config for H3 as H3 differ with other SoC
> on ep number.
>
> Signed-off-by: Jun Nie
> Reviewed-by: Jagan Teki
> ---
> drivers/usb/musb-new/sunxi.c | 32
From: Stefan Agner
The input keycode KEY_POWER is used in the imx6ull.dtsi file,
hence include the input header where used.
Signed-off-by: Stefan Agner
---
arch/arm/dts/imx6ull-14x14-evk.dts | 1 -
arch/arm/dts/imx6ull.dtsi | 1 +
On Thu, Jan 25, 2018 at 10:43 AM, Michael Trimarchi
wrote:
> SION bit should be used in the situation that we need
> to read back the value of a pin and should not be set by
> default macro.
>
> We get some mulfuction as raised by following thread
malfunction
>
>
Hi Jagan,
On Fri, 2018-01-19 at 14:17 +0100, Eugeniy Paltsev wrote:
> Hi Jagan,
>
> Could you please pull these patches to your tree?
> It would be really nice to see this patch in the nearest release.
>
> Thanks.
>
> On Thu, 2017-12-28 at 15:09 +0300, Eugeniy Paltsev wrote:
> > Add option to
SION bit should be used in the situation that we need
to read back the value of a pin and should not be set by
default macro.
We get some mulfuction as raised by following thread
https://www.spinics.net/lists/linux-usb/msg162574.html
As reported by this application note:
Hello,
Be mild with me - my first patch to u-boot.
Signed-off-by: Arno Steffens
diff -Nur u-boot-2017.11/drivers/net/phy/smsc.c
u-boot-2017.11_patched/drivers/net/phy/smsc.c
--- u-boot-2017.11/drivers/net/phy/smsc.c 2017-11-14 02:08:06.0 +0100
+++
On Fri, Jan 5, 2018 at 9:45 PM, Jun Nie wrote:
> Allwinner H3 have a dual-routed USB PHY0 -- routed to either OHCI/EHCI
> or MUSB controller.
>
> Signed-off-by: Jun Nie
> ---
Reviewed-by: Jagan Teki
[Please do not top post in mailing lists]
On Thu, Jan 25, 2018 at 9:06 AM, Mehmet Ali İPİN
wrote:
> Dear Fabio,
>
> I checked my PHY KSZ9021 schematic (we used i.mx6 Dual Light) with boundary
> devices sabre_light_revD(they used i.mx6 quad) KSZ9021. We both use
Hi Fabio,
2018-01-21 15:57 GMT-02:00 Fabio Estevam :
> From: Fabio Estevam
>
> The original text is from the time that the config options were not
> converted to Kconfig.
>
> After the conversion to Kconfig only CONFIG_SECURE_BOOT and
>
Hi JJ,
On 01/25/2018 07:51 PM, Jean-Jacques Hiblot wrote:
>
> This series adds the missing bits to enable the UHS and HS200 modes
> for the TI platforms.
>
> Enabling support for high speed modes on omap5 requires implementing:
> * io signal voltage selection
> * tuning support
> * pin
Firmware on the Raspberry Pi family of devices can dynamically configure either
the PL011, Mini-UART or no device at all to be routed to the user accessible
UART pins.
That means we need to always include both drivers, because we can never be sure
which of the two serial devices firmware actually
We want to use Kconfig logic to depend on whether pl01x devices
are built in, so let's convert their inclusion selection to Kconfig.
This round goes to pl010.
Signed-off-by: Alexander Graf
---
arch/arm/Kconfig | 1 +
drivers/serial/Kconfig | 6 ++
The bcm283x mini-uart is only really usable as U-Boot serial output
when it is muxed to the UART pins of the RPi pin header.
So fail probing in case it is not muxed correctly, as in that case
firmware did not initialize it properly either.
Signed-off-by: Alexander Graf
---
The serial drivers now depend on the pinctrl driver to determine whether
they are enabled. That means if a serial device wants to be used pre-reloc,
we also need the pinctrl device pre-reloc.
Adapt the pinctrl driver as well as dts overlay accordingly.
Signed-off-by: Alexander Graf
1 - 100 of 206 matches
Mail list logo