diff options
Diffstat (limited to 'projects/linux/io')
29 files changed, 502 insertions, 95 deletions
diff --git a/projects/linux/io/I2C-add-atomic_xfer.yaml b/projects/linux/io/I2C-add-atomic_xfer.yaml new file mode 100644 index 0000000..b3f3a7a --- /dev/null +++ b/projects/linux/io/I2C-add-atomic_xfer.yaml @@ -0,0 +1,11 @@ +title: I2C; add atomic_xfer callbacks +team: IO +key: 30697a96-203e-11eb-98aa-cf61d186fbec +assignee: Ulrich +status: Active + +upstream: + +comments: + - "created seperate task from the already finished IIC task" + - "Wolfram provided test case to Ulrich" diff --git a/projects/linux/io/I2C-add_RECV_LEN-support.yaml b/projects/linux/io/I2C-add_RECV_LEN-support.yaml new file mode 100644 index 0000000..5720a4d --- /dev/null +++ b/projects/linux/io/I2C-add_RECV_LEN-support.yaml @@ -0,0 +1,12 @@ +title: I2C; add RECV_LEN support to the i2c-rcar driver +team: IO +key: 3c3dd6fe-03d9-11eb-ad24-7782efa69bb6 +assignee: Wolfram +status: Paused + +comments: + - "I2C core update:" + - "RFC v1: http://patchwork.ozlabs.org/project/linux-i2c/patch/20200728004708.4430-1-daniel.stodden@gmail.com/" + - "RFC v2: http://patchwork.ozlabs.org/project/linux-i2c/patch/20200729203658.411-1-daniel.stodden@gmail.com/" + - "I2C driver update:" + - "working prototype is implemented" diff --git a/projects/linux/io/I2C-dynamic_client_addresses.yaml b/projects/linux/io/I2C-dynamic_client_addresses.yaml index 5dc820d..4ffe54c 100644 --- a/projects/linux/io/I2C-dynamic_client_addresses.yaml +++ b/projects/linux/io/I2C-dynamic_client_addresses.yaml @@ -2,7 +2,7 @@ title: I2C; dynamic client address infrastructure for the core team: IO key: 60a472ea-1c32-4f6e-a693-c5f4298ef20a assignee: Wolfram -status: Blocked +status: Paused relationships: - depends: 6f15b8c0-7ff6-43aa-a47a-7341694c37af @@ -16,3 +16,6 @@ comments: - "RFC v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=222619&state=*" - "preparational series to block addresses in DT needed first" - "prep series v1: http://patchwork.ozlabs.org/project/linux-i2c/list/?series=159794&state=*" + - "prep series v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=258263&state=*" + - "refactored bindings docs as preparation: https://patchwork.kernel.org/patch/11491099/" + - "not enough worktime for this currently" diff --git a/projects/linux/io/IIC-fix_arb_lost.yaml b/projects/linux/io/IIC-fix_arb_lost.yaml index b9eb880..fe760a1 100644 --- a/projects/linux/io/IIC-fix_arb_lost.yaml +++ b/projects/linux/io/IIC-fix_arb_lost.yaml @@ -3,7 +3,6 @@ team: IO key: 2fb3d3ef-f2dc-4229-860c-0e64fa13e4f4 assignee: Wolfram status: Paused -target-date: 2019-06-30 upstream: diff --git a/projects/linux/io/PCI-fix-suspend.yaml b/projects/linux/io/PCI-fix-suspend.yaml new file mode 100644 index 0000000..e634ac0 --- /dev/null +++ b/projects/linux/io/PCI-fix-suspend.yaml @@ -0,0 +1,17 @@ +title: "PCIe: handle suspend problem" +team: IO +key: 61128a40-edce-11ea-90d7-7f8bdf62ff21 +status: Active +assignee: Marek + +upstream: + +comments: + - "PCIe suspend causes an exception which needs to be handled" + - "For Gen3, a fix was made for ATF: https://github.com/ARM-software/arm-trusted-firmware/commit/0969397f295621aa26b3d14b76dd397d22be58bf" + - "For Gen2, a similar approach needs to be taken with hooks for Linux exception handling" + - "v1: https://patchwork.kernel.org/patch/11772083/" + - "v2: https://patchwork.kernel.org/patch/11801531/" + - "v3: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20201011160045.574323-1-marek.vasut@gmail.com/" + - "v4: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20201016120416.7008-1-marek.vasut@gmail.com/" + - "on-going disucssion with PCI maintainers" diff --git a/projects/linux/io/PCI-review-endpoint-support.yaml b/projects/linux/io/PCI-review-endpoint-support.yaml deleted file mode 100644 index 5c5be15..0000000 --- a/projects/linux/io/PCI-review-endpoint-support.yaml +++ /dev/null @@ -1,16 +0,0 @@ -title: "Review patch series for PCI endpoint support" -team: IO -key: 312f9fca-3325-11ea-8113-002170711890 -status: New -assignee: Marek - -relationships: - -upstream: - -comments: - - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=199045&state=*" - - "v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=216247&state=*" - - "v3: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=225521&state=*" - - "v4: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=238723&state=*" - - "v5: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=249127&state=*" diff --git a/projects/linux/io/SCIF-investigate-DMA-limitations.yaml b/projects/linux/io/SCIF-investigate-DMA-limitations.yaml new file mode 100644 index 0000000..e86cfcc --- /dev/null +++ b/projects/linux/io/SCIF-investigate-DMA-limitations.yaml @@ -0,0 +1,8 @@ +title: SCIF; check DMA problems with SysRq, BREAK and parity errors +team: IO +key: 3cdb3c8c-03d9-11eb-91e0-b7234f6a00bc +status: New + +comments: + - "check IO IRC log from 2020-10-01 for details" + diff --git a/projects/linux/io/SDHI-HW-busy-timeout.yaml b/projects/linux/io/SDHI-HW-busy-timeout.yaml index 0c260f4..e3f2857 100644 --- a/projects/linux/io/SDHI-HW-busy-timeout.yaml +++ b/projects/linux/io/SDHI-HW-busy-timeout.yaml @@ -1,7 +1,7 @@ title: SDHI; implement support for HW busy timeout team: IO key: e2c455e0-1210-11ea-8389-b359bc6084c5 -status: New +status: Active upstream: @@ -9,3 +9,12 @@ comments: - "currently we use a tasklet to detect busy timeouts" - "MMC maintainer says this is OKish, but HW timeout would be much better" - "this is all for supporting MMC_CAP_ERASE properly" + - "MMC_CAP_ERASE has been removed meanwhile, and we set max_busy_timeout, too" + - "we still should care about handling when data timeouts happen" + - "RFT v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=388391&state=*" + - "RFT v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=388435&state=*" + - "needs some refactoring" + - "refactored v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=391145&state=*" + - "refactored series with max_busy_timeout merged" + - "prototype patches for handling data timeout developed by Shimoda-san and reviewed by Wolfram" + - "WAIT_WHILE_BUSY needs to be enabled on top of 'data timeout' patches" diff --git a/projects/linux/io/SDHI-non_removable_fix.yaml b/projects/linux/io/SDHI-non_removable_fix.yaml index 195f621..3f99fb7 100644 --- a/projects/linux/io/SDHI-non_removable_fix.yaml +++ b/projects/linux/io/SDHI-non_removable_fix.yaml @@ -2,10 +2,9 @@ title: SDHI; remove workaround to enable 'non-removable' property team: IO key: 5799545f-2472-4332-aba9-f0909e1d2154 assignee: Wolfram -status: Blocked +status: Paused relationships: - - depends: d8082b1e-0535-11ea-b216-574c9e1142f4 upstream: - torvalds: 8861474a105c91e812d38cd65d3be795c7f32c4f # Revert "mmc: tmio: move runtime PM enablement to the driver implementations" @@ -23,3 +22,4 @@ comments: - "workaround removal patch: https://patchwork.kernel.org/patch/11149285/" - "regression was discovered, reopening" - "first investigations showed stalled SCC, so blocking on the SCC clock handling task" + - "after some more RPM updates, Wolfram now gets an OOPS and not a stalled SCC; removing dependency, continuing investigation" diff --git a/projects/linux/io/SDHI-refactor-SDHn.yaml b/projects/linux/io/SDHI-refactor-SDHn.yaml new file mode 100644 index 0000000..ebffbf8 --- /dev/null +++ b/projects/linux/io/SDHI-refactor-SDHn.yaml @@ -0,0 +1,12 @@ +title: "SDHI; refactor SDHn to be a seperate clock" +team: IO +key: 008d3362-4055-11eb-9620-cb34de96bb07 +status: New +assignee: Wolfram + +upstream: + +comments: + - "check mail thread 'SDnCKCR setting for HS200 #297087'" + - "BSP will use a workaround, but we should model SDHn as a seperate clock" + - "This allows us to handle proper frequency settings from the SDHI driver" diff --git a/projects/linux/io/SDHI-refactor-reset.yaml b/projects/linux/io/SDHI-refactor-reset.yaml new file mode 100644 index 0000000..1c19495 --- /dev/null +++ b/projects/linux/io/SDHI-refactor-reset.yaml @@ -0,0 +1,28 @@ +title: "SDHI; refactor reset into proper reset and hw_reset" +team: IO +key: b408bad6-edcd-11ea-942b-eb603d86bc58 +status: Active +assignee: Wolfram + +bsp-commits: + +upstream: + - torvalds: 6e7d4de10890545b00f7d7c33310f1555963d592 # mmc: renesas_sdhi: move wrong 'hw_reset' to 'reset' + - torvalds: 34e3211e5492756d4e59ef54f9ab1750ec7050ec # Revert "mmc: tmio: fix reset operation" + - torvalds: a8c83064e73382d6bb069bd51c56074d1e4f4eec # mmc: tmio: remove indirection of 'hw_reset' callback + - torvalds: 576146ea4ed986f44a4406ec32a5d3363216b3d2 # mmc: tmio: factor out common parts of the reset routine + - torvalds: 5b0739d76227fd5a3f02f014385bfa9c86e0404b # mmc: tmio: don't reset whole IP core when tuning fails + - torvalds: 510bfe58936f7d79d4c377bcc7425244d879b1ff # mmc: tmio: remove indirection of 'execute_tuning' callback + +comments: + - "Shimoda-san reported that after IP core reset, some card initialization needs to be done again" + - "Wolfram then evaluated that the usage of reset and hw_reset in the SDHI driver is different from what the MMC core expects" + - "a proper refactoring was needed" + - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=335877&state=*" + - "v1 merged" + - "regression when re-inserting SD cards found, investigating" + - "also, we should probably reset the device in probe()" + - "BSP team suggests to use SRCR3 register SD-IFx bit" + - "regressions fixed: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=378775&state=*" + - "a better fix for the regression: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20201125204953.3344-1-wsa+renesas@sang-engineering.com/" + - "prototype for reset via SRCR3 sent internally; unusual delay needed, asking HW team for confirmation" diff --git a/projects/linux/io/SDHI-upport-pre-post-req.yaml b/projects/linux/io/SDHI-upport-pre-post-req.yaml new file mode 100644 index 0000000..332ea5a --- /dev/null +++ b/projects/linux/io/SDHI-upport-pre-post-req.yaml @@ -0,0 +1,15 @@ +title: "SDHI; upport pre-/post-req support from BSP for better performance" +team: IO +key: 00bf69ae-4055-11eb-af7f-9b89cbb89d45 +status: Active +assignee: Shimoda + +bsp-commits: + - bc6ecd4154b765cf565b96a6c970ba64f46e05c0 # mmc: tmio: Add support for pre_req and post_req + - 20998a8ef0cfd25e1f8f20fbbe10e3ef51e060c7 # mmc: renesas_sdhi: Add support for pre_req and post_req + +upstream: + +comments: + - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/patch/1607087853-6570-1-git-send-email-yoshihiro.shimoda.uh@renesas.com/" + - "v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=402809&state=*" diff --git a/projects/linux/io/WDT-handover_from_bootloader.yaml b/projects/linux/io/WDT-handover_from_bootloader.yaml deleted file mode 100644 index 6a947c3..0000000 --- a/projects/linux/io/WDT-handover_from_bootloader.yaml +++ /dev/null @@ -1,17 +0,0 @@ -title: Watchdog; implement handover from bootloader -team: IO -key: a0883915-709c-4116-afc3-2629f1b06a4f -assignee: Ulrich -status: Active - -upstream: - -comments: - - "RFC, needs discussion with Geert: https://patchwork.kernel.org/patch/10900571/" - - "v1 https://patchwork.kernel.org/patch/11099761/" - - "v2 https://patchwork.kernel.org/patch/11101573/" - - "v3 needed, bailing out and leave clock enabled is an open issue" - - "handed over task to Ulrich" - - "after discussion, we decided to ask watchdog-ml what to do when probing a wdt fails" - - "another approach to handle clocks during boot is using the 'ignore-unused' property" - - "ignore-unused v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=247897&state=*" diff --git a/projects/linux/io/bsp397_SDHI.yaml b/projects/linux/io/bsp397_SDHI.yaml deleted file mode 100644 index 557c33c..0000000 --- a/projects/linux/io/bsp397_SDHI.yaml +++ /dev/null @@ -1,50 +0,0 @@ -title: "From bsp397, upport SDHI patches" -team: IO -key: d8082b1e-0535-11ea-b216-574c9e1142f4 -status: New -assignee: Wolfram - -relationships: - -bsp-commits: - - 0c9dc7d65f8fb44dcbed1f52c303830f9b2d2a78 # mmc: renesas_sdhi: Change HS400 manual calibration method - - 7f2a7d6d94c7595d03488b99518d4cb0342d2cf9 # mmc: renesas_sdhi: Avoid bad TAP in HS400 - - f5a5c92906e113f712e584a5b7b9ff5911b78e40 # mmc: renesas_sdhi: Ignore DAT correction error status in manual correction - - 217814147a6220530ce02ec0d49137fa35d2c98c # mmc: renesas_sdhi: Use manual correction in HS400 - - bdd3c3b75cd6e5faa5bc92b890d8e4a5c5cca434 # mmc: renesas_sdhi: Add manual correction - - 8a21392f2c0472712c208ab3f526bc7ce2ea25ea # mmc: renesas_sdhi: Fix value of Hardware Adjustment Register in HS400 - - 8ce90dc51484a7d4f98c2a5f0aa4085e1e33fd85 # mmc: renesas_sdhi: Improved the data structure of quirks - - addfe9203290e3c274bca15e64e3f11638649e66 # mmc: renesas_sdhi: Fix hang up in HS400 timing mode selection - - a0f3de1e17422b135343788af49032e5e8264172 # mmc: renesas_sdhi: Add selecting optimum TAP when all of TAP is OK - -upstream: - - torvalds: 6e3cbb050b825e9003616ded9aa39957be20e77b # mmc: renesas_sdhi: keep sorting for quirk entries - - torvalds: e5088f20ed4057fd717449caadfd741dacb2cdc7 # mmc: renesas_sdhi: make warning more precise - - torvalds: 7af08206cb20308399f6ced08c52fb926624f24e # mmc: renesas_sdhi: make quirks info accessible outside probe() - - torvalds: 12e3c55d236b18fae00daa4ff54195b15cd741c3 # mmc: renesas_sdhi: remove 4taps as a TMIO flag - - torvalds: c1a49782cc32d720284d82742e8d9468c5ceb988 # mmc: renesas_sdhi: use recent tap values for HS400 - - next: 603a546a8c0b8c61cd28859b106f032b8524de4e # mmc: renesas_sdhi: remove double clear of automatic correction - - next: bb4f0504da6e0921e1e2dc10507842ae734d4e90 # mmc: renesas_sdhi: Add manual correction - - next: 839ada7649379933eb63fd93bcba51f31f937710 # mmc: renesas_sdhi: only check CMD status for HS400 manual correction - - next: 7f12135b2d68452d2c6072281faeeea55e6e521e # mmc: renesas_sdhi: enforce manual correction for Gen3 - - next: 968e94d11ba37371dc9760ce9fd10f294d22660a # mmc: renesas_sdhi: cleanup SCC defines - - next: 5cd51174617b7f0fca6569acaa34e152350551f5 # mmc: tmio: refactor tuning execution into SDHI driver - - next: 96f886e7aadbd73e235fcfff776454b5659d7335 # mmc: renesas_sdhi: complain loudly if driver needs update - - next: e89561948ec367d9ccf59a24553d9696f982692d # mmc: tmio: give callback a generic name - - next: 47ffea62ccfbaa54e4ba6e90a135de8fa8e845c9 # mmc: tmio: enforce retune after runtime suspend - - next: 3122c16609f3988c59f94ac011f3f5f29aba0b31 # mmc: tmio: factor out TAP usage - - next: 49dbebe26202847e0c7e0b3fc202ab8923a903aa # mmc: tmio: remove superfluous callback wrappers - -comments: - - "There is further work needed (some refactoring/squashing)" - - "8ce90dc51484a7d4f98c2a5f0aa4085e1e33fd85: Proposing 'N': BSP adapts here to what already exists in mainline" - - "8a21392f2c0472712c208ab3f526bc7ce2ea25ea: v1 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=211263&state=*" - - "8a21392f2c0472712c208ab3f526bc7ce2ea25ea: v1 series accepted" - - "bdd3c3b75cd6e5faa5bc92b890d8e4a5c5cca434, 217814147a6220530ce02ec0d49137fa35d2c98c: RFC v1 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=211277&state=*" - - "bdd3c3b75cd6e5faa5bc92b890d8e4a5c5cca434, 217814147a6220530ce02ec0d49137fa35d2c98c: RFC v2 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=218163&state=*" - - "f5a5c92906e113f712e584a5b7b9ff5911b78e40: depends on BSP patch a0f3de1e17422b135343788af49032e5e8264172 (mmc: renesas_sdhi: Add selecting optimum TAP when all of TAP is OK)" - - "f5a5c92906e113f712e584a5b7b9ff5911b78e40: we should also look before if moving SCC handling from TMIO to SDHI makes sense" - - "addfe9203290e3c274bca15e64e3f11638649e66: hang up hard to reproduce but this is needed for further investigations" - - "bdd3c3b75cd6e5faa5bc92b890d8e4a5c5cca434, 217814147a6220530ce02ec0d49137fa35d2c98c: merged" - - "move SCC handling into SDHI driver: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=234711&state=*" - - "above series merged" diff --git a/projects/linux/io/done/I2C-add-testunit.yaml b/projects/linux/io/done/I2C-add-testunit.yaml new file mode 100644 index 0000000..147b049 --- /dev/null +++ b/projects/linux/io/done/I2C-add-testunit.yaml @@ -0,0 +1,19 @@ +title: I2C; add a software testunit to test/implement additional features +team: IO +key: cbdfb88c-bc48-11ea-bc06-dfb1d88525f4 +assignee: Wolfram +status: Done + +upstream: + - torvalds: a8335c64c5f0916c9ee8b88835ce114085c3642e # i2c: add slave testunit driver + +comments: + - "preparational doc updates:" + - "https://patchwork.kernel.org/patch/11630291/" + - "https://patchwork.kernel.org/patch/11630293/" + - "https://patchwork.kernel.org/patch/11630295/" + - "actual implementation:" + - "RFC v1: https://patchwork.kernel.org/patch/11631987/" + - "v1 https://patchwork.kernel.org/patch/11769861/" + - "v2 https://patchwork.kernel.org/patch/11773045/" + - "merged" diff --git a/projects/linux/io/done/I2C-fix-slave-corner-cases.yaml b/projects/linux/io/done/I2C-fix-slave-corner-cases.yaml new file mode 100644 index 0000000..7b8ef13 --- /dev/null +++ b/projects/linux/io/done/I2C-fix-slave-corner-cases.yaml @@ -0,0 +1,33 @@ +title: I2C; fix issues when using the slave mode +team: IO +key: cd177762-bc48-11ea-af02-1fe19e7a99a4 +assignee: Wolfram +status: Done + +upstream: + - torvalds: 314139f9f0abdba61ed9a8463bbcb0bf900ac5a2 # i2c: rcar: slave: only send STOP event when we have been addressed + - torvalds: 914a7b3563b8fb92f976619bbd0fa3a4a708baae # i2c: rcar: in slave mode, clear NACK earlier + - torvalds: eb01597158ffb1853a7a7fc2c57d4c844640f75e # i2c: rcar: always clear ICSAR to avoid side effects + - torvalds: c7c9e914f9a0478fba4dc6f227cfd69cf84a4063 # i2c: rcar: avoid race when unregistering slave + +comments: + - "Issue 1: we should not monitor every STOP but only when we have been addressed" + - "v1 https://patchwork.kernel.org/patch/11632397/" + - "v2 https://patchwork.kernel.org/patch/11632107/" + - "v1 merged, v2 was not really better" + + - "Issue 2: how to properly handle the FNA bit" + - "working prototype exists, waiting for confirmation from the HW team" + - "HW team acknowledged the prototype" + - "v1 https://patchwork.kernel.org/patch/11718127/" + - "v1 merged" + + - "Issue 3: do we need to clear SAR when disabling the slave interface?" + - "working prototype exists, needs confirmation from the HW team" + - "only applies to Gen2, Gen3 is fine" + - "v1: https://patchwork.kernel.org/patch/11643625/" + - "v1 merged" + + - "Issue 4: race when unregistering slave" + - "v1: https://patchwork.kernel.org/patch/11685989/" + - "v1 merged" diff --git a/projects/linux/io/done/I2C-implement-HostNotify.yaml b/projects/linux/io/done/I2C-implement-HostNotify.yaml new file mode 100644 index 0000000..3e1a32f --- /dev/null +++ b/projects/linux/io/done/I2C-implement-HostNotify.yaml @@ -0,0 +1,24 @@ +title: I2C; implement SMBusHostNotify using the slave interface +team: IO +key: cd3f2a8c-bc48-11ea-9c13-3fd26b9b312b +assignee: Wolfram +status: Done + +upstream: + - torvalds: c4651f11d09ac975b6593653edbf74b892523a8f # i2c: rcar: add HostNotify support +comments: + - "core fix: https://patchwork.kernel.org/patch/11635635/" + - "generic binding proposal: https://patchwork.kernel.org/patch/11637351/" + - "waiting for the binding proposal to be accepted" + - "binding merged" + - "I2C core implementation (developed by ST.com, reviewed and merged by Wolfram):" + - "RFC v1: http://patchwork.ozlabs.org/project/linux-i2c/list/?series=174668&state=*" + - "RFC v2: http://patchwork.ozlabs.org/project/linux-i2c/list/?series=185718&state=*" + - "v1: http://patchwork.ozlabs.org/project/linux-i2c/list/?series=187213&state=*" + - "v2: http://patchwork.ozlabs.org/project/linux-i2c/list/?series=187405&state=*" + - "v3: http://patchwork.ozlabs.org/project/linux-i2c/list/?series=193772&state=*" + - "R-Car implementation:" + - "RFC: https://patchwork.kernel.org/patch/11635623/" + - "v1: https://patchwork.kernel.org/patch/11767165/" + - "merged" + diff --git a/projects/linux/io/I2C-new_device_conversion.yaml b/projects/linux/io/done/I2C-new_device_conversion.yaml index 4eda81c..318869c 100644 --- a/projects/linux/io/I2C-new_device_conversion.yaml +++ b/projects/linux/io/done/I2C-new_device_conversion.yaml @@ -2,7 +2,7 @@ title: I2C; convert i2c_new_device and friends to errno and managed devices and team: IO key: 6f15b8c0-7ff6-43aa-a47a-7341694c37af assignee: Wolfram -status: Active +status: Done upstream: - torvalds: 7159dbdae3c58d0200ae2550fab977a19a3c497a # i2c: core: improve return value handling of i2c_new_device and i2c_new_dummy @@ -46,7 +46,7 @@ comments: - "instead of listing patches and patch series, I will follow Morimoto-san's example how to describe big API changes" - "step 1: convert i2c_new_dummy() [done]" - "step 2: convert i2c_new_secondary_device() [done]" - - "step 3: convert i2c_new_probed_device() [core changes applied; driver patches sent, two left to be applied]" - - "step 4: convert i2c_new_device() [core changes applied, driver changes on-going, two batches sent out]" - - "step 5: convert i2c_setup_smbus_alert() [v2 sent out, seems ready to be merged]" - - "step 6: remove old API calls [steps 1-2 done, blocked by steps 3-5]" + - "step 3: convert i2c_new_probed_device() [done]" + - "step 4: convert i2c_new_device() [done]" + - "step 5: convert i2c_setup_smbus_alert() [done]" + - "step 6: remove old API calls [done]" diff --git a/projects/linux/io/done/IIC-add-atomic_xfer.yaml b/projects/linux/io/done/IIC-add-atomic_xfer.yaml new file mode 100644 index 0000000..54c91ec --- /dev/null +++ b/projects/linux/io/done/IIC-add-atomic_xfer.yaml @@ -0,0 +1,19 @@ +title: IIC; add atomic_xfer callbacks +team: IO +key: 591f9c90-70ad-11ea-9962-8faea49ce5f9 +assignee: Ulrich +status: Done + +upstream: + - torvalds: a49cc1fe9d64a2dc4e19b599204f403e5d25f44b # i2c: sh_mobile: implement atomic transfers + +comments: + - "Ulrich prototypes the IIC driver first; can refactor non-atomic xfer routine" + - "IIC v1: https://patchwork.kernel.org/patch/11598605/" + - "IIC v2: https://patchwork.kernel.org/patch/11612451/" + - "IIC prototype tested by Wolfram, works" + - "need to ensure how to keep PM domain active that late, trying the reboot notifier" + - "reboot notifier v1: https://patchwork.kernel.org/patch/11749121/" + - "IIC v3: https://patchwork.kernel.org/patch/11792759/" + - "IIC v4: https://patchwork.kernel.org/patch/11804027/" + - "IIC merged" diff --git a/projects/linux/io/PCI-OB-windows-RFC.yaml b/projects/linux/io/done/PCI-OB-windows-RFC.yaml index 114897d..89cd7f4 100644 --- a/projects/linux/io/PCI-OB-windows-RFC.yaml +++ b/projects/linux/io/done/PCI-OB-windows-RFC.yaml @@ -7,8 +7,9 @@ assignee: Marek relationships: upstream: + - torvalds: 2b9f217433e31d125fb697ca7974d3de3ecc3e92 # PCI: rcar: Fix incorrect programming of OB windows comments: - "RFC: https://patchwork.kernel.org/patch/11174493/" - "reviewed and tested by Marek, awaiting upstream" - + - "finally merged" diff --git a/projects/linux/io/done/PCI-review-endpoint-support.yaml b/projects/linux/io/done/PCI-review-endpoint-support.yaml new file mode 100644 index 0000000..612f6ab --- /dev/null +++ b/projects/linux/io/done/PCI-review-endpoint-support.yaml @@ -0,0 +1,28 @@ +title: "Review patch series for PCI endpoint support" +team: IO +key: 312f9fca-3325-11ea-8113-002170711890 +status: Done +assignee: Shimoda + +relationships: + +upstream: + +comments: + - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=199045&state=*" + - "v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=216247&state=*" + - "v3: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=225521&state=*" + - "v4: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=238723&state=*" + - "v5: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=249127&state=*" + - "Shimoda-san reviewed v5" + - "v6: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=265553&state=*" + - "Shimoda-san reviewed v6" + - "v7: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=268131&state=*" + - "Shimoda-san reviewed v7" + - "v8: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=273593&state=*" + - "Shimoda-san reviewed v8" + - "v9: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=276295&state=*" + - "Shimoda-san reviewed v9" + - "v10: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=283863&state=*" + - "Shimoda-san reviewed v10" + - "appeared upstream in the v5.8 merge window, marking done" diff --git a/projects/linux/io/done/SDHI-manual-calibration.yaml b/projects/linux/io/done/SDHI-manual-calibration.yaml new file mode 100644 index 0000000..95405e1 --- /dev/null +++ b/projects/linux/io/done/SDHI-manual-calibration.yaml @@ -0,0 +1,33 @@ +title: "SDHI; add manual calibration" +team: IO +key: d50ff876-95e8-11ea-9862-cb3c9259ec31 +status: Done +assignee: Wolfram + +relationships: + - depends: d593a7de-95e8-11ea-8695-9f6a675410b7 + +bsp-commits: + - a27609e63e9c4915706022b367d1d005833fe547 # mmc: tmio: Add adjust HS400 offset by manual calibration mode + - 1f84d574931b1319ebc1229678816338578f2d1e # mmc: renesas_sdhi_core: Add adjust HS400 offset by manual calibration mode + - b2e044a3602f7f9ffe6c61b6655e6b0b283d85c4 # mmc: renesas_sdhi: Change HS400 manual calibration value for r8a77990 + - 0c9dc7d65f8fb44dcbed1f52c303830f9b2d2a78 # mmc: renesas_sdhi: Change HS400 manual calibration method + - d01f6ab4bac4ff7f7ec152e0652beccfc0533d83 # Revert "mmc: renesas_sdhi: Change HS400 manual calibration method" + - 5e1187e7ad6af53a9081fa03578d5f18730cb6c1 # mmc: renesas_sdhi: Change HS400 manual calibration method + +upstream: + - torvalds: 354f47b699ae209606dcd0b05200cd7f17059e38 # mmc: tmio: add generic hook to fixup after a completed request + - torvalds: ce6f92c2801e90650106b00666aa37560978e324 # mmc: renesas_sdhi: support manual calibration + +comments: + - "a27609e63e9c4915706022b367d1d005833fe547, 1f84d574931b1319ebc1229678816338578f2d1e, b2e044a3602f7f9ffe6c61b6655e6b0b283d85c4: rfc v1 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=139709&state=*" + - "a27609e63e9c4915706022b367d1d005833fe547, 1f84d574931b1319ebc1229678816338578f2d1e, b2e044a3602f7f9ffe6c61b6655e6b0b283d85c4: rfc v2 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=140049&state=*" + - "5e1187e7ad6af53a9081fa03578d5f18730cb6c1: we are missing new info from HW team, waiting" + - "we got the new information" + - "new RFC patchset: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=298229&state=*" + - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=298683&state=*" + - "depends on the stalled SCC issue being fixed" + - "SCC issues was fixed" + - "Testing by Shimoda-san revealed an issue" + - "v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=342057&state=*" + - "v2 merged" diff --git a/projects/linux/io/done/SDHI-set-max_busy_timeout.yaml b/projects/linux/io/done/SDHI-set-max_busy_timeout.yaml new file mode 100644 index 0000000..a6a3f90 --- /dev/null +++ b/projects/linux/io/done/SDHI-set-max_busy_timeout.yaml @@ -0,0 +1,16 @@ +title: SDHI; set proper max_busy_timeout value +team: IO +key: 2bf4b23a-03da-11eb-b1a4-33206c8185b4 +status: Done + +upstream: + - next: 30ae3e13caeaa47884c222ebf5711ce27ed25f19 # mmc: tmio: set max_busy_timeout + - next: 58959f89dd3d8cc8bedcd2d665496603098b29a2 # mmc: tmio: add hook for custom busy_wait calculation + - next: b191deced78a12e26a827db03745b0da6cbc4f0e # mmc: renesas_sdhi: populate hook for longer busy_wait + +comments: + - "check 'SDHI: Should set max_busy_timeout value for erase command' on periperi list" + - "RFT v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=388391&state=*" + - "RFT v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=388435&state=*" + - "regrouped v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=391145&state=*" + - "merged" diff --git a/projects/linux/io/done/SDHI-stalled-SCC.yaml b/projects/linux/io/done/SDHI-stalled-SCC.yaml new file mode 100644 index 0000000..a66077b --- /dev/null +++ b/projects/linux/io/done/SDHI-stalled-SCC.yaml @@ -0,0 +1,29 @@ +title: "SDHI; SCC may stall if SDnH is not provided" +team: IO +key: d593a7de-95e8-11ea-8695-9f6a675410b7 +status: Done +assignee: Wolfram + +relationships: + +bsp-commits: + - addfe9203290e3c274bca15e64e3f11638649e66 # mmc: renesas_sdhi: Fix hang up in HS400 timing mode selection + +upstream: + - torvalds: 24fdcb377892b44dfe9755a62e4b92e9c6a0b359 # mmc: core: when downgrading HS400, callback into drivers earlier + - torvalds: 97a7d87e96b02fc5b3944d7735e0f6b8446d07da # mmc: core: add a 'doing_init_tune' flag and a 'mmc_doing_tune' helper + - torvalds: 0f93db6542fa94262b611ff942b9b3ad7ecbea10 # mmc: renesas_sdhi: keep SCC clock active when tuning + +comments: + - "hang up is surprisingly hard to reproduce but we keep trying" + - "updated manual calibration patchset makes the issue appear again" + - "v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=298209&state=*" + - "not all error paths covered; we need a new flag in the MMC core. Wolfram will work on it" + - "delayed because of generic Gen3 board boot problems" + - "patches for MMC core updates exists. However, currently not possible to trigger the issue again" + - "issue could be triggered again once" + - "patch to inject the fault for stalled SCC was created" + - "MMC core updates could be tested and worked" + - "v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=341697&state=*" + - "v2 tested and reviewed by Shimoda-san" + - "v2 merged" diff --git a/projects/linux/io/done/WDT-handover_from_bootloader.yaml b/projects/linux/io/done/WDT-handover_from_bootloader.yaml new file mode 100644 index 0000000..9085cfa --- /dev/null +++ b/projects/linux/io/done/WDT-handover_from_bootloader.yaml @@ -0,0 +1,29 @@ +title: Watchdog; implement handover from bootloader +team: IO +key: a0883915-709c-4116-afc3-2629f1b06a4f +assignee: Ulrich, Wolfram +status: Done + +upstream: + - torvalds: ed4a11807d2a35ccfc0d00371f20b826f670b5f2 # clk: renesas: cpg-mssr: Mark clocks as critical only if on at boot + - torvalds: f23f1101ad0ef1acdc219d3364522166e2c711ce # clk: renesas: rcar-gen3: Mark RWDT clocks as critical + - torvalds: 52bc5ea6edde35bc65ed6ecd7639534e78002c74 # clk: renesas: rzg2: Mark RWDT clocks as critical + - torvalds: 962085a2bb823d8c88c6bc706c654648407e6408 # watchdog: renesas_wdt: support handover from bootloader + +comments: + - "RFC, needs discussion with Geert: https://patchwork.kernel.org/patch/10900571/" + - "v1 https://patchwork.kernel.org/patch/11099761/" + - "v2 https://patchwork.kernel.org/patch/11101573/" + - "v3 needed, bailing out and leave clock enabled is an open issue" + - "handed over task to Ulrich" + - "after discussion, we decided to ask watchdog-ml what to do when probing a wdt fails" + - "another approach to handle clocks during boot is using the 'ignore-unused' property" + - "ignore-unused v1: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=247897&state=*" + - "ignore-unused v2: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=257141&state=*" + - "ignore-unused v3: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=285925&state=*" + - "Geert suggested to mark running WDT clocks as IS_CRITICAL during probe. Uli will implement this" + - "v4: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=303821&state=*" + - "merged" + - "WDT driver update still missing, Wolfram will resend" + - "resend: https://patchwork.kernel.org/patch/11763069/" + - "resend merged" diff --git a/projects/linux/io/bsp392_MSIOF.yaml b/projects/linux/io/done/bsp392_MSIOF.yaml index 3f859e6..66f7d73 100644 --- a/projects/linux/io/bsp392_MSIOF.yaml +++ b/projects/linux/io/done/bsp392_MSIOF.yaml @@ -1,7 +1,7 @@ title: "From bsp392, upport MSIOF patches" team: IO key: 1185bf87-d9d3-4cbf-a5fa-c46794018cba -status: Paused +status: Abandoned assignee: Geert relationships: @@ -19,3 +19,4 @@ comments: - "9312d43151d28307f527920dafbd7789eabdc63a: Proposing 'N': Should use ´assigned-clocks´ and ´assigned-clock-rates´ in board DTS file that actually uses MSIOF" - "a14d0903968f1524304f5b4de3da584778dbdfde: No access to H3 ES3.0 for testing" - "f925bf9ef632042ebb32e52108cc97305c15183d: Proposing 'N': not needed as the driver matches against ´renesas,rcar-gen3-msiof´" + - "No HW access to H3 ES3.0 for a long time now. Abandoning this patch. We will revive if we ever get this HW." diff --git a/projects/linux/io/done/bsp397_SDHI.yaml b/projects/linux/io/done/bsp397_SDHI.yaml new file mode 100644 index 0000000..7c04369 --- /dev/null +++ b/projects/linux/io/done/bsp397_SDHI.yaml @@ -0,0 +1,67 @@ +title: "From bsp397, upport SDHI patches" +team: IO +key: d8082b1e-0535-11ea-b216-574c9e1142f4 +status: Done +assignee: Wolfram + +relationships: + +bsp-commits: + - 0c9dc7d65f8fb44dcbed1f52c303830f9b2d2a78 # mmc: renesas_sdhi: Change HS400 manual calibration method + - 7f2a7d6d94c7595d03488b99518d4cb0342d2cf9 # mmc: renesas_sdhi: Avoid bad TAP in HS400 + - f5a5c92906e113f712e584a5b7b9ff5911b78e40 # mmc: renesas_sdhi: Ignore DAT correction error status in manual correction + - 217814147a6220530ce02ec0d49137fa35d2c98c # mmc: renesas_sdhi: Use manual correction in HS400 + - bdd3c3b75cd6e5faa5bc92b890d8e4a5c5cca434 # mmc: renesas_sdhi: Add manual correction + - 8a21392f2c0472712c208ab3f526bc7ce2ea25ea # mmc: renesas_sdhi: Fix value of Hardware Adjustment Register in HS400 + - 8ce90dc51484a7d4f98c2a5f0aa4085e1e33fd85 # mmc: renesas_sdhi: Improved the data structure of quirks + - addfe9203290e3c274bca15e64e3f11638649e66 # mmc: renesas_sdhi: Fix hang up in HS400 timing mode selection + - a0f3de1e17422b135343788af49032e5e8264172 # mmc: renesas_sdhi: Add selecting optimum TAP when all of TAP is OK + - ae58f551411e3e1d3dbc0e718f173f5100335eca # mmc: tmio: Add selecting optimum TAP when all of TAP is OK + +upstream: + - torvalds: 6e3cbb050b825e9003616ded9aa39957be20e77b # mmc: renesas_sdhi: keep sorting for quirk entries + - torvalds: e5088f20ed4057fd717449caadfd741dacb2cdc7 # mmc: renesas_sdhi: make warning more precise + - torvalds: 7af08206cb20308399f6ced08c52fb926624f24e # mmc: renesas_sdhi: make quirks info accessible outside probe() + - torvalds: 12e3c55d236b18fae00daa4ff54195b15cd741c3 # mmc: renesas_sdhi: remove 4taps as a TMIO flag + - torvalds: c1a49782cc32d720284d82742e8d9468c5ceb988 # mmc: renesas_sdhi: use recent tap values for HS400 + - torvalds: 44f54e701205d78e78bbac67d764a8833c2717c1 # mmc: renesas_sdhi: remove double clear of automatic correction + - torvalds: 11a219606a9bc7f1fcdb4fde285100fd8a601d0d # mmc: renesas_sdhi: Add manual correction + - torvalds: 71cfc92751ac7a3185e73cffc43a673b73c39683 # mmc: renesas_sdhi: only check CMD status for HS400 manual correction + - torvalds: 9b0d6855e756b60dd09c2a3d2a697130ffdc297d # mmc: renesas_sdhi: enforce manual correction for Gen3 + - torvalds: 6199a10e7e53d8185f25430fbae918d0f105a0ec # mmc: renesas_sdhi: cleanup SCC defines + - torvalds: 0c482d829ac413024b9ffa3b292ab8bd998eb62f # mmc: tmio: refactor tuning execution into SDHI driver + - torvalds: 3a821a8244bcdefb8d9242c49deb6a01fbf5039b # mmc: renesas_sdhi: complain loudly if driver needs update + - torvalds: 64982b9f2f37802b72430aed3796a89a01a088d1 # mmc: tmio: give callback a generic name + - torvalds: a86bf70b7021c93119f81454ad81293c526f3cb8 # mmc: tmio: enforce retune after runtime suspend + - torvalds: b2dd9a1325e680654cf5b7d8fc19000114bd145f # mmc: tmio: factor out TAP usage + - torvalds: f22084b662e5029f3ec31a9871d9c1c01aaa76de # mmc: tmio: remove superfluous callback wrappers + - torvalds: a5d90dc488e417c7f4a08e67936c25a199179cc4 # mmc: renesas_sdhi: simplify execute_tuning + - torvalds: 92fa2a567d520ed71bb810a3b24c6b60f8ef329c # mmc: renesas_sdhi: refactor calculation of best TAP + - torvalds: ec4fc1acf363985882c37278bfe8881c4e0ec121 # mmc: renesas_sdhi: clarify handling of selecting TAPs + - torvalds: 5fb6bf51f6d153c188087c7fef21f6a8cd481951 # mmc: renesas_sdhi: improve TAP selection if all TAPs are good + - torvalds: f583da4013a7e694fb0c3c5916537a72989e82a3 # mmc: renesas_sdhi: handle M3-W ES1.2 and 1.3 revisions + - torvalds: a38c078fea0b1393fd2acb50e91057d7e429d9aa # mmc: renesas_sdhi: Avoid bad TAP in HS400 + +comments: + - "There is further work needed (some refactoring/squashing)" + - "8ce90dc51484a7d4f98c2a5f0aa4085e1e33fd85: Proposing 'N': BSP adapts here to what already exists in mainline" + - "8a21392f2c0472712c208ab3f526bc7ce2ea25ea: v1 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=211263&state=*" + - "8a21392f2c0472712c208ab3f526bc7ce2ea25ea: v1 series accepted" + - "bdd3c3b75cd6e5faa5bc92b890d8e4a5c5cca434, 217814147a6220530ce02ec0d49137fa35d2c98c: RFC v1 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=211277&state=*" + - "bdd3c3b75cd6e5faa5bc92b890d8e4a5c5cca434, 217814147a6220530ce02ec0d49137fa35d2c98c, f5a5c92906e113f712e584a5b7b9ff5911b78e40: RFC v2 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=218163&state=*" + - "7f2a7d6d94c7595d03488b99518d4cb0342d2cf9: depends on BSP patch a0f3de1e17422b135343788af49032e5e8264172 (mmc: renesas_sdhi: Add selecting optimum TAP when all of TAP is OK)" + - "7f2a7d6d94c7595d03488b99518d4cb0342d2cf9: we should also look before if moving SCC handling from TMIO to SDHI makes sense" + - "addfe9203290e3c274bca15e64e3f11638649e66: hang up hard to reproduce but this is needed for further investigations" + - "bdd3c3b75cd6e5faa5bc92b890d8e4a5c5cca434, 217814147a6220530ce02ec0d49137fa35d2c98c, f5a5c92906e113f712e584a5b7b9ff5911b78e40: merged" + - "move SCC handling into SDHI driver: https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=234711&state=*" + - "above series merged" + - "a0f3de1e17422b135343788af49032e5e8264172, ae58f551411e3e1d3dbc0e718f173f5100335eca: v1 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=252313&state=*" + - "a0f3de1e17422b135343788af49032e5e8264172, ae58f551411e3e1d3dbc0e718f173f5100335eca: v2 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=267969&state=*" + - "above series merged" + - "7f2a7d6d94c7595d03488b99518d4cb0342d2cf9: v1 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=275439&state=*" + - "7f2a7d6d94c7595d03488b99518d4cb0342d2cf9: v2 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=276081&state=*" + - "7f2a7d6d94c7595d03488b99518d4cb0342d2cf9: v3 https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=276101&state=*" + - "7f2a7d6d94c7595d03488b99518d4cb0342d2cf9: v3 series accepted" + - "addfe9203290e3c274bca15e64e3f11638649e66: is more than upporting, moved to seperate task" + - "0c9dc7d65f8fb44dcbed1f52c303830f9b2d2a78: still missing new info from HW team, moved to seperate task" + - "closing this task" diff --git a/projects/linux/io/dt_bindings_json_schema_io.yaml b/projects/linux/io/dt_bindings_json_schema_io.yaml new file mode 100644 index 0000000..42278f9 --- /dev/null +++ b/projects/linux/io/dt_bindings_json_schema_io.yaml @@ -0,0 +1,50 @@ +title: "dt-bindings conversion to json-schema (I/O)" +team: IO +key: d7e7fc08-6e95-11ea-a34c-9f9195f9e9d0 +status: Active + +upstream: + - torvalds: 7f3bf4203774013bdb1648d7e2ce949e94564b07 # dt-bindings: at24: convert the binding document to yaml + - torvalds: 85d27be81e39323c8e3c1151e4858b26d7e1b20d # dt-bindings: hspi: Convert bindings to json-schema + - torvalds: 2a197ce6720a5431f3ffaa571ce108a5553a9bb3 # dt-bindings: pwm: renesas: pwm-rcar: convert bindings to json-schema + - torvalds: faf66c22e6470f5aa65e8c5643112a9db4c0f7c2 # dt-bindings: pwm: renesas: tpu: convert bindings to json-schema + - torvalds: 7ae8b2f5dfb357f0627aa5952c7d36cadafc408c # dt-bindings: rtc: rtc-sh: convert bindings to json-schema + - torvalds: df230079140f836aeaef640cd31e01e20f37e099 # dt-bindings: serial: Convert snps,dw-apb-uart to json-schema + - torvalds: 37a2fce0900119bd5e8b2989970578a34584da97 # dt-bindings: sh_eth convert bindings to json-schema + - torvalds: 9c3c41761f45216880c6a274da661797c06ebf76 # dt-bindings: spi: sh-msiof: Convert bindings to json-schema + - torvalds: 51d11d0a9ea46203241e25651af90ca4c5e2d71a # dt-bindings: usb: renesas: usb3-peri: convert bindings to json-schema + - torvalds: ec5f8dfd89d289361efa7348a778f888edc1feca # dt-bindings: usb: renesas_usbhs: convert bindings to json-schema + - torvalds: 8acbbddcf9913149ef47b20f487289da02c4a291 # dt-bindings: ata: rcar-sata: Convert to json-schema + - torvalds: 175a7427bb72050f2cc12664d62c8ed0f2b40a23 # dt-bindings: serial: Convert generic bindings to json-schema + - torvalds: 384d00fae8e51f8ff812937b2e654ba3da858227 # dt-bindings: serial: sh-sci: Convert to json-schema + - torvalds: 8f5a0a3750c171d1c717e54b017ecd84c555492d # dt-bindings: thermal: rcar-thermal: Convert bindings to json-schema + - torvalds: 999866c92f4a333cb776c3e87831feeddef74f96 # spi: dt-bindings: rspi: Convert to json-schema + - torvalds: 45037dd681577e876b6085bad1aa44415b0cbe93 # dt-bindings: phy: renesas: usb2-phy: convert bindings to json-schema + - torvalds: 007e358094bfb48f206c32b5c82777d980913d2f # dt-bindings: phy: renesas: usb3-phy: convert bindings to json-schema + - torvalds: 809eb4e9bf9d84eb5b703358afd0d564d514f6d2 # dt-bindings: timer: Add renesas,em-sti bindings + - torvalds: 038fb87fa3314e001de2dd4cf20a74fa623ac7ad # dt-bindings: usb: renesas,usb-xhci: convert to YAML + - torvalds: a1c76734095344fdbe43cbfe4940020e13151679 # dt-bindings: mmc: renesas,sdhi: convert to YAML + - torvalds: 41a053886b059d60945d3575e2328ff661599a04 # dt-bindings: timer: renesas: cmt: Convert to json-schema + - torvalds: d0941cfb9fa8ac69a67f264f81e2ba8ecb1caa0d # dt-bindings: watchdog: renesas-wdt: Convert to json-schema + - torvalds: 8f18632153e7f55d0150baa66af7a990fa812348 # dt-bindings: timer: renesas: ostm: Convert to json-schema + - torvalds: 37d1e94692e06a35c53ff052e2d0983548ef0395 # dt-bindings: thermal: rcar-gen3-thermal: Convert bindings to json-schema + - torvalds: 4b74c424a1b1d272e8677f26aeb5d37924fe7384 # dt-bindings: serial: Add renesas,em-uart bindings + - torvalds: bc6b83d636eb8b0083a166a6be6bae89440393c6 # dt-bindings: timer: renesas: mtu2: Convert to json-schema + - torvalds: d7adf6331189cbe9d73729052a9ff14fed802667 # dt-bindings: net: renesas,etheravb: Convert to json-schema + - next: b3ad845d3241fdf039afeaad8af2192b1de2429d # dt-bindings: timer: renesas: tmu: Convert to json-schema + - next: 0d69ce3c2c63d4db06b369ef67cb6e73b06a8ad8 # dt-bindings: PCI: rcar-pci-host: Convert bindings to json-schema + - next: 8c41245872e206ec932c24d1fd63f8ff054e9855 # dt-bindings:iio:adc:renesas,rcar-gyroadc: txt to yaml conversion. + +comments: + - Documentation/devicetree/bindings/i2c/renesas,i2c.txt + - Documentation/devicetree/bindings/i2c/renesas,iic-emev2.txt + - Documentation/devicetree/bindings/i2c/renesas,iic.txt + - Documentation/devicetree/bindings/i2c/renesas,riic.txt + - Documentation/devicetree/bindings/mmc/renesas,mmcif.txt + - Documentation/devicetree/bindings/net/can/rcar_canfd.txt + - Documentation/devicetree/bindings/net/can/rcar_can.txt + - Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt + - Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt + - Documentation/devicetree/bindings/phy/rcar-gen3-phy-pcie.txt + - Documentation/devicetree/bindings/spi/renesas,rzn1-spi.txt + - Documentation/devicetree/bindings/timer/renesas,tpu.txt diff --git a/projects/linux/io/r8a77961_io.yaml b/projects/linux/io/r8a77961_io.yaml new file mode 100644 index 0000000..756bfe3 --- /dev/null +++ b/projects/linux/io/r8a77961_io.yaml @@ -0,0 +1,27 @@ +title: "add r8a77961 support (I/O)" +team: IO +key: 5a349912-6ff1-11ea-aa8f-ab8daf9c94ea +status: Active + +upstream: + - torvalds: 8b183f5b85e0be4f94fa9309da5504bb7ba3367e # dt-bindings: i2c: rcar: Document r8a77961 support + - torvalds: 15c0677162b77636899ac668f3bc2055c941b9b7 # dt-bindings: i2c: sh_mobile: Document r8a77961 support + - torvalds: de27e978dc82ea22ef0f7999dfe870a087073907 # dt-bindings: mmc: renesas_sdhi: Document r8a77961 support + - torvalds: 5bfb26303663b022a7750fd9d80dc8bb8dc8b604 # dt-bindings: serial: sh-sci: Document r8a77961 bindings + - torvalds: e63318785234c9c33e97b7793e09a82c869e3ef0 # dt-bindings: net: ravb: Document r8a77961 support + - torvalds: 5bfb26303663b022a7750fd9d80dc8bb8dc8b604 # dt-bindings: serial: sh-sci: Document r8a77961 bindings + - torvalds: 26f1e12c714e9e7314e1a099fd8225473cb76ab8 # dt-bindings: watchdog: renesas-wdt: Document r8a77961 support + - torvalds: 07b053ff1c6ee7c972e7e3d0915d05f1b1280f14 # dt-bindings: pwm: rcar: add r8a77961 support + - torvalds: 68b1add4c51a96da21df1d1427a1b30614aeb9d9 # dt-bindings: usb: renesas,usb3-peri: add r8a77961 support + - torvalds: 0dc710353f630cace26db39d856800b17d3d2dda # dt-bindings: usb: renesas,usbhs: add r8a77961 support + - torvalds: 37db507496179fd43cf30b12aa56fe7df8d0ae73 # dt-bindings: usb: usb-xhci: add r8a77961 support + - torvalds: b24a0c16f738a68cd8c2997edf8ebe3d8951df93 # dt-bindings: pci: rcar: add r8a77961 support + - torvalds: 37d1e94692e06a35c53ff052e2d0983548ef0395 # dt-bindings: thermal: rcar-gen3-thermal: Convert bindings to json-schema + - torvalds: ca432812d9344a79f7c58375e07ad1936e9f0fc6 # dt-bindings: phy: renesas: usb2-phy: add r8a77961 support + - torvalds: 42aed917819d58bf202e7e2df7707fd5c2a4ef5c # dt-bindings: phy: renesas: usb3-phy: add r8a77961 support + - next: aef161f4f1b829e91c4aaaac75c2b8fcdbc033fc # spi: renesas,sh-msiof: Add r8a77961 support + - lore: https://lore.kernel.org/linux-renesas-soc/CAMuHMdVA0UCZi41JzKgqm7njr1fmSHa-2eA+ECd+AUM3K6Bhtg@mail.gmail.com/T/#m785cf17feb52ebd9f898d2d057453e4fdd249ffd + +comments: + - Documentation/devicetree/bindings/net/can/rcar_canfd.txt + - Documentation/devicetree/bindings/net/can/rcar_can.txt |