Skip to contentSkip to conversation

Remove undocumented IMR-LX4 device nodes

PATCH In review Magnus Damm 4 participants 13 messages Jan 21, 2019 – Mar 27, 2019

Subsystems (2)
lore
Share & tools
lore

Magnus Damm

author maintainer
#0 lore raw

cover Remove undocumented IMR-LX4 device nodes

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.

In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.

Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.

---

Developed on top of v5.0-rc3

 arch/arm64/boot/dts/renesas/r8a7795.dtsi |   40 ------------------------------
 arch/arm64/boot/dts/renesas/r8a7796.dtsi |   20 ---------------
 2 files changed, 60 deletions(-)
author maintainer
#1 lore raw

PATCH 1/2 arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes

From: Magnus Damm <[email protected]>

Get rid of undocumented IMR-LX4 device nodes for the r8a7795 SoC.

I would much prefer to have a proper driver with documented DT bindings in upstream instead. However removing DT nodes seems better than this current half-way state.

---

 arch/arm64/boot/dts/renesas/r8a7795.dtsi |   40 ------------------------------
 1 file changed, 40 deletions(-)
arch/arm64/boot/dts/renesas/r8a7795.dtsi +0 -40
@@ -2607,46 +2607,6 @@
 			status = "disabled";
 		};
 
