All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
	"Benoît Cousson" <bcousson@baylibre.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: Add missing ranges for dra7 mcasp l3 ports
Date: Wed, 12 Dec 2018 07:28:29 -0800	[thread overview]
Message-ID: <20181212152829.GF6707@atomide.com> (raw)
In-Reply-To: <d7382c9f-6da8-6c8f-b1c6-ba2a017245d4@ti.com>

* Peter Ujfalusi <peter.ujfalusi@ti.com> [181212 08:00]:
> 
> 
> On 08/12/2018 2.54, Tony Lindgren wrote:
> > We need to add mcasp l3 port ranges for mcasp to use a correct l3
> > data port address for dma. And we're also missing the optional clocks
> > that we have tagged with HWMOD_OPT_CLKS_NEEDED in omap_hwmod_7xx_data.c.
> > 
> > Note that for reading the module revision register HWMOD_OPT_CLKS_NEEDED
> > do not seem to be needed. So they could be probably directly managed
> > only by the mcasp driver, and then we could leave them out for the
> > interconnect target module.
> 
> Tested on dra7-evm and dra72-evm. Works nicely, thanks!
> 
> Tested-by: Peter Ujfalusi <peter.ujfalusi@ti.com>

OK good to hear and thanks for testing. I already pushed this one out
yesterday as I was able to test it myself on beagle-x15.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
	"Benoît Cousson" <bcousson@baylibre.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: Add missing ranges for dra7 mcasp l3 ports
Date: Wed, 12 Dec 2018 07:28:29 -0800	[thread overview]
Message-ID: <20181212152829.GF6707@atomide.com> (raw)
In-Reply-To: <d7382c9f-6da8-6c8f-b1c6-ba2a017245d4@ti.com>

* Peter Ujfalusi <peter.ujfalusi@ti.com> [181212 08:00]:
> 
> 
> On 08/12/2018 2.54, Tony Lindgren wrote:
> > We need to add mcasp l3 port ranges for mcasp to use a correct l3
> > data port address for dma. And we're also missing the optional clocks
> > that we have tagged with HWMOD_OPT_CLKS_NEEDED in omap_hwmod_7xx_data.c.
> > 
> > Note that for reading the module revision register HWMOD_OPT_CLKS_NEEDED
> > do not seem to be needed. So they could be probably directly managed
> > only by the mcasp driver, and then we could leave them out for the
> > interconnect target module.
> 
> Tested on dra7-evm and dra72-evm. Works nicely, thanks!
> 
> Tested-by: Peter Ujfalusi <peter.ujfalusi@ti.com>

OK good to hear and thanks for testing. I already pushed this one out
yesterday as I was able to test it myself on beagle-x15.

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:[~2018-12-12 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08  0:54 [PATCH] ARM: dts: Add missing ranges for dra7 mcasp l3 ports Tony Lindgren
2018-12-08  0:54 ` Tony Lindgren
2018-12-12  8:01 ` Peter Ujfalusi
2018-12-12  8:01   ` Peter Ujfalusi
2018-12-12 15:28   ` Tony Lindgren [this message]
2018-12-12 15:28     ` Tony Lindgren

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=20181212152829.GF6707@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@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.