[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210408023656.GM904837@yoga>
Date: Wed, 7 Apr 2021 21:36:56 -0500
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: skakit@...eaurora.org, Rob Herring <robh+dt@...nel.org>
Cc: Alessandro Zummo <a.zummo@...ertech.it>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Andy Gross <agross@...nel.org>,
Lee Jones <lee.jones@...aro.org>, linux-rtc@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, kgunda@...eaurora.org
Subject: Re: [PATCH 2/3] dt-bindings: mfd: Convert pm8xxx bindings to yaml
On Wed 07 Apr 10:37 CDT 2021, skakit@...eaurora.org wrote:
> Hi Bjorn,
>
> On 2021-03-11 22:33, Bjorn Andersson wrote:
> > On Thu 11 Mar 01:29 CST 2021, satya priya wrote:
[..]
> > > +patternProperties:
> > > + "rtc@[0-9a-f]+$":
> >
> > Can we somehow link this to individual binding docs instead of listing
> > all the possible functions here?
> >
>
> you mean we should split this into two:
> qcom-pm8xxx.yaml and qcom-pm8xxx-rtc.yaml
> Please correct me if wrong.
>
Right, I'm worried that it will be quite hard to maintain this document
once we start adding all the various pmic blocks to it. So if we somehow
can maintain a series of qcom-pm8xxx-<func>.yaml and just ref them into
the main PMIC definition.
@Rob, can you give us some guidance on how to structure this binding,
with the various PMICs described will have some defined subset of a
larger set of hardware blocks that's often shared between versions?
Regards,
Bjorn
Powered by blists - more mailing lists