-		imr-lx4@fe860000 {
-			compatible = "renesas,r8a7795-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe860000 0 0x2000>;
-			interrupts = <GIC_SPI 192 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 823>;
-			power-domains = <&sysc R8A7795_PD_A3VC>;
-			resets = <&cpg 823>;
-		};
-
-		imr-lx4@fe870000 {
-			compatible = "renesas,r8a7795-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe870000 0 0x2000>;
-			interrupts = <GIC_SPI 193 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 822>;
-			power-domains = <&sysc R8A7795_PD_A3VC>;
-			resets = <&cpg 822>;
-		};
-
-		imr-lx4@fe880000 {
-			compatible = "renesas,r8a7795-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe880000 0 0x2000>;
-			interrupts = <GIC_SPI 194 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 821>;
-			power-domains = <&sysc R8A7795_PD_A3VC>;
-			resets = <&cpg 821>;
-		};
-
-		imr-lx4@fe890000 {
-			compatible = "renesas,r8a7795-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe890000 0 0x2000>;
-			interrupts = <GIC_SPI 195 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 820>;
-			power-domains = <&sysc R8A7795_PD_A3VC>;
-			resets = <&cpg 820>;
-		};
-
 		fdp1@fe940000 {
 			compatible = "renesas,fdp1";
 			reg = <0 0xfe940000 0 0x2400>;
#2 lore raw

Re: [PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes

Quoted 9 lines · Magnus Damm

From: Magnus Damm <[email protected]>

Get rid of undocumented IMR-LX4 device nodes for the r8a7795 SoC.

I would much prefer to have a proper driver with documented DT bindings in upstream instead. However removing DT nodes seems better than this current half-way state.

I agree, likewise for patch 02/02.

Shall I go ahead and apply this series?

Quoted 55 lines

---

 arch/arm64/boot/dts/renesas/r8a7795.dtsi |   40 ------------------------------
 1 file changed, 40 deletions(-)
arch/arm64/boot/dts/renesas/r8a7795.dtsi +0 -40
@@ -2607,46 +2607,6 @@
 			status = "disabled";
 		};
 
-		imr-lx4@fe860000 {
-			compatible = "renesas,r8a7795-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe860000 0 0x2000>;
-			interrupts = <GIC_SPI 192 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 823>;
-			power-domains = <&sysc R8A7795_PD_A3VC>;
-			resets = <&cpg 823>;
-		};
-
-		imr-lx4@fe870000 {
-			compatible = "renesas,r8a7795-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe870000 0 0x2000>;
-			interrupts = <GIC_SPI 193 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 822>;
-			power-domains = <&sysc R8A7795_PD_A3VC>;
-			resets = <&cpg 822>;
-		};
-
-		imr-lx4@fe880000 {
-			compatible = "renesas,r8a7795-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe880000 0 0x2000>;
-			interrupts = <GIC_SPI 194 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 821>;
-			power-domains = <&sysc R8A7795_PD_A3VC>;
-			resets = <&cpg 821>;
-		};
-
-		imr-lx4@fe890000 {
-			compatible = "renesas,r8a7795-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe890000 0 0x2000>;
-			interrupts = <GIC_SPI 195 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 820>;
-			power-domains = <&sysc R8A7795_PD_A3VC>;
-			resets = <&cpg 820>;
-		};
-
 		fdp1@fe940000 {
 			compatible = "renesas,fdp1";
 			reg = <0 0xfe940000 0 0x2400>;
#3 lore raw

Re: [PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes

Quoted 8 lines · Simon Horman
Quoted 8 lines

From: Magnus Damm <[email protected]>

Get rid of undocumented IMR-LX4 device nodes for the r8a7795 SoC.

I would much prefer to have a proper driver with documented DT bindings in upstream instead. However removing DT nodes seems better than this current half-way state.

Quoted 5 lines
Quoted 1 line

I agree, likewise for patch 02/02.

Shall I go ahead and apply this series?

I will return to the IMR driver after I'm done with V3M/V3H (and I have the HyperFlash
driver to push upstream yet for those). Sorry for dropping the ball here, it wasn't my fault.

MBR, Sergei

author maintainer
#4 lore raw

PATCH 2/2 arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

In reply to Magnus Damm

From: Magnus Damm <[email protected]>

Get rid of undocumented IMR-LX4 device nodes for the r8a7796 SoC.

I would much prefer to have a proper driver with documented DT bindings in upstream instead. However removing DT nodes seems better than this current half-way state.

---

 arch/arm64/boot/dts/renesas/r8a7796.dtsi |   20 --------------------
 1 file changed, 20 deletions(-)
arch/arm64/boot/dts/renesas/r8a7796.dtsi +0 -20
@@ -2470,26 +2470,6 @@
 			status = "disabled";
 		};
 
-		imr-lx4@fe860000 {
-			compatible = "renesas,r8a7796-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe860000 0 0x2000>;
-			interrupts = <GIC_SPI 192 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 823>;
-			power-domains = <&sysc R8A7796_PD_A3VC>;
-			resets = <&cpg 823>;
-		};
-
-		imr-lx4@fe870000 {
-			compatible = "renesas,r8a7796-imr-lx4",
-				     "renesas,imr-lx4";
-			reg = <0 0xfe870000 0 0x2000>;
-			interrupts = <GIC_SPI 193 IRQ_TYPE_LEVEL_HIGH>;
-			clocks = <&cpg CPG_MOD 822>;
-			power-domains = <&sysc R8A7796_PD_A3VC>;
-			resets = <&cpg 822>;
-		};
-
 		fdp1@fe940000 {
 			compatible = "renesas,fdp1";
 			reg = <0 0xfe940000 0 0x2400>;
#5 lore raw
In reply to Magnus Damm

Hi Magnus,

Quoted 12 lines · Magnus Damm

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.

Quoted 8 lines

In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.

Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.

[PATCH v5] media: platform: Renesas IMR driver
https://lore.kernel.org/linux-renesas-soc/[email protected]/

Gr{oetje,eeting}s,

Geert

Signature · 5 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In 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
author maintainer
#6 lore raw

Hi Geert,

Quoted 19 lines · Geert Uytterhoeven

Hi Magnus,

Quoted 15 lines · Magnus Damm

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.

In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.

Quoted 8 lines
Quoted 5 lines

Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.

[PATCH v5] media: platform: Renesas IMR driver
https://lore.kernel.org/linux-renesas-soc/[email protected]/

Thanks, but that seems to be from 2017! =)

Cheers,

/ magnus

#7 lore raw

Hello!

Quoted 22 lines · Magnus Damm
Quoted 22 lines · Magnus Damm
Quoted 20 lines

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.

In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.

Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.

Quoted 4 lines
Quoted 2 lines

[PATCH v5] media: platform: Renesas IMR driver
https://lore.kernel.org/linux-renesas-soc/[email protected]/

Thanks, but that seems to be from 2017! =)

I dropped the ball there, as I was tasked with upstreaming V3x support...
The last thing done about the IMR driver was talking to Hans in Prague in 2017. I'm planning to return to the driver after I'm done with the HyperFlash driver.

