Dear Heinrich,
In message <63fcd992-2d43-d168-64e8-7058c3a24...@gmx.de> you wrote:
>
> > Oops? Is it possible that you are not aware of the
> > tools/env/fw_env* code?
>
> I am fully aware of this.
OK, then why do you claim that U-Boot nvironment variables are not
"available to the operating
Hi Chris,
On Tue, Jun 25 2019, Chris Packham wrote:
> On Mon, Jun 24, 2019 at 8:30 PM Baruch Siach wrote:
>>
>> Reduce Auto Voltage Scaling VDD limit when core frequency is lower than
>> 1600MHz. This reduces core voltage level from 1.25V to 1.15V, which
>> saves power.
>>
>> The code is taken
On Tue, Jun 25, 2019 at 10:51 AM Ramon Fried wrote:
>
> On Mon, Jun 24, 2019 at 7:03 AM Anup Patel wrote:
> > The SiFive MACB ethernet has a custom TX_CLK_SEL register to select
> > different TX clock for 1000mbps vs 10/100mbps.
> >
> > This patch adds SiFive MACB compatible string and extends
> Subject: Re: [PATCH V2 1/3] test: dm: adc: use the real device name
>
> On Wed, Jun 19, 2019 at 02:17:59AM +, Peng Fan wrote:
> > Hi Simon, Tom
> > > Subject: [PATCH V2 1/3] test: dm: adc: use the real device name
> > >
> > > "adc" is not the real device name, "adc@0" is.
> > >
> > >
Hi Baruch,
On Mon, Jun 24, 2019 at 8:30 PM Baruch Siach wrote:
>
> Reduce Auto Voltage Scaling VDD limit when core frequency is lower than
> 1600MHz. This reduces core voltage level from 1.25V to 1.15V, which
> saves power.
>
> The code is taken from Marvell's U-Boot 2013.01 revision 18.06.
>
>
On Mon, Jun 24, 2019 at 7:03 AM Anup Patel wrote:
The SiFive MACB ethernet has a custom TX_CLK_SEL register to select
different TX clock for 1000mbps vs 10/100mbps.
This patch adds SiFive MACB compatible string and extends the MACB
ethernet driver to change TX clock using TX_CLK_SEL register
On Tue, Jun 25, 2019 at 7:15 AM Anup Patel wrote:
>
> Instead of depending on CONFIG_SYS_LITTLE_ENDIAN, we check at runtime
> whether underlying system is little-endian or big-endian. This way
> we are not dependent on any U-Boot specific OR compiler specific macro
> to check system endianness.
>
On 6/25/19 5:51 AM, Jonathan Gray wrote:
On Mon, Jun 24, 2019 at 02:11:43PM -0400, Tom Rini wrote:
On Wed, Jun 12, 2019 at 04:25:33PM -0400, Tom Rini wrote:
On Wed, Jun 12, 2019 at 10:21:22PM +0200, Heinrich Schuchardt wrote:
On 6/12/19 10:08 PM, Tom Rini wrote:
On Wed, Jun 12, 2019 at
On 6/25/19 3:10 AM, AKASHI Takahiro wrote:
On Mon, Jun 24, 2019 at 09:10:07PM +0200, Heinrich Schuchardt wrote:
On 6/24/19 8:50 PM, Wolfgang Denk wrote:
Dear Heinrich,
In message <7083d208-4b3c-7261-a03b-9066dc8d2...@gmx.de> you wrote:
to be really useful UEFI variables should be available
Instead of depending on CONFIG_SYS_LITTLE_ENDIAN, we check at runtime
whether underlying system is little-endian or big-endian. This way
we are not dependent on any U-Boot specific OR compiler specific macro
to check system endianness.
Signed-off-by: Anup Patel
Reviewed-by: Bin Meng
---
This patch extends SiFive FU540 board support to setup ethaddr
env variable based on board serialnum read from OTP.
Signed-off-by: Anup Patel
Reviewed-by: Bin Meng
---
board/sifive/fu540/fu540.c | 122 +
configs/sifive_fu540_defconfig | 1 +
2 files
Due changes in DT bindings, we now embed DTB from Linux-5.3 (or
higher) in OpenSBI FW_PAYLOAD along with payload u-boot.bin. This
patch updates SiFive FU540 README to reflect the changes in build
and boot steps.
Signed-off-by: Anup Patel
Reviewed-by: Bin Meng
Reviewed-by: Alistair Francis
---
The SiFive MACB ethernet has a custom TX_CLK_SEL register to select
different TX clock for 1000mbps vs 10/100mbps.
This patch adds SiFive MACB compatible string and extends the MACB
ethernet driver to change TX clock using TX_CLK_SEL register for
SiFive MACB.
Signed-off-by: Anup Patel
The GEMGXL clock driver is now directly part of Cadence MACB
ethernet driver in upstream Linux kernel. There is no separate
GEMGXL clock driver in upstream Linux kernel hence we drop
GEMGXL clock driver from U-Boot as well.
Signed-off-by: Anup Patel
Reviewed-by: Bin Meng
---
The DT bindings of SiFive clock driver in upstream Linux has
changes. As-per latest DT bindings, the clock driver takes two
parent clocks and compatible string has also changed.
This patch sync-up SiFive clock driver implementation as-per
upstream Linux so that we now use latest DT bindings.
Now that SiFive clock driver is merged in upstream Linux, we
sync-up WRPLL library used by SiFive clock driver with upstream
Linux sources.
Signed-off-by: Anup Patel
Reviewed-by: Bin Meng
---
drivers/clk/analogbits/wrpll-cln28hpc.c | 165 --
The location and license header of DT bindings header for SiFive
clock driver has changed in upstream Linux hence this patch.
Signed-off-by: Anup Patel
Reviewed-by: Bin Meng
---
drivers/clk/sifive/fu540-prci.c | 2 +-
include/dt-bindings/clk/sifive-fu540-prci.h | 29
To match SiFive clock driver with latest Linux, we factor-out PLL
library as separate module under drivers/clk/analogbits.
Signed-off-by: Anup Patel
Reviewed-by: Bin Meng
---
drivers/clk/Kconfig | 1 +
drivers/clk/Makefile
This series update SiFive Unleashed clock driver and Cadence MACB driver
so that:
1. It is in sync with upstream Linux driver
2. It uses latest DT bindings as-per upstream Linux driver
With this series, we can now use latest DT bindings with U-Boot. I have
tested SiFive Serial driver and Cadence
On Mon, Jun 24, 2019 at 6:37 PM Ramon Fried wrote:
>
>
> On 6/24/19 4:02 PM, Daniel Schwierzeck wrote:
> > can't you simply remove the non-DM part of the driver and add a
> > device-tree property for the endianess?
> >
> > If that's not possible short-term, than maybe add a Kconfig symbol like
>
Hello Heinrich,
Am 22.06.2019 um 21:12 schrieb Heinrich Schuchardt:
On 6/22/19 8:15 PM, Simon Glass wrote:
Hi,
On Sat, 22 Jun 2019 at 16:10, Andreas Färber wrote:
Hi Simon,
Am 22.06.19 um 16:55 schrieb Simon Glass:
I'd like to better understand the benefits of the 3-month timeline.
It
On Mon, Jun 24, 2019 at 02:11:43PM -0400, Tom Rini wrote:
> On Wed, Jun 12, 2019 at 04:25:33PM -0400, Tom Rini wrote:
> > On Wed, Jun 12, 2019 at 10:21:22PM +0200, Heinrich Schuchardt wrote:
> > > On 6/12/19 10:08 PM, Tom Rini wrote:
> > > >On Wed, Jun 12, 2019 at 10:07:31PM +0200, Heinrich
Hi Simon,
I forgot about these for a while, but I believe I addressed all the
feedback you still had in the latest version (v4). Looks like they
didn't get picked up anywhere though. Can you help?
On Thu, May 16, 2019 at 7:34 PM Simon Glass wrote:
>
> On Wed, 15 May 2019 at 16:30, Julius Werner
On Tue, Jun 25, 2019 at 4:00 AM Simon Goldschmidt
wrote:
>
> Am 30.05.2019 um 11:03 schrieb Ley Foon Tan:
> > Add base address for Intel Agilex SoC.
> >
> > Reuse base_addr_s10.h for Agilex, only one base address is
> > different from S10.
> >
> > Signed-off-by: Ley Foon Tan
> > ---
>
> Wait,
On Mon, Jun 24, 2019 at 09:10:07PM +0200, Heinrich Schuchardt wrote:
> On 6/24/19 8:50 PM, Wolfgang Denk wrote:
> >Dear Heinrich,
> >
> >In message <7083d208-4b3c-7261-a03b-9066dc8d2...@gmx.de> you wrote:
> >>
> >>to be really useful UEFI variables should be available to the operating
> >>system.
Hi Tom,
This patchset is to cleanup code, not bug fix, but it has been long time since
v1 and there
will be conflicts if defconfig changes or driver code change, and then there
will surely
need v9. So I pick up this patchset after collected several R-b and A-b tags.
CI:
On Tue, Jun 25, 2019 at 3:53 AM Simon Goldschmidt
wrote:
>
> Am 30.05.2019 um 11:03 schrieb Ley Foon Tan:
> > This is 2nd version of patchset to add Intel Agilex SoC[1] support.
>
> If this is v2, why doesn't the subject say so?
This is v2.
Forgot change the subject to v2 after sent the patches.
Hi Marek,
On Mon, 24 Jun 2019 at 11:10, Marek Vasut wrote:
>
> On 6/24/19 3:56 PM, Simon Glass wrote:
> > Hi Andreas,,
> >
> > On Sat, 22 Jun 2019 at 20:49, Andreas Färber wrote:
> >>
> >> Hi Simon,
> >>
> >> Am 22.06.19 um 21:14 schrieb Simon Glass:
> >>> On Sat, 22 Jun 2019 at 20:08, Andreas
On Tue, 25 Jun 2019, Ahmad Ijaz wrote:
> Hi Sir,
>
> I am trying to understand u-boot source code. As a starting point, I
> compiled u-boot for beaglebone black and successfully executed it on
> beaglebone hardware.
> My question is related to compilation step.
>
> The u-boot can be compiled with
Hi Sir,
I am trying to understand u-boot source code. As a starting point, I
compiled u-boot for beaglebone black and successfully executed it on
beaglebone hardware.
My question is related to compilation step.
The u-boot can be compiled with the following switches on *make.*
*1.
Frank Wunderlich schrieb am Mo., 24. Juni 2019,
22:09:
> You mean passing the offset (normal/redundant) instead of a bool?
>
Would you mind keeping the mail style of this list and stop top-responses
please?
I don't care where you make the difference between bool and actual offset,
but you
You mean passing the offset (normal/redundant) instead of a bool?
Am 24. Juni 2019 21:40:36 MESZ schrieb Simon Goldschmidt
:
>Am 28.04.2019 um 10:51 schrieb Frank Wunderlich:
>> this adds erase environment for mmc storage
>>
>> Signed-off-by: Frank Wunderlich
>
>I think this is still too
Am 30.05.2019 um 11:03 schrieb Ley Foon Tan:
Add base address for Intel Agilex SoC.
Reuse base_addr_s10.h for Agilex, only one base address is
different from S10.
Signed-off-by: Ley Foon Tan
---
Wait, this is v2, right? What hss changed since v1? I notice v2 has 15
patches while v1 had 14.
Am 30.05.2019 um 11:03 schrieb Ley Foon Tan:
This is 2nd version of patchset to add Intel Agilex SoC[1] support.
If this is v2, why doesn't the subject say so?
This patchset needs to apply after patch in [2] for Designware i2c clock from
DM.
Intel Agilex SoC is with a 64-bit quad core ARM
Am 12.06.2019 um 03:48 schrieb Ley Foon Tan:
Get clock rate from clock DM if CONFIG_CLK is enabled.
Otherwise, uses IC_CLK define.
Signed-off-by: Ley Foon Tan
Acked-by: Marek Vasut
Reviewed-by: Simon Goldschmidt
---
v2:
- Changed u32 to unsigned int for bus_mhz.
- Added ACK from Marek
Am 28.04.2019 um 10:51 schrieb Frank Wunderlich:
this adds erase environment for mmc storage
Signed-off-by: Frank Wunderlich
I think this is still too complex.
I'd drop patches 3/4 and 4/4 and just erase both redundant storages here
in env/mmc.c by calling the actual erase function twice.
Am 28.04.2019 um 10:51 schrieb Frank Wunderlich:
this patch adds basic changes for adding a erase-subcommand to env
with this command the environment stored on non-volatile storage written
by saveenv can be cleared.
Signed-off-by: Frank Wunderlich
Reviewed-by: Simon Goldschmidt
However,
Hi Frank,
Am 24.06.2019 um 12:30 schrieb Frank Wunderlich:
no opinion about the last version?
Sorry, I tried multiple times to review this but failed to find the
time. Seems like I found the time now ;-)
I'll reply to the original patch mails.
Regards,
Simon
regards Frank
Am 28.
Hi Heinrich,
On Sun, Jun 23, 2019 at 11:04 AM Heinrich Schuchardt wrote:
> With U-Boot HEAD I cannot see any difference between the files:
> $ md5sum u-boot*.bin
> 56a64c916b79c012759ad430a52fb2c1 u-boot.bin
> 56a64c916b79c012759ad430a52fb2c1 u-boot-dtb.bin
> ed69f924f0cb4b9415d0bed27f896be3
On 6/24/19 8:50 PM, Wolfgang Denk wrote:
Dear Heinrich,
In message <7083d208-4b3c-7261-a03b-9066dc8d2...@gmx.de> you wrote:
to be really useful UEFI variables should be available to the operating
system. This is not possible using U-Boot variables as storage.
Oops? Is it possible that you
Macb Ethernet controller requires a RX buffer of 128 bytes. It is
highly sub-optimal for Gigabit-capable GEM that is able to use
a bigger DMA buffer. Change this constant and associated macros
with data stored in the private structure.
RX DMA buffer size has to be multiple of 64 bytes as indicated
Dear Heinrich,
In message <7083d208-4b3c-7261-a03b-9066dc8d2...@gmx.de> you wrote:
>
> to be really useful UEFI variables should be available to the operating
> system. This is not possible using U-Boot variables as storage.
Oops? Is it possible that you are not aware of the
tools/env/fw_env*
Hi Heinrich,
On Mon, 24 Jun 2019 at 11:36, Heinrich Schuchardt wrote:
>
> On 6/24/19 3:56 PM, Simon Glass wrote:
> > On Sun, 16 Jun 2019 at 22:44, Heinrich Schuchardt
> > wrote:
> >>
> >> Avoid duplicate translation of arrow key codes.
> >>
> >> Signed-off-by: Heinrich Schuchardt
> >> ---
>
Hi Heinrich,
OK...I can't remember the details but there is a tool that does that. The
format that U-Boot's proftool emits is pretty standard. I recall using it
with a tool the kernel uses to get info like you are looking for.
Regards,
Simon
On Mon, 24 Jun 2019 at 11:30, Heinrich Schuchardt
On Mon, Jun 24, 2019 at 12:30:01PM +0200, Frank Wunderlich wrote:
> no opinion about the last version?
>
> regards Frank
>
> > Am 28. April 2019 10:51:24 MESZ schrieb Frank Wunderlich
> > :
> > >sometimes it is needed to erase the non-volatile environment
> > >e.g. for boot-up with
On Wed, Jun 12, 2019 at 04:25:33PM -0400, Tom Rini wrote:
> On Wed, Jun 12, 2019 at 10:21:22PM +0200, Heinrich Schuchardt wrote:
> > On 6/12/19 10:08 PM, Tom Rini wrote:
> > >On Wed, Jun 12, 2019 at 10:07:31PM +0200, Heinrich Schuchardt wrote:
> > >>On 6/12/19 9:56 PM, Tom Rini wrote:
> > >>>On
On 6/24/19 7:56 AM, Alexander Graf wrote:
Am 24.06.2019 um 00:01 schrieb Ard Biesheuvel :
On Sun, 23 Jun 2019 at 23:47, Alexander Graf wrote:
Am 23.06.2019 um 17:08 schrieb Heinrich Schuchardt :
Hello Alex,
on the i.MX6 Wandboard the Kernel crashes when booting via GRUB at least
On 6/24/19 12:23 PM, Wolfgang Denk wrote:
Dear Heinrich,
In message <83a2d8c5-1b06-c502-8a63-dc3ca307d...@gmx.de> you wrote:
thanks a lot for the good online meeting this morning together with your
colleague Suggan where we discussed the requirements for the
implementation of non-volatile
On 6/24/19 7:47 PM, Adam Ford wrote:
> On Mon, Jun 24, 2019 at 12:07 PM Marek Vasut wrote:
>>
>> The EHCI iMX6 driver is only partly converted to DT probing and
>> still uses a tremendous amount of hard-coded addresses. Worse,
>> the driver uses hard-coded SoC-model-specific base addresses, which
On Mon, Jun 24, 2019 at 12:07 PM Marek Vasut wrote:
>
> The EHCI iMX6 driver is only partly converted to DT probing and
> still uses a tremendous amount of hard-coded addresses. Worse,
> the driver uses hard-coded SoC-model-specific base addresses, which
> are derived from values protected by
On 6/24/19 3:56 PM, Simon Glass wrote:
On Sun, 16 Jun 2019 at 22:44, Heinrich Schuchardt wrote:
Avoid duplicate translation of arrow key codes.
Signed-off-by: Heinrich Schuchardt
---
common/usb_kbd.c | 31 +--
1 file changed, 9 insertions(+), 22 deletions(-)
On 6/24/19 3:56 PM, Simon Glass wrote:
Hi Heinrich,
On Sat, 22 Jun 2019 at 20:37, Heinrich Schuchardt wrote:
On 6/22/19 9:10 PM, Simon Glass wrote:
On Fri, 14 Jun 2019 at 20:51, Heinrich Schuchardt wrote:
There is no good reason to limit the trace buffer to 2GiB on a 64bit
system. Adjust
On Mon, 20 May 2019 at 01:19, Chris Packham wrote:
>
> On Sun, 19 May 2019, 4:07 AM Simon Glass, wrote:
>>
>> This script attempts to create a git commit which removes a single board.
>> It is quite fallible and everything it does needs checking. But it can
>> help speed up the process.
>>
>>
Hi,
On Fri, 19 Apr 2019 at 03:34, Marek Vasut wrote:
>
> On 4/18/19 2:30 PM, Vabhav Sharma wrote:
> > Hello Maintainers,
> > A gentle reminder to merge the changes.
>
> Next time, use
> $ ./scripts/get_maintainer.pl -f drivers/serial/serial_lpuart.c
> and actually CC the maintainers.
>
> >
On Wed, 15 May 2019 at 02:02, Chris Packham wrote:
>
> On Wed, May 15, 2019 at 9:54 AM Simon Glass wrote:
> >
> > This series updates patman to support Python 3:
> >
> > - Avoid using 'unicode' type directly
> > - Use items() instead of iteritems()
> > - Make sure file I/O uses binary mode where
Hi,
On Fri, 17 May 2019 at 22:01, Simon Glass wrote:
>
> This series updates both binman and dtoc to support Python 3 as well as
> Python 2. This mostly involves moving the code to use the 'bytes' type
> on Python 3 (with associated unicode conversions) but there are various
> other tweaks
On 6/24/19 3:56 PM, Simon Glass wrote:
> Hi Andreas,,
>
> On Sat, 22 Jun 2019 at 20:49, Andreas Färber wrote:
>>
>> Hi Simon,
>>
>> Am 22.06.19 um 21:14 schrieb Simon Glass:
>>> On Sat, 22 Jun 2019 at 20:08, Andreas Färber wrote:
Am 22.06.19 um 20:15 schrieb Simon Glass:
> On Sat, 22
The EHCI iMX6 driver is only partly converted to DT probing and
still uses a tremendous amount of hard-coded addresses. Worse,
the driver uses hard-coded SoC-model-specific base addresses, which
are derived from values protected by SoC-specific macros, hence the
driver is also compiled for a
From: Thomas Schaefer
During QSPI reads, current is_busy_controller function sporadically
fails with -ETIMEDOUT due to fixed number of 5 test loops. This patch
fixes this by using the readl_poll_timeout function with
1000 us timeout.
Signed-off-by: Thomas Schaefer
Signed-off-by: Fabio Estevam
Hi Vabhav,
On Thu, 18 Apr 2019 at 06:30, Vabhav Sharma wrote:
>
> Hello Maintainers,
> A gentle reminder to merge the changes.
>
> Regards,
> Vabhav
>
> > -Original Message-
> > From: Vabhav Sharma
> > Sent: Thursday, January 31, 2019 5:38 PM
> > To: u-boot@lists.denx.de;
Like the other Logic PD OMAP35/DM37 boards, this board has device
tree enabled for U-Boot. This patch converts the board to enable
SPL_OF_CONTROL and further shrinks the device tree in SPL to limit
it to UART3 (console), MMC1, i2c1, and GPIO4 (for mmc1 CD and WP).
There appears to be a bug in
On 6/24/19 5:21 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Now that we removed all legacy boards selecting TI_EMAC we can
> completely convert the driver code to using the driver model.
> This patch also updates all remaining users of davinci_emac.
>
> Signed-off-by: Bartosz
On Mon, Jun 24, 2019 at 9:21 AM Bartosz Golaszewski wrote:
>
> From: Bartosz Golaszewski
>
> Now that we removed all legacy boards selecting TI_EMAC we can
> completely convert the driver code to using the driver model.
> This patch also updates all remaining users of davinci_emac.
>
>
Hi Thomas,
On Mon, Jun 24, 2019 at 12:47 PM Thomas Schaefer
wrote:
> Following Fabio's suggestion I have prepared the following patch that fixes
> the QSPI read support issue of the fsl_qspi driver on my i.MX7D Sabre eval
> system. Could you please review/check this patch and introduce it
On Wed, Jun 19, 2019 at 02:17:59AM +, Peng Fan wrote:
> Hi Simon, Tom
> > Subject: [PATCH V2 1/3] test: dm: adc: use the real device name
> >
> > "adc" is not the real device name, "adc@0" is.
> >
> > Signed-off-by: Peng Fan
>
> Will you pick up this patchset?
>
Hi all,
> Hi Fabio,
>
> > Hi Thomas,
> >
> > On Wed, Jun 19, 2019 at 10:04 AM Thomas Schaefer
> > wrote:
> > >
> > > Hi all,
> > >
> > > I've built current u-boot (v2019.07-rc4) with QSPI support for our i.MX7D
> > > Sabre eval system. I am using mx7dsabresd_qspi_defconfig.
> > >
> > > The
On Sat, Jun 22, 2019 at 09:43:42PM +0200, Marek Vasut wrote:
> On 6/22/19 9:12 PM, Heinrich Schuchardt wrote:
> > On 6/22/19 8:15 PM, Simon Glass wrote:
> >> Hi,
> >>
> >> On Sat, 22 Jun 2019 at 16:10, Andreas Färber wrote:
> >>>
> >>> Hi Simon,
> >>>
> >>> Am 22.06.19 um 16:55 schrieb Simon
On Mon, Jun 24, 2019 at 03:04:41PM +0200, Harald Seiler wrote:
> Hello Peng,
>
> On Thu, 2019-06-20 at 06:42 +, Peng Fan wrote:
> > Hi Wolfgang,
> >
> [...]
> > >
> > > The switch will take place as follows:
> > >
> > > 1. We will create user accounts for all custodians at gitlab.denx.de
>
pon., 24 cze 2019 o 15:39 Adam Ford napisał(a):
>
> On Mon, Jun 24, 2019 at 7:07 AM Bartosz Golaszewski wrote:
> >
> > śr., 12 cze 2019 o 18:46 Adam Ford napisał(a):
> > >
> > > On Mon, Jun 3, 2019 at 10:29 AM Bartosz Golaszewski wrote:
> > > >
> > > > pon., 3 cze 2019 o 15:03 Adam Ford
From: Bartosz Golaszewski
Now that we removed all legacy boards selecting TI_EMAC we can
completely convert the driver code to using the driver model.
This patch also updates all remaining users of davinci_emac.
Signed-off-by: Bartosz Golaszewski
---
v1 -> v2:
- moved the packetp assignment to
This patch series brings the files from Linux kernel (SHA1: 5752b50477da
Linux 5.1.12 to provide clocks support as it is used on the Linux kernel
with Common Clock Framework [CCF] setup.
This series also fixes several problems with current clocks and provides
sandbox tests for functions added to
Hello,
sorry I am completely new to these kind of mailing lists, and quite probably I
violate most of the rules for using this mailing list, but I have a serious bug
to report and actually no time at all...
/u-boot_2019/drivers/mtd/nand/raw/omap_gpmc.c - function
omap_nand_read_prefetch():
On Sun, 16 Jun 2019 at 22:44, Heinrich Schuchardt wrote:
>
> Avoid duplicate translation of arrow key codes.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> common/usb_kbd.c | 31 +--
> 1 file changed, 9 insertions(+), 22 deletions(-)
Reviewed-by: Simon Glass
We
Hi Andreas,,
On Sat, 22 Jun 2019 at 20:49, Andreas Färber wrote:
>
> Hi Simon,
>
> Am 22.06.19 um 21:14 schrieb Simon Glass:
> > On Sat, 22 Jun 2019 at 20:08, Andreas Färber wrote:
> >> Am 22.06.19 um 20:15 schrieb Simon Glass:
> >>> On Sat, 22 Jun 2019 at 16:10, Andreas Färber wrote:
>
Hi Heinrich,
On Sat, 22 Jun 2019 at 20:37, Heinrich Schuchardt wrote:
>
> On 6/22/19 9:10 PM, Simon Glass wrote:
> > On Fri, 14 Jun 2019 at 20:51, Heinrich Schuchardt
> > wrote:
> >>
> >> There is no good reason to limit the trace buffer to 2GiB on a 64bit
> >> system. Adjust the types of the
Enable by default the Common Clock Framework [CCF] clock code for sandbox.
Signed-off-by: Lukasz Majewski
---
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
configs/sandbox_defconfig | 1 +
configs/sandbox_flattree_defconfig | 1 +
2 files changed, 2
This patch adds the 'osc' fixed clock to facilitate the CCF testing in
the sandbox U-Boot. It is a starting point for building CCF hierarchy of
clocks.
Signed-off-by: Lukasz Majewski
---
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
arch/sandbox/dts/test.dts
This patch provides code to implement the CCF clock tree in sandbox. It
uses all the introduced primitives; some generic ones are reused, some
sandbox specific were developed.
In that way (after introducing the real CCF tree in sandbox) the recently
added to clk-uclass.c: clk_get_by_id() and
This patch brings the files from Linux kernel (linux-stable/linux-5.1.y
SHA1: 5752b50477da)to provide clocks support as it is used on the Linux
kernel with Common Clock Framework [CCF] setup.
The directory structure has been preserved. The ported code only supports
reading information from PLL,
The generic divider clock code for CCF requires reading the divider value
from HW registers. As sandbox by design has readl() as no-op it was
necessary to provide this value in the other way.
The new field in the divider structure (accessible only when sandbox is
run) has been introduced for this
The generic mux clock code for CCF requires reading the clock multiplexer
value from HW registers. As sandbox by design has readl() as no-op it was
necessary to provide this value in the other way.
The new field in the mux structure (accessible only when sandbox is run)
has been introduced for
This file now stores the dev_get_clk_ptr() wrapper on the dev_get_uclass_priv()
function.
Signed-off-by: Lukasz Majewski
---
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
include/linux/clk-provider.h | 16
1 file changed, 16 insertions(+)
This commit adds the clk_get_parent() function, which is responsible
for getting the parent's struct clock pointer.
U-Boot's DM support for getting parent is different (the parent
relationship is in udevice) than the one in Common Clock Framework [CCF]
in Linux. To obtain the pointer to struct
This commit adds the clk_get_parent_rate() function, which is responsible
for getting the rate of parent clock.
Unfortunately, u-boot's DM support for getting parent is different
(the parent relationship is in udevice) than the one in Common Clock
Framework [CCF] in Linux.
To alleviate this
This commit adds the clk_get_by_id() function, which is responsible
for getting the udevice with matching clk->id. Such approach allows
re-usage of inherit DM list relationship for the same class (UCLASS_CLK).
As a result - we don't need any other external list - it is just enough
to look for
The clock subsystem needs active maintenance as it steadily grows.
I do offer my help for this task.
Signed-off-by: Lukasz Majewski
---
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git
If the CLK_GET_RATE_NOCACHE flag is set - the clk_get_parent_rate()
provides recalculated clock value without considering the cache setting.
This may be necessary for some clocks tightly coupled with power domains
(i.e. imx8), and prevents from reading invalid cached values.
Signed-off-by:
Up till now the fixed rate clock ('osc') has been added to UCLASS_CLK
without declaring struct clk. As a result it was only accessible by
iterating the udevice's uclass list.
This is a problem for clock code, which operates on pointers to struct
clk (like clk_get_rate()), not udevices.
After
This commit extends the struct clk to provide information regarding the
flags related to this devices.
Those flags are clk device agnostic and indicate generic features
(like e.g. CLK_GET_RATE_NOCACHE - the need to always recalculate the rate).
Signed-off-by: Lukasz Majewski
Reviewed-by: Peng
This check requires the struct clk passed to .get_rate() to be always
cleared out as any clock with valid ID causes -EINVAL return value.
The return code of fixed clocks shall always be returned.
Signed-off-by: Lukasz Majewski
Reviewed-by: Peng Fan
---
Changes in v6: None
Changes in v5: None
This commit extends the struct clk to provide information regarding the
clock rate.
As a result the clock tree traversal is performed at most once, and further
reads are using the cached value.
Signed-off-by: Lukasz Majewski
---
Changes in v6: None
Changes in v5:
- Use long long to store rate
There is no UCLASS_CLOCK uclass defined. Instead we do use the UCLASS_CLK.
Signed-off-by: Lukasz Majewski
Reviewed-by: Simon Glass
Reviewed-by: Peng Fan
---
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
include/clk.h | 2 +-
1 file changed, 1 insertion(+),
This patch describes the design decisions considerations and taken approach
for porting in a separate documentation entry.
Signed-off-by: Lukasz Majewski
---
Changes in v6: None
Changes in v5:
- s/U-boot/U-Boot/g
- Update Linux version to 5.1.12
- Add paragraph regarding sandbox CCF testing
On Mon, Jun 24, 2019 at 7:07 AM Bartosz Golaszewski wrote:
>
> śr., 12 cze 2019 o 18:46 Adam Ford napisał(a):
> >
> > On Mon, Jun 3, 2019 at 10:29 AM Bartosz Golaszewski wrote:
> > >
> > > pon., 3 cze 2019 o 15:03 Adam Ford napisał(a):
> > > >
> > > > On Mon, Jun 3, 2019 at 3:12 AM Bartosz
On 6/24/19 4:12 PM, Bin Meng wrote:
> Hi Ramon,
>
> On Mon, Jun 24, 2019 at 8:51 PM Ramon Fried wrote:
>>
>> On 6/24/19 3:32 PM, Bin Meng wrote:
>>> Hi Ramon,
>>>
>>> On Mon, Jun 24, 2019 at 8:22 PM Ramon Fried wrote:
On 6/24/19 8:03 AM, Bin Meng wrote:
On Mon, Jun 24, 2019 at
Hi Ramon,
On Mon, Jun 24, 2019 at 8:51 PM Ramon Fried wrote:
>
>
> On 6/24/19 3:32 PM, Bin Meng wrote:
> > Hi Ramon,
> >
> > On Mon, Jun 24, 2019 at 8:22 PM Ramon Fried wrote:
> >>
> >> On 6/24/19 8:03 AM, Bin Meng wrote:
> >>
> >> On Mon, Jun 24, 2019 at 12:03 PM Anup Patel wrote:
> >>
> >>
Hi Marek,
> On 6/24/19 1:57 PM, Lukasz Majewski wrote:
> > Hi Marek,
> >
> >> On 6/24/19 12:26 PM, Lukasz Majewski wrote:
> >>> On Mon, 24 Jun 2019 12:06:28 +0200
> >>> Marek Vasut wrote:
> >>>
> On 6/24/19 8:33 AM, Peng Fan wrote:
> > Hi Marek,
> >
> >>
On 6/24/19 4:02 PM, Daniel Schwierzeck wrote:
> can't you simply remove the non-DM part of the driver and add a
> device-tree property for the endianess?
>
> If that's not possible short-term, than maybe add a Kconfig symbol like this:
>
> config MACB_BIG_ENDIAN
> bool ""
> depends on
Hello Peng,
On Thu, 2019-06-20 at 06:42 +, Peng Fan wrote:
> Hi Wolfgang,
>
[...]
> >
> > The switch will take place as follows:
> >
> > 1. We will create user accounts for all custodians at gitlab.denx.de
> >You will receive an e-mail notification with your login
> >credentials.
On Mon, Jun 24, 2019 at 2:51 PM Ramon Fried wrote:
>
>
> On 6/24/19 3:32 PM, Bin Meng wrote:
> > Hi Ramon,
> >
> > On Mon, Jun 24, 2019 at 8:22 PM Ramon Fried wrote:
> >>
> >> On 6/24/19 8:03 AM, Bin Meng wrote:
> >>
> >> On Mon, Jun 24, 2019 at 12:03 PM Anup Patel wrote:
> >>
> >> We should
1 - 100 of 148 matches
Mail list logo
