Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Magnus Damm <magnus.damm@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Simon Horman <horms+renesas@verge.net.au>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Konstantin Kozhevnikov 
	<Konstantin.Kozhevnikov@cogentembedded.com>
Subject: Re: [PATCH/RFC 00/02] Remove undocumented IMR-LX4 device nodes
Date: Wed, 23 Jan 2019 21:19:59 +0300	[thread overview]
Message-ID: <d9f6abfa-e480-cd85-a1a4-0c2ad219200f@cogentembedded.com> (raw)
In-Reply-To: <CANqRtoTNk7MQuXmoEZ6aTbEbEEOg7t-B63USvjcxKs-7LWggSA@mail.gmail.com>

Hello!

On 01/21/2019 03:01 PM, Magnus Damm wrote:

>> On Mon, Jan 21, 2019 at 12:49 PM Magnus Damm <magnus.damm@gmail.com> wrote:
>>> 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.
>>
>> [PATCH v5] media: platform: Renesas IMR driver
>> https://lore.kernel.org/linux-renesas-soc/20170309200818.786255823@cogentembedded.com/
> 
> 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.

> Cheers,
> 
> / magnus

MBR, Sergei

  reply	other threads:[~2019-01-23 18:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 11:49 [PATCH/RFC 00/02] Remove undocumented IMR-LX4 device nodes Magnus Damm
2019-01-21 11:50 ` [PATCH/RFC 01/02] arm64: dts: renesas: r8a7795: Remove " Magnus Damm
2019-01-23  9:59   ` Simon Horman
2019-01-23 15:43     ` Sergei Shtylyov
2019-01-21 11:50 ` [PATCH/RFC 02/02] arm64: dts: renesas: r8a7796: " Magnus Damm
2019-01-21 11:52 ` [PATCH/RFC 00/02] Remove undocumented " Geert Uytterhoeven
2019-01-21 12:01   ` Magnus Damm
2019-01-23 18:19     ` Sergei Shtylyov [this message]
2019-01-28 12:58       ` Simon Horman
2019-03-25 11:03         ` Simon Horman
2019-03-25 15:53           ` Sergei Shtylyov
2019-03-27 12:11             ` Simon Horman
2019-03-27 12:15               ` Simon Horman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9f6abfa-e480-cd85-a1a4-0c2ad219200f@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=Konstantin.Kozhevnikov@cogentembedded.com \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox