From: Keerthy <j-keerthy@ti.com>
To: Tony Lindgren <tony@atomide.com>, <linux-omap@vger.kernel.org>
Cc: Dave Gerlach <d-gerlach@ti.com>, Faiz Abbas <faiz_abbas@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nishanth Menon <nm@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Roger Quadros <rogerq@ti.com>, Suman Anna <s-anna@ti.com>,
Tero Kristo <t-kristo@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH 0/2] Two ti-sysc driver fixes for v5.3 merge window
Date: Thu, 2 May 2019 09:40:57 +0530 [thread overview]
Message-ID: <3cb61934-0add-38f5-dd37-6fc597e0ed6b@ti.com> (raw)
In-Reply-To: <20190501214129.12572-1-tony@atomide.com>
On 02/05/19 3:11 AM, Tony Lindgren wrote:
> Hi all,
>
> Here are few fixes for the am335x d_can boot issue Sebastian reported for
> Beaglebone.
Tested for AM437x-gp-evm RTC+DDR mode and DS0.
Also tried DS0 on Am335x beaglebone black.
For the above:
Tested-by: Keerthy <j-keerthy@ti.com>
>
> Regards,
>
> Tony
>
>
> Tony Lindgren (2):
> ARM: dts: Configure osc clock for d_can on am335x
> bus: ti-sysc: Handle devices with no control registers
>
> arch/arm/boot/dts/am33xx-l4.dtsi | 14 ++++++--------
> arch/arm/boot/dts/am437x-l4.dtsi | 4 ----
> drivers/bus/ti-sysc.c | 23 +++++++++++------------
> 3 files changed, 17 insertions(+), 24 deletions(-)
>
prev parent reply other threads:[~2019-05-02 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 21:41 Tony Lindgren
2019-05-01 21:41 ` [PATCH 1/2] ARM: dts: Configure osc clock for d_can on am335x Tony Lindgren
2019-05-01 21:41 ` [PATCH 2/2] bus: ti-sysc: Handle devices with no control registers Tony Lindgren
2019-05-02 4:10 ` Keerthy [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=3cb61934-0add-38f5-dd37-6fc597e0ed6b@ti.com \
--to=j-keerthy@ti.com \
--cc=bigeasy@linutronix.de \
--cc=d-gerlach@ti.com \
--cc=faiz_abbas@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=rogerq@ti.com \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®