search for: renesa

...orked on, how likely they are to continue to be invested in, etc - versus accepting that companies have their own >>priorities, some private objectives, etc). No worries I’m very happy to provide any information necessary. I really want the port to accepted upstream. RL78 MCUs are part of the Renesas Product Longevity program https://www.renesas.com/eu/en/support/products-common/product-longevity-program-plp.html. The majority of current RL78 devices have the termination date set as “December 2033”, and a few “March 2026”. Also RL78 is under active development: new devices (which a much later...

...sy. >>Compatibility with an existing compiler is usually compelling - are the compilers you're trying to be compatible with publicly available/documented? Yes the compiler can be downloaded from here (is available for free with some restrictions compared to the paid version). https://www.renesas.com/in/en/products/software-tools/tools/compiler-assembler/compiler-package-for-rl78-family.html The documentation is available as well (in toolchain installer and website): https://www.renesas.com/in/en/doc/products/tool/doc/015/r20ut3123ej0109-ccrl.pdf >>The other aspect to new features,...

Hello all, For the past couple of months I've been writing a new llvm backend for Renesas RL78 MCU: https://www.renesas.com/eu/en/products/microcontrollers-microprocessors/rl78.html The software manual which contains all there is to know about RL78 is available here: https://www.renesas.com/us/en/doc/products/mpumcu/doc/rl78/r01us0015ej0220_rl78.pdf The motivation behind this is the f...

Hi All, I'm a Speex newbie wanting to figure if it's worth trying to get the fixed point decoder working on an M32C processor. It has a hardware 16x16->32 multiply and a 16x16+48->48 multiply/accumulate in about 8 cycles and runs at 25Mhz. No shortage of RAM. I'm confident that I could make it work and am willing to commit the effort, but before I do so I should ask: 1) Does

On Tue, Jun 9, 2020 at 8:04 PM Kieran Bingham <kieran.bingham+renesas at ideasonboard.com> wrote: > > The word 'descriptor' is misspelled throughout the tree. I think, *throughout the tree* is not appropriate* here. This patch has fixed it within the file. With that, Acked-by: Souptick Joarder <jrdr.linux at gmail.com> > > Fix it up a...

...Rolf Kemper, Manager, Mixed Signal Design, Networking, Renesas Electronics Europe GmbH, , Arcadiastr. 10, 40472, Duesseldorf, Germany, Phone:+49 211 6503-1475, Fax:+49 211 6503-1540, mailto:Rolf.Kemper@renesas.com, http://www.renesas.eu This message is intended only for the use of the address...{{dropped:24}}

...le" is missing from all but the implementations in > include/asm-generic/io.h. As my "volatile" comment applies to iowrite*(), too, probably that should be done in a separate patch. Hence with patches 1-5 squashed, and for patches 11-13: Reviewed-by: Geert Uytterhoeven <geert+renesas at glider.be> Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "program...

Dear Prof.Vikram. Really appreciate the hard work and determination in bringing LLVM concept. I had been a GCC contributor for almost 3-4 years, specially in backend with Renesas(SH) targets. Gone through http://llvm.org and found very challenging, seems to be better in many areas w.r.t GCC. Seeing the work of LLVM, am motivated to contribute to LLVM with reference to HPC needs. I maybe slow to start with but w.r.t time, will certainly pick up. Hopefully, Performance w.r....

...PCIe 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe 05:00.0 PCI bridge: Renesas Technology Corp. Device 001d 06:00.0 PCI bridge: Renesas Technology Corp. Device 001d 07:00.0 PCI bridge: Renesas Technology Corp. Device 001a 0a:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0a:00.1 Ethernet controller: Broadcom Corporation Ne...

Signed-off-by: Geert Uytterhoeven <geert+renesas at glider.be> --- mm/balloon_compaction.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/balloon_compaction.c b/mm/balloon_compaction.c index ba739b76e6c52e55..17ac81d8d26bcb50 100644 --- a/mm/balloon_compaction.c +++ b/mm/balloon_compaction.c @@ -60,7 +60,7 @@ EXPORT_S...

Signed-off-by: Geert Uytterhoeven <geert+renesas at glider.be> --- mm/balloon_compaction.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/balloon_compaction.c b/mm/balloon_compaction.c index ba739b76e6c52e55..17ac81d8d26bcb50 100644 --- a/mm/balloon_compaction.c +++ b/mm/balloon_compaction.c @@ -60,7 +60,7 @@ EXPORT_S...

On Thu, 29 Jun 2023 14:05:26 +0200, Wolfram Sang <wsa+renesas at sang-engineering.com> wrote: > vm_dev has a separate lifecycle because it has a 'struct device' > embedded. Thus, having a release callback for it is correct. > > Allocating the vm_dev struct with devres totally breaks this protection, device? or driver? And why? >...

