From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Vignesh R <vigneshr@ti.com>,
bcousson@baylibre.com, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, t-kristo@ti.com, jsarha@ti.com
Subject: Re: [PATCH] ARM: dts: am33xx-l4: Fix epwmssX/ecapX/ehrpwmX ranges and reg
Date: Tue, 11 Dec 2018 06:20:47 -0800 [thread overview]
Message-ID: <20181211142047.GN6707@atomide.com> (raw)
In-Reply-To: <dea21560-3e1f-5158-9fb0-3fedd0044a0a@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [181211 11:00]:
>
>
> On 11/12/2018 13.00, Vignesh R wrote:
> >
> >
> > On 11/12/18 4:24 PM, Peter Ujfalusi wrote:
> >> Correct the ranges for epwmsX nodes and the reg for the subnodes.
> >>
> >> Fixes: 87fc89ced3a78 ("ARM: dts: am335x: Move l4 child devices to probe them with ti-sysc")
> >>
> >> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> >> ---
> >> Hi Tony,
> >>
> >> with this patch am335x-evmsk LCD is working.
> >>
> >
> > I guess Tony has already posted a patch: https://patchwork.kernel.org/patch/10722671/
>
> Yep, I just noticed it, this can be ignored.
OK. In the long run we can just leave out the extra parent module
for epwmss as it just probes the children. But let's do that later
for v4.22 as clean-up, I did some initial patches for that yesterday.
Regards,
Tony
prev parent reply other threads:[~2018-12-11 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 10:54 [PATCH] ARM: dts: am33xx-l4: Fix epwmssX/ecapX/ehrpwmX ranges and reg Peter Ujfalusi
2018-12-11 11:00 ` Vignesh R
2018-12-11 11:01 ` Peter Ujfalusi
2018-12-11 14:20 ` Tony Lindgren [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=20181211142047.GN6707@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.com \
--cc=vigneshr@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).