diff options
| author | Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> | 2019-12-12 12:53:17 +0900 |
|---|---|---|
| committer | Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> | 2019-12-12 12:53:17 +0900 |
| commit | b0f66a9df80c5bfc05a69bfc48b39e98cb002886 (patch) | |
| tree | 827e9ac3ec900a0f1e8f171925eff288403cebea | |
| parent | d861c1c907b9d1c09f66e8bbab34c173771a9259 (diff) | |
wiki: 2016-10-miniperi: remove white space
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
| -rw-r--r-- | wiki/2016-10-miniperi.wiki | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/wiki/2016-10-miniperi.wiki b/wiki/2016-10-miniperi.wiki index 7d21563..6cd5bab 100644 --- a/wiki/2016-10-miniperi.wiki +++ b/wiki/2016-10-miniperi.wiki @@ -159,7 +159,7 @@ h2. renesas-drivers between v4.9-rc1 and v4.9 * Drop -next branches unless absolutely needed * Only include topic branches that will survive * Drop test and prototype code (e.g. SCIF/HSCIF external loopback) -* General: +* General: ** Be conservative! ** Update your topic branches when (some) commits have been accepted! * Risk: @@ -169,7 +169,7 @@ h2. renesas-drivers between v4.9-rc1 and v4.9 | v4.9 | renesas/topic/i2c_sdhi_maintenance | | v4.9 | renesas/topic/pretimeout | | v4.9 | [RFC] tty: serial_core: Move uart_console() check after console registration | -| v4.10 | clk-renesas-for-v4.10 | +| v4.10 | clk-renesas-for-v4.10 | | v4.10 | renesas/topic/sdhi-8bit-emmc | | v4.10 | sh-pfc-for-v4.10 | | v4.10 | topic/r8a7796-dmac-driver-v1-rebased1 | @@ -274,7 +274,7 @@ h3. What is the current status of "Cache management on V4L2":../../wiki/2016-10- ** BSP team want to use it Jan, 2017 v4.9 or July 2017 Final ** Backport is OK -The problem is well known but no mainline solution has been developed yet. +The problem is well known but no mainline solution has been developed yet. There is however interest in this topic from various companies. This can be handled as additional task(s), the schedule needs to be discussed. @@ -309,7 +309,7 @@ Work is in progress on a second one. Whether the issue found by the BSP team is h3. DU/VIN DT style difference ES1.x/ES2.0 ? -The DU and attached VSPs have changed significantly between ES1.x and ES2.0. +The DU and attached VSPs have changed significantly between ES1.x and ES2.0. This will require different compatible strings. The "renesas,vsps" property will still be used, referencing 3 VSPs instead of 4. There should be no other change needed to the DU DT bindings. For VIN, differences between ES versions are limited to CSI2 routing. This is hardcoded in the driver at the moment. As VIN has no IP core version register, routing selection has to be done through different compatible strings at the minimum. Another option would be to express full routing in DT, but that would be more complex and isn't considered as a good solution. |