On Wed, Jun 22, 2016 at 11:49 AM, Francis Greaves <francis at choughs.net> wrote: > More information... > I have pcifront showing as a module in the DomU and the usb shows in dmesg > as: > [ 3.167543] usbcore: registered new interface driver usbfs > [ 3.167563] usbcore: registered new interface driver hub > [ 3.167585] usbcore: registered new device driver usb >

...>> include/asm-generic/io.h. >> >> As my "volatile" comment applies to iowrite*(), too, probably that should be >> done in a separate patch. >> >> Hence with patches 1-5 squashed, and for patches 11-13: >> Reviewed-by: Geert Uytterhoeven <geert+renesas at glider.be> > > I'll add to this one also changes to ioreadX_rep() and add another > patch for volatile for reads and writes. I guess your review will be > appreciated once more because of ioreadX_rep() > volatile should really only be used where deemed necessary: https...

...N # revisit driver if we can enable big-endian ptes select IOMMU_API - select ARM_DMA_USE_IOMMU help Support for the IOMMU (System MMU) of Samsung Exynos application processor family. This enables H/W multimedia accelerators to see @@ -283,7 +281,6 @@ config IPMMU_VMSA depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64) select IOMMU_API select IOMMU_IO_PGTABLE_LPAE - select ARM_DMA_USE_IOMMU help Support for the Renesas VMSA-compatible IPMMU Renesas found in the R-Mobile APE6 and R-Car H2/M2 SoCs. @@ -304,7 +301,6 @@ config ARM_SMMU depends on (ARM64...

...series to fix drivers/i2c/[1], fix the terminology for users of > I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists > in the specification. > > Compile tested, no functionality changes intended > > [1]: https://lore.kernel.org/all/20240322132619.6389-1-wsa+renesas at sang-engineering.com/ > > Signed-off-by: Easwar Hariharan <eahariha at linux.microsoft.com> > --- > .../gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c | 8 +++--- > drivers/gpu/drm/amd/amdgpu/amdgpu_i2c.c | 10 +++---- > drivers/gpu/drm/amd/amdgpu/atombios_i2c.c...

...rivers/gpu/drm/amd/display/dc/dce60/Makefile | 2 +- drivers/gpu/drm/amd/display/dc/dce80/Makefile | 2 +- drivers/gpu/drm/i915/Makefile | 6 ++-- .../drm/nouveau/nvkm/subdev/bios/shadowof.c | 7 +++- drivers/gpu/drm/xe/Makefile | 4 +-- drivers/net/ethernet/renesas/sh_eth.c | 2 +- drivers/parport/parport_mfc3.c | 3 +- drivers/pinctrl/aspeed/Makefile | 2 +- drivers/scsi/cxlflash/lunmgt.c | 4 +-- drivers/scsi/cxlflash/main.c | 14 ++++---- drivers/scsi/cxlflash/superpipe.c...

...t initialized by the QXL driver and thus the This is still initialized, it's the ->disable that goes boom. At least the call to drm_crtc_helper_add is still there. The ->disable was removed in: commit 64581714b58bc3e16ede8dc37a025c3aa0e0eef1 Author: Laurent Pinchart <laurent.pinchart+renesas at ideasonboard.com> Date: Fri Jun 30 12:36:45 2017 +0300 drm: Convert atomic drivers from CRTC .disable() to .atomic_disable() Fixes: 64581714b58b ("drm: Convert atomic drivers from CRTC .disable() to .atomic_disable()") Cc: <stable at vger.kernel.org> # v4.14+ Reviewed...

Hi, Changes since v1 ================ https://lore.kernel.org/lkml/1578415992-24054-1-git-send-email-krzk at kernel.org/ 1. Constify also ioreadX_rep() and mmio_insX(), 2. Squash lib+alpha+powerpc+parisc+sh into one patch for bisectability, 3. Add Geert's review, 4. Re-order patches so all optional driver changes are at the end. Description =========== The ioread8/16/32() and others have

...1], fix the terminology for users of > > I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists > > in the specification. > > > > Compile tested, no functionality changes intended > > > > [1]: https://lore.kernel.org/all/20240322132619.6389-1-wsa+renesas at sang-engineering.com/ > > > > Signed-off-by: Easwar Hariharan <eahariha at linux.microsoft.com> > > --- > > .../gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c | 8 +++--- > > drivers/gpu/drm/amd/amdgpu/amdgpu_i2c.c | 10 +++---- > > drivers/gpu/drm/a...