From: Michael Walle <michael@walle.cc>
To: Shawn Guo <shawnguo@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Li Yang <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>, Biwen Li <biwen.li@nxp.com>
Subject: Re: [PATCH 2/2] Revert "arm64: dts: ls1028a: add flextimer based pwm nodes"
Date: Sat, 29 Jan 2022 11:12:22 +0100 [thread overview]
Message-ID: <3d1328729d93daa2e6a50a4d03ec5ef0@walle.cc> (raw)
In-Reply-To: <20220129054209.GO4686@dragon>
Am 2022-01-29 06:42, schrieb Shawn Guo:
> On Sat, Jan 15, 2022 at 10:09:07PM +0100, Michael Walle wrote:
>> The changes to the device tree look very wrong. There are now two
>> devices with the same base address: pwm0 and ftm_alarm0. Both are
>> using
>> the Flex Timer Module. It seems like this should either be one driver
>> or
>> and MFD driver. Either way, there should only be one node in the
>> device
>> tree. Revert the offending changes to avoid getting a broken device
>> tree
>> in circulation.
>
> Why not just fix the conflicting nodes?
And how would you fix it? There are two conflicting drivers. Like
I said, maybe it should be an MFD driver, see for example
Documentation/devicetree/bindings/mfd/atmel-flexcom.txt, which also
have a common block which you can switch between different modes. But
that would mean a lot of work which I don't think will happen until
the next merge window, let alone that this is not a bugfix.
Therefore, the only sensible thing is to revert the latest changes,
so that you don't have a broken device tree released with 5.17 and
work on a proper support for the next release.
And TBH, I'd expect that NXP will fix this.
-michael
next prev parent reply other threads:[~2022-01-29 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 21:09 [PATCH 1/2] Revert "arm64: dts: ls1028a-rdb: enable pwm0" Michael Walle
2022-01-15 21:09 ` [PATCH 2/2] Revert "arm64: dts: ls1028a: add flextimer based pwm nodes" Michael Walle
2022-01-29 5:42 ` Shawn Guo
2022-01-29 10:12 ` Michael Walle [this message]
2022-02-07 14:02 ` Michael Walle
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=3d1328729d93daa2e6a50a4d03ec5ef0@walle.cc \
--to=michael@walle.cc \
--cc=biwen.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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
all inboxes | Powered by JetHome®