[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5813f448-590c-0f6a-ec22-d2b5fa36cf03@gmail.com>
Date: Tue, 23 Apr 2019 21:27:19 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Lee Jones <lee.jones@...aro.org>, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Laxman Dewangan <ldewangan@...dia.com>,
Mallikarjun Kasoju <mkasoju@...dia.com>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>
Cc: devicetree@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 6/7] mfd: max77620: Support device-tree properly
22.04.2019 22:13, Dmitry Osipenko пишет:
> For some unknown reason the driver for Max77620 doesn't wire up the
> device-tree support properly and nothing in kernel creates I2C device
> for the driver (and never did), moreover device-tree files for NVIDIA
> Tegra210/186/194 boards already have nodes for Max77620. Hence add the
> missing of_match_table to make driver actually usable.
>
> Signed-off-by: Dmitry Osipenko <digetx@...il.com>
> ---
I found out that I2C core actually parses the compatible value of the device-tree node for the driver-device matching and hence it's enough to have the id_table solely. I'll drop this patch in v3.
Powered by blists - more mailing lists