All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: keerthy <j-keerthy@ti.com>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org, t-kristo@ti.com
Subject: Re: [PATCH 2/2] arm: dts: dra76-evm: Disable rtc target module
Date: Thu, 16 May 2019 09:58:24 -0700	[thread overview]
Message-ID: <20190516165824.GD5447@atomide.com> (raw)
In-Reply-To: <f2470149-0a17-cd1a-30d3-288fe2b821e3@ti.com>

* keerthy <j-keerthy@ti.com> [190516 16:54]:
> On 5/16/2019 10:17 PM, Tony Lindgren wrote:
> > But then any new board with dra76 or dra71 will need to debug
> > the same issue again. Sure we can get away for now tweaking the
> > board file, but to me it sounds like it's going to be more
> > devices that will be affected too?
> 
> Okay. This is a SoC related issue so yes any new board will have to again
> implement disabling.

OK

> > Is there some feature matrix available somewhere online?
> 
> Not that i know of. I will try finding something.

OK thanks.

> > How about add minimal dra76 and dra71 dtsi files in addition to
> > the board specific fix(es)? Then for v5.3, we can deal adding more
> > dra7 specifc evm files using these dtsi files or dynamically start
> > disabling modules.
> 
> You mean having a dra76/dra71.dtsi with rtc/usb4_tm disabled and that gets
> included in dra76/dra71-evm.dts?

Yeah, add dra76.dtsi and dra71.dtsi, then include those.

If however you have the same evm dts file with multiple SoC variants
available, then for now you need to also disable devices in the
evm dts. Or add another evm dts file.

Regards,

Tony

      reply	other threads:[~2019-05-16 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  9:06 [PATCH 1/2] arm: dts: dra76-evm: Disable usb4_tm target module Keerthy
2019-05-16  9:06 ` [PATCH 2/2] arm: dts: dra76-evm: Disable rtc " Keerthy
2019-05-16 16:12   ` Tony Lindgren
2019-05-16 16:31     ` keerthy
2019-05-16 16:47       ` Tony Lindgren
2019-05-16 16:54         ` keerthy
2019-05-16 16:58           ` 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=20190516165824.GD5447@atomide.com \
    --to=tony@atomide.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=t-kristo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.