linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Keerthy <j-keerthy@ti.com>
Cc: Suman Anna <s-anna@ti.com>, Vignesh R <vigneshr@ti.com>,
	Jyri Sarha <jsarha@ti.com>, "Andrew F. Davis" <afd@ti.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Franklin S Cooper Jr <fcooper@ti.com>,
	Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH 12/16] ARM: OMAP2+: Drop legacy platform data for am3 and am4 rtc
Date: Fri, 13 Dec 2019 06:59:26 -0800	[thread overview]
Message-ID: <20191213145926.GI35479@atomide.com> (raw)
In-Reply-To: <422c4d8d-27e3-7055-e8a4-c830a7e569be@ti.com>

* Keerthy <j-keerthy@ti.com> [191213 05:28]:
> On 11/12/19 10:50 pm, Tony Lindgren wrote:
> > We can now probe devices with ti-sysc interconnect driver and dts
> > data. Let's drop the related platform data and custom ti,hwmods
> > dts property.
> > 
> > As we're just dropping data, and the early platform data init
> > is based on the custom ti,hwmods property, we want to drop both
> > the platform data and ti,hwmods property in a single patch.
> > 
> > Note that we also must tag rtc as disabled on am43x-epos-evm as
> > it's not accessible according to commit 4321dc8dff35 ("ARM: AM43XX:
> > hwmod: Add rtc hwmod").
> 
> Both AM3 & AM4 are crashing while probing rtc. Due to rtc-clkctrl enable
> failure. So this breaks AM4/3.

Oh thanks for letting me know. I'll take a look.

Regards,

Tony



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-12-13 22:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 17:19 [PATCH 00/16] Drop legacy platform data for various omap devices Tony Lindgren
2019-12-11 17:19 ` [PATCH 01/16] ARM: OMAP2+: Drop legacy platform data for am3 and am4 epwmss Tony Lindgren
2019-12-11 17:20 ` [PATCH 02/16] ARM: OMAP2+: Drop legacy platform data for dra7 epwmss Tony Lindgren
2019-12-11 17:20 ` [PATCH 03/16] ARM: OMAP2+: Drop legacy platform data for am3 and am4 spinlock Tony Lindgren
2019-12-11 17:20 ` [PATCH 04/16] ARM: OMAP2+: Drop legacy platform data for omap4 spinlock Tony Lindgren
2019-12-11 17:20 ` [PATCH 05/16] ARM: OMAP2+: Drop legacy platform data for omap5 spinlock Tony Lindgren
2019-12-11 17:20 ` [PATCH 06/16] ARM: OMAP2+: Drop legacy platform data for dra7 spinlock Tony Lindgren
2019-12-11 17:20 ` [PATCH 07/16] ARM: OMAP2+: Drop legacy platform data for am3 and am4 spi Tony Lindgren
2019-12-11 17:20 ` [PATCH 08/16] ARM: OMAP2+: Drop legacy platform data for am3 and am4 dcan Tony Lindgren
2019-12-11 17:20 ` [PATCH 09/16] ARM: OMAP2+: Drop legacy platform data for dra7 dcan Tony Lindgren
2019-12-11 17:20 ` [PATCH 10/16] ARM: OMAP2+: Drop legacy platform data for am3 adc_tsc Tony Lindgren
2019-12-11 17:20 ` [PATCH 11/16] ARM: OMAP2+: Drop legacy platform data for am4 adc_tsc Tony Lindgren
2019-12-11 17:20 ` [PATCH 12/16] ARM: OMAP2+: Drop legacy platform data for am3 and am4 rtc Tony Lindgren
2019-12-13  5:28   ` Keerthy
2019-12-13 14:59     ` Tony Lindgren [this message]
2019-12-11 17:20 ` [PATCH 13/16] ARM: OMAP2+: Drop legacy platform data for am3 and am4 elm Tony Lindgren
2019-12-11 17:20 ` [PATCH 14/16] ARM: OMAP2+: Drop legacy platform data for omap4 elm Tony Lindgren
2019-12-11 17:20 ` [PATCH 15/16] ARM: OMAP2+: Drop legacy platform data for dra7 elm Tony Lindgren
2019-12-11 17:20 ` [PATCH 16/16] ARM: OMAP2+: Drop legacy platform data for am3 lcdc Tony Lindgren
2019-12-13  6:10 ` [PATCH 00/16] Drop legacy platform data for various omap devices Keerthy

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=20191213145926.GI35479@atomide.com \
    --to=tony@atomide.com \
    --cc=afd@ti.com \
    --cc=fcooper@ti.com \
    --cc=j-keerthy@ti.com \
    --cc=jsarha@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rogerq@ti.com \
    --cc=s-anna@ti.com \
    --cc=tomi.valkeinen@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).