Quoted 3 lines

Cheers,

/ magnus

MBR, Sergei

#8 lore raw
Quoted 29 lines · Sergei Shtylyov

Hello!

Quoted 25 lines · Magnus Damm
Quoted 24 lines · Magnus Damm
Quoted 12 lines

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.

Quoted 8 lines

In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.

Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.

[PATCH v5] media: platform: Renesas IMR driver
https://lore.kernel.org/linux-renesas-soc/[email protected]/

Quoted 6 lines
Quoted 1 line

Thanks, but that seems to be from 2017! =)

I dropped the ball there, as I was tasked with upstreaming V3x support...
The last thing done about the IMR driver was talking to Hans in Prague in 2017. I'm planning to return to the driver after I'm done with the HyperFlash driver.

Hi Sergei,

I appreciate that we are not always in control of our own priorities, indeed I sympathise with that predicament. However, we shouldn't really be in a situation where DT is making use of undocumented bindings.

I would like to ask for the bindings to be documented in the upstream kernel in the near future. And if that is not possible I believe we should consider temporarily removing their use in DT in the upstream kernel.

#9 lore raw
Quoted 39 lines · Simon Horman
Quoted 29 lines · Sergei Shtylyov

Hello!

Quoted 25 lines · Magnus Damm
Quoted 24 lines · Magnus Damm
Quoted 12 lines

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.

Quoted 8 lines

In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.

Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.

[PATCH v5] media: platform: Renesas IMR driver
https://lore.kernel.org/linux-renesas-soc/[email protected]/

Quoted 6 lines
Quoted 1 line

Thanks, but that seems to be from 2017! =)

I dropped the ball there, as I was tasked with upstreaming V3x support...
The last thing done about the IMR driver was talking to Hans in Prague in 2017. I'm planning to return to the driver after I'm done with the HyperFlash driver.

Hi Sergei,

Quoted 7 lines

I appreciate that we are not always in control of our own priorities, indeed I sympathise with that predicament. However, we shouldn't really be in a situation where DT is making use of undocumented bindings.

I would like to ask for the bindings to be documented in the upstream kernel in the near future. And if that is not possible I believe we should consider temporarily removing their use in DT in the upstream kernel.

Hi Sergei,

about two months have passed since Magnus posted this series. Do you have a timeline to address the problems? If so I believe that the way forward should be to apply this series. The topic can always be readdressed in future.

#10 lore raw

Hello!

Quoted 38 lines · Simon Horman
Quoted 38 lines
Quoted 25 lines
Quoted 25 lines
Quoted 24 lines · Magnus Damm
Quoted 12 lines

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.

Quoted 8 lines

In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.

Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.

[PATCH v5] media: platform: Renesas IMR driver
https://lore.kernel.org/linux-renesas-soc/[email protected]/

Quoted 6 lines
Quoted 1 line

Thanks, but that seems to be from 2017! =)

I dropped the ball there, as I was tasked with upstreaming V3x support...
The last thing done about the IMR driver was talking to Hans in Prague in 2017. I'm planning to return to the driver after I'm done with the HyperFlash driver.

Hi Sergei,

I appreciate that we are not always in control of our own priorities, indeed I sympathise with that predicament. However, we shouldn't really be in a situation where DT is making use of undocumented bindings.

Quoted 7 lines
Quoted 3 lines

I would like to ask for the bindings to be documented in the upstream kernel in the near future. And if that is not possible I believe we should consider temporarily removing their use in DT in the upstream kernel.

Hi Sergei,

about two months have passed since Magnus posted this series.

Time flies...
Dealing w/ the flash drivers turned into unending nightmare. :-(

Quoted 1 line

Do you have a timeline to address the problems?

I'm looking into posting the bindings separately right now.
The patch should be ready today or tomorrow.

Quoted 1 line

If so I believe> that the way forward should be to apply this series.

Hm, not sure I understood you correctly. You're going to remove
the device nodes even if I have a timeline?

[...]

MBR, Sergei

#11 lore raw
Quoted 55 lines · Sergei Shtylyov

Hello!

Quoted 38 lines · Simon Horman
Quoted 38 lines
Quoted 25 lines
Quoted 25 lines
Quoted 24 lines · Magnus Damm
Quoted 12 lines

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.

Quoted 8 lines

In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.

Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.

[PATCH v5] media: platform: Renesas IMR driver
https://lore.kernel.org/linux-renesas-soc/[email protected]/

Quoted 6 lines
Quoted 1 line

Thanks, but that seems to be from 2017! =)

