arm64: renesas: add sound support
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v6 Latest posting 8/80 of 12 patches 0 repliesNew
- v6 posting 7/80 of 12 patches 0 repliesSuperseded
- v6 posting 6/80 of 12 patches 0 repliesSuperseded
Earlier versions · 5
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v6 posting 5/8 | 0 of 12 patches | 0 replies | Superseded | |
| v6 posting 4/8 | 0 of 12 patches | 0 replies | Superseded | |
| v6 posting 3/8 | 0 of 12 patches | 0 replies | Superseded | |
| v6 posting 2/8 | 0 of 12 patches | 0 replies | Superseded | |
| v6 posting 1/8 | 0 of 12 patches | 0 replies | Superseded |
Patches in v6 posting 8/8 No applies recorded yet
None of the 12 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v6 yet.
Cover letter [PATCH v6 00/12] arm64: renesas: add sound support
Quoted 15 lines · Geert Uytterhoeven
Hi Morimoto-san, Simon,
Quoted 11 lines · Kuninori Morimoto
Quoted 11 lines
Quoted 2 lines
I would like to check latest version.
Which branch/tag can I check ?If you want to check for apply-time and compile-time dependencies use the latest renesas-devel tag in my renesas tree.
If you want to check run-time you may need to pull in some dependencies, especially the cpg-mssr-v6 branch of Geert's renesas-drivers tree. A sledge-hammer approach would be to pull in the latest renesas-drivers tag of that tree.
Quoted 5 lines
Quoted 3 lines
Quoted 3 lines
In any case I'll need to know what run-time dependencies, other than cpg-mssr, are missing from renesas-next and/or renesas-devel so we can sensibly decide what to queue up.
This is about DT, which is independent from code? ;-)
Yes, I agree.
But I would at least like to get a handle on what the dependencies are. To make sure the bindings are on track. And to make sure there is some way to test the code.
Quoted 27 lines
Quoted 4 lines
Recent renesas-drivers sound has many conflicts, and sound has strange behavior. I had tried it before and noticed. I'm not sure latest one, but it has conflict log. I'm using a littile older kernel, because of above reason.
You mean the conflict when merging vsp1-kms-20151112~4?
As that branch is based on a very old renesas-drivers release, I made sure that merging it doesn't impact any sound driver. I.e. I reverted all changes not related to rcar-du and vsp1.You can verify using git diff
38f5d0b6..1f9e8ee5Quoted 1 line
Anyway, I tried below, and I could get sound.
Good, thanks for checking!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.orgIn personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds