From: Vinod Koul <vkoul@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [RFD]: Solving qcom unique unit address warnings
Date: Wed, 9 Feb 2022 11:13:49 +0530 [thread overview]
Message-ID: <YgNUlVjoXaNYyTM3@matsya> (raw)
In-Reply-To: <YgLNJPpyVgFYuB45@robh.at.kernel.org>
On 08-02-22, 14:05, Rob Herring wrote:
> On Fri, Jan 21, 2022 at 10:38:37PM +0530, Vinod Koul wrote:
> >
> >
> > The problem comes with all these nodes having same unit addresses. This
> > is adding to ~2K warning for unique_unit_address upstream.
>
> This is with W=1, right?
Yes
>
> > So to solve this we thought of creating a qup se node and then query the
> > protocol supported from the firmware on boot and create a child
> > auxillary_device. The problem with that approach is another warning
> > "node name for SPI buses should be 'spi'"! So that would not help
> >
> > Now, I cant think of any better idea here, except maybe move these to
> > respective board dts and perhaps keep them commented here for
> > documentation.
> >
> > Do we have any better idea to solve this problem?
>
> There is another dtc warning option called
> unique_unit_address_if_enabled which we could enable under W=1 instead
> of unique_unit_address. Even that option has too many warnings to enable
> by default.
Bjorn pointed me to your proposal https://www.irccloud.com/pastebin/OnYqVn6p/
with this change I do get a better stats for warnings which we can focus
on reducing :)
Before:
6483 unique_unit_address\n\
1108 simple_bus_reg\n\
764 avoid_unnecessary_addr_size\n\
712 unit_address_vs_reg\n\
120 graph_child_address\n\
32 unique_unit_address_if_enabled
After:
277 simple_bus_reg\n\
191 avoid_unnecessary_addr_size\n\
178 unit_address_vs_reg\n\
32 unique_unit_address_if_enabled\n\
30 graph_child_address
So, it would be helpful for now to merge this.
Thanks
--
~Vinod
prev parent reply other threads:[~2022-02-09 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 17:08 [RFD]: Solving qcom unique unit address warnings Vinod Koul
2022-02-01 4:44 ` Vinod Koul
2022-02-08 20:05 ` Rob Herring
2022-02-09 5:43 ` Vinod Koul [this message]
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=YgNUlVjoXaNYyTM3@matsya \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh@kernel.org \
/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