[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170817160537.GL8569@atomide.com>
Date: Thu, 17 Aug 2017 09:05:37 -0700
From: Tony Lindgren <tony@...mide.com>
To: Kishon Vijay Abraham I <kishon@...com>
Cc: Ulf Hansson <ulf.hansson@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>, nsekhar@...com,
linux-omap@...r.kernel.org, linux-mmc@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 5/7] dt-bindings: ti-omap-hsmmc: Document new
compatible for sdhci omap
* Kishon Vijay Abraham I <kishon@...com> [170816 22:44]:
> Hi Tony,
>
> On Thursday 10 August 2017 03:42 AM, Tony Lindgren wrote:
> > * Kishon Vijay Abraham I <kishon@...com> [170807 09:03]:
> >> Document the new compatible string "ti,dra7-sdhci" to be used for
> >> MMC controllers in DRA7 and DRA72 SoCs.
> >
> > I wonder if this should really be documented for sdhci
> > instead of ti-omap-hsmmc.txt?
>
> hmm.. yeah, having a separate binding document for sdhci would make the binding
> really clean and we also don't have to carry legacy binding code. But we'll be
> never able to remove omap-hsmmc driver then and end up maintaining 2 drivers
> for the same controller.
Well I think it's best to be able to enable sdhci one board at
a time after testing. Then eventually when fully supported, we
can just have sdhci also parse the legacy omap binding and just
drop the omap-hsmmc driver.
Regards,
Tony
Powered by blists - more mailing lists