[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=VoBLh+SFmo8NieRT6LrOopkKRE86xiEMt_ap2gyDZXWw@mail.gmail.com>
Date: Wed, 24 Oct 2018 13:36:49 -0700
From: Doug Anderson <dianders@...omium.org>
To: Vivek Gautam <vivek.gautam@...eaurora.org>
Cc: Evan Green <evgreen@...omium.org>, Rob Herring <robh@...nel.org>,
Andy Gross <andy.gross@...aro.org>,
Kishon Vijay Abraham I <kishon@...com>,
Stephen Boyd <swboyd@...omium.org>, cang@...eaurora.org,
LKML <linux-kernel@...r.kernel.org>,
Manu Gautam <mgautam@...eaurora.org>
Subject: Re: [PATCH v4 2/5] phy: qcom-qmp: Utilize fully-specified DT registers
Hi,
On Wed, Oct 24, 2018 at 11:29 AM Vivek Gautam
<vivek.gautam@...eaurora.org> wrote:
> Thanks for the patch.
> I am starting to think that the driver is heavily relying on the
> resource indices to request
> all these areas ioremapped. Is it a good way forward that driver and the
> dt bindings are
> chained together?
> Should we rather switch to requesting these resources by some names?
>
> Rob can comment on this possibly.
I thought about suggesting that but I know that Rob really doesn't
like accessing register ranges by name [1]. Even in cases where you
reference things by name Rob likes there to be a fully defined order
and once you have a fully defined order you don't really need the
names unless you have more than one optional register range.
In any case, Rob already gave his review to Evan's bindings change. See:
https://lore.kernel.org/r/20181023002903.GA16854@bogus
...so my vote would be to keep it as Evan's patch series has it and
not try to bikeshed it.
> Reviewed-by: Vivek Gautam <vivek.gautam@...eaurora.org>
Thanks for the review!
[1] https://lkml.kernel.org/r/CAL_Jsq+MMunmVWqeW9v2RyzsMKP+=kMzeTHNMG4JDHM7Fy0HBg@mail.gmail.com
-Doug
Powered by blists - more mailing lists