summaryrefslogtreecommitdiff
path: root/wiki/Chat_log/20160301-core-chatlog
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert+renesas@glider.be>2020-11-25 09:03:16 +0100
committerGeert Uytterhoeven <geert+renesas@glider.be>2020-11-25 09:09:08 +0100
commit3c2025406eac5dc155cb7053f486e82709f0da7c (patch)
treee7b119ca672ff15ff286baecc9d558b9b37ed6fa /wiki/Chat_log/20160301-core-chatlog
parent69f4ba5e612e3d7862fd5e909926aaf9ef11b080 (diff)
projects: linux: Update json-schema conversions
Several new conversions have been accepted upstream: - rcar-pci-host - rsnd - tmu Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Diffstat (limited to 'wiki/Chat_log/20160301-core-chatlog')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-28 11:23:33 +0000
; geertu> 2. Discussion Topics 09:37 < geertu> Topic 1. Status updates 09:37 < geertu> A) What have we done since last time: 09:37 < geertu> Kaneko-san sorted more nodes in arm64 DTS. 09:37 < geertu> Marek worked on ATF (Condor, DDR B, BSP upport), U-Boot (ULCB CPLD 09:37 < geertu> control tool, R8A66597 DM/DT), Linux (PCIe 32bit limitation and DMA 09:37 < geertu> range handling). 09:37 < geertu> Shimoda-san submitted PFC fixes. 09:37 < geertu> Simon cleant up DT binding doc filenames. 09:37 < geertu> Ulrich reviewed R-Car H1 DTS fixes. 09:37 < geertu> Geert reviewed the pwm-rcar/pfc/gpio patches, sent pull requests for 09:37 < geertu> v5.4 (arm-soc/pfc), submitted OSTM unique device names and always-on PM 09:37 < geertu> Domain fixes, did periject housekeeping, and improved ARM Cortex-A7/A9 09:37 < geertu> Errata selection. 09:38 < geertu> B) What we plan to do till next time: 09:38 < geertu> Marek plans to work on U-Boot (limited USB sticks, Migo-R and R2D 09:38 < geertu> DM/DT). 09:38 < geertu> Shimoda-san plans to ping the BSDL files, and continue preparing 09:38 < geertu> rcar-dmac patches for V3U. 09:38 < geertu> Simon plans to continue cleaning up DT binding doc filenames. 09:38 < geertu> Geert plans to send more pull requests for v5.4 for clk/pfc/arm-soc, and 09:38 < geertu> rework always-on PM Domain fixes, determine_rate() patches, and the GPIO 09:38 < geertu> aggregator. 09:38 < geertu> C) Problems we have currently: 09:38 < geertu> Geert wonders how to treat R-Car M3-W ES3.0 aka M3-W+. 09:38 < geertu> ---EOL--- 09:38 < geertu> Anything I missed? 09:39 < geertu> shimoda: About "Switching multiplexed LSI pins during operation is not guaranteed" 09:39 < geertu> I think this means that it cannot guarantee that there are no glitches 09:40 < geertu> For PWM output, glitches shouldn't harm much 09:41 < geertu> As the PWM hardware doesn't seem to finish the current cycle when changing PWM parameters, glitches cannot be avoided anyway. 09:45 < shimoda> geertu: sorry I cannot understand your last comment. is this related to gpio thing? or just PWM hardware? 09:46 < geertu> shimoda: My last comment was related to the rcar-pwm hardware 09:47 < geertu> IIRC, you replied that to a question from Uwe about finishing cycles? 09:49 < geertu> Oops, looks like I misread: "the hardware will complete the currently running period" 09:49 < shimoda> geertu: Yes, I replied to Uwe. this is a violation between PWM subsystem vs the rcar-pwm hardware. 09:49 < geertu> but not when disabling it. 09:51 < shimoda> pwm itself is no problem about glitches point of view, I think. 09:51 < shimoda> s/pwm/rcar-pwm hardware/ 09:51 < geertu> So the question for continuing with PWM/GPIO is: can we live with the glitches 09:54 < shimoda> geertu: I don't think we can live for now. Especially, any customer don's ask us about this topic for now. If customer wants such a feature, our hardware team will start to investigate how to achieve it :) 09:54 < geertu> OK 09:54 < geertu> case closed ;-) 09:54 < shimoda> :) 09:55 < geertu> I think that already counted as a Topic 2. Discussion Topics 09:55 < geertu> B) R-Car M3-W ES3.0 aka M3-W+ 09:56 < geertu> Eugeniu nicely summarized the possible approaches