s://lore.kernel.org/2c133f811fca225a0f796b8b94b16e63b33e56a6.ca...@physik.fu-berlin.de/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker.
m a quick skim of the linux kernel code.
> I believe it should look like the above, but lemme CC Geert to be on the
> safe side.
I have no idea. I removed the corresponding (but incomplete) code
from Linux in commit 25c7d77d695a4104 ("sh: boot: Remove sh5 cache
handling"), as it was
93 DTS from Linux
4.15-rc8")
Fixes: 9a26fc5a73fe2369 ("ARM: dts: rmobile: Import R8A7794 DTS from Linux
4.15-rc8")
Signed-off-by: Geert Uytterhoeven
---
Cfr.
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/commit/?h=clk-next&id=d6c5fc9add9eb7a0d5bd179ab07cbf43e32b28d8
I as
trying to probe the clocks.
>
> Fix this by filling in the pointers in the Gen2 code path with the
> values used before they where moved to struct cpg_mssr_info.
were
> Fixes: d413214fb748 ("clk: renesas: Add register pointers into struct
> cpg_mssr_info")
> Signed-off
Hi Yamada-san,
On Thu, Dec 14, 2023 at 7:12 AM Masahiro Yamada wrote:
> On Thu, Dec 14, 2023 at 1:03 PM Chen-Yu Tsai wrote:
> > On Sun, Dec 10, 2023 at 1:31 AM Geert Uytterhoeven
> > wrote:
> > > On Sat, Dec 9, 2023 at 4:29 PM Laurent Pinchart
> > > wrote:
&
a
setups[4][5]).
[1] arch/arm64/boot/dts/renesas/ulcb-kf.dtsi
[2] arch/arm64/boot/dts/renesas/*-ulcb.dts
[3] arch/arm64/boot/dts/renesas/*-ulcb-kf.dts
[4] arch/arm/boot/dts/renesas/r8a7742-iwg21d-q7-dbcm-ov5640-single.dtsi
[5] arch/arm/boot/dts/renesas/r8a7742-iwg21d-q7-dbcm-ov7725-single.d
tible string could be untied
> > from the base board's compatible string if needed (which we probably do).
> >
> > So something like:
> >
> > config {
> > config-1 {
> > compatible = "google,krane-sku0";
> > fdt = &quo
On Tue, Feb 28, 2023 at 10:28 PM Marek Vasut
wrote:
> Use CONFIG_RCAR_64 to make the driver available on both
> R-Car Gen3 and R-Car Gen4.
>
> Signed-off-by: Marek Vasut
LGTM, so
Reviewed-by: Geert Uytterhoeven
> --- a/drivers/spi/Kconfig
> +++ b/drivers/spi/Kconfig
ult)
U-Boot still contains include/configs/M5208EVBE.h, but there are no
actual users...
Angelo: so support for amcore in qemu would be nice ;-)
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In
hatever platforms interest them?
> Otherwise, sometime this year I'm likely to drop the architecture.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technica
atic void update_rpc_status(void *blob)
>
> int ft_board_setup(void *blob, struct bd_info *bd)
> {
> + apply_atf_overlay(blob);
> scrub_duplicate_memory(blob);
> update_rpc_status(blob);
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots
Hi Iwamatsu-san, Marek,
On Wed, Jun 15, 2022 at 4:34 PM Geert Uytterhoeven wrote:
> On Tue, Mar 29, 2022 at 2:19 PM Geert Uytterhoeven
> wrote:
> > On Renesas R-Car Gen3 platforms, the SPI Multi I/O Bus Controllers
> > (RPC-IF) provide access to HyperFlash or QSPI stora
On Tue, Mar 29, 2022 at 2:19 PM Geert Uytterhoeven
wrote:
> On Renesas R-Car Gen3 platforms, the SPI Multi I/O Bus Controllers
> (RPC-IF) provide access to HyperFlash or QSPI storage. On production
> systems, they are typically locked by the TF-A firmware, unless TF-A is
>
, hence the
most logical SoC-specific value is used, without specifying a
family-specific value.
Signed-off-by: Geert Uytterhoeven
---
Not strictly necessary.
Perhaps you prefer to do this in a future DTS sync with e.g. Linux
v5.19, to take care of the other differences in the RPC device nodes
RM: dts: rmobile: Disable RPC HF by
default")
[2] commit 361377dbdbc9f0f5 ("ARM: rmobile: Merge prior-stage firmware
DT fragment into U-Boot DT on Gen3")
Signed-off-by: Geert Uytterhoeven
---
board/renesas/rcar-common/common.c | 46 --
1 file changed, 44
is enabled by passing a DT fragment from TF-A to U-Boot, and
from U-Boot to subsequent software.
Fix this by renaming the device nodes from "rpc" to "spi".
Signed-off-by: Geert Uytterhoeven
---
Needs a similar patch to TF-A.
---
arch/arm/dts/r7s72100-gr-peach-u-boot.dts |
https://lore.kernel.org/r/3685623bed84674039adb61e723288d359ab0a50.1648544199.git.geert+rene...@glider.be
[2] "[PATCH 0/5] arm64: dts: renesas: rcar-gen3: Enable HyperFlash support"
https://lore.kernel.org/r/cover.1648548339.git.geert+rene...@glider.be
Geert Uytterhoeven (3):
ARM: dts: rmobile: Fix RPC-IF device nod
Hi Laurent,
On Tue, Jun 19, 2018 at 9:10 AM Laurent Pinchart
wrote:
> On Tuesday, 19 June 2018 09:58:59 EEST Geert Uytterhoeven wrote:
> > On Tue, Jun 19, 2018 at 4:15 AM Laurent Pinchart wrote:
> > > On Sunday, 17 June 2018 03:08:02 EEST Marek Vasut wrote:
> > >> O
call to get memory topology. It surprises me that it
> > >>>>> wouldn't.
> > >>>>
> > >>>> In fact, Laurent (CCed) was solving some similar issue with lossy
> > >>>> decomp
> > >>>> and I think th
hy they
> can't do that themselves if they have interest in it.
>
> BTW: m68k has the same kind of luggage, in the middle of it
> timekeeping code:
> arch/m68k/kernel/time.c
Fixing that means converting m68k to GPIO first, which would take lots of
heartbeats ;-)
Gr{oetje,eeti
r a slight difference in
behavior between two different i2c eeproms that were described the same before.
Oops.
P.S. I'd ike to point people to my presentation "Engaging Device Trees" at
ELC2014 (http://elinux.org/File:Engaging_Device_Trees_0.pdf).
Gr{oetje,eeting}s,
must be clarified in any case.
>> Like the latter overrides the former if clock phandles can be handled by
>> the environment. (And this should be stated in the binding.)
>
> Ah right. I don't think that naming is super critical though, as a lot
> of properties in the DT
22 matches
Mail list logo