I dropped the ball there, as I was tasked with upstreaming V3x support...
The last thing done about the IMR driver was talking to Hans in Prague in 2017. I'm planning to return to the driver after I'm done with the HyperFlash driver.

Hi Sergei,

I appreciate that we are not always in control of our own priorities, indeed I sympathise with that predicament. However, we shouldn't really be in a situation where DT is making use of undocumented bindings.

Quoted 7 lines
Quoted 3 lines

I would like to ask for the bindings to be documented in the upstream kernel in the near future. And if that is not possible I believe we should consider temporarily removing their use in DT in the upstream kernel.

Hi Sergei,

about two months have passed since Magnus posted this series.

   Time flies...
   Dealing w/ the flash drivers turned into unending nightmare. :-(
Quoted 1 line

Do you have a timeline to address the problems?

Quoted 7 lines

I'm looking into posting the bindings separately right now.
The patch should be ready today or tomorrow.

Quoted 1 line

If so I believe> that the way forward should be to apply this series.

Hm, not sure I understood you correctly. You're going to remove
the device nodes even if I have a timeline?

Sorry, there was a typo in the above. Of course not.

#12 lore raw
Quoted 59 lines · Simon Horman
Quoted 58 lines · Sergei Shtylyov

Hello!

Quoted 38 lines · Simon Horman
Quoted 38 lines
Quoted 25 lines
Quoted 25 lines
Quoted 24 lines · Magnus Damm
Quoted 12 lines

Remove undocumented IMR-LX4 device nodes

[PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove IMR-LX4 device nodes [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: Remove IMR-LX4 device nodes

These patches take the easy way out and simply remove the undocumented IMR-LX4 device nodes from the upstream tree. Good or bad, let me know!

So perhaps this is a bit overly aggressive but since the DT bindings seem undocumented and no driver exists in upstream my gut feeling says these DT nodes were part of an upstreaming attempt that got suspended half-way through.

Quoted 8 lines

In case DT binding documentation is in-flight and queued up somewhere (ideally together with a driver) then feel free to ignore this series.

Instead of removing nodes we could also document the DT bindings for the IMR-LX4 devices. It would also make sense to add device nodes to other more recent SoCs than just H3 and M3-W. But blindly adding more DT nodes with a DT binding but without a driver seems a bit suboptimal compared to testing against an actual driver.

[PATCH v5] media: platform: Renesas IMR driver
https://lore.kernel.org/linux-renesas-soc/[email protected]/

Quoted 6 lines
Quoted 1 line

Thanks, but that seems to be from 2017! =)

I dropped the ball there, as I was tasked with upstreaming V3x support...
The last thing done about the IMR driver was talking to Hans in Prague in 2017. I'm planning to return to the driver after I'm done with the HyperFlash driver.

Hi Sergei,

I appreciate that we are not always in control of our own priorities, indeed I sympathise with that predicament. However, we shouldn't really be in a situation where DT is making use of undocumented bindings.

Quoted 7 lines
Quoted 3 lines

I would like to ask for the bindings to be documented in the upstream kernel in the near future. And if that is not possible I believe we should consider temporarily removing their use in DT in the upstream kernel.

Hi Sergei,

about two months have passed since Magnus posted this series.

   Time flies...
   Dealing w/ the flash drivers turned into unending nightmare. :-(
Quoted 1 line

Do you have a timeline to address the problems?

I'm looking into posting the bindings separately right now.
The patch should be ready today or tomorrow.

Quoted 6 lines
Quoted 4 lines
Quoted 1 line

If so I believe> that the way forward should be to apply this series.

Hm, not sure I understood you correctly. You're going to remove
the device nodes even if I have a timeline?

Sorry, there was a typo in the above. Of course not.

Also, I now see
"[PATCH v2] dt-bindings: media: Renesas R-Car IMR bindings".

Thanks for working on this.