From: b-cousson@ti.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] ARM: dts: Update OMAP5 with address space and interrupts
Date: Wed, 24 Oct 2012 11:15:02 +0200 [thread overview]
Message-ID: <5087B196.7090804@ti.com> (raw)
In-Reply-To: <1351062434-22514-1-git-send-email-s-guiriec@ti.com>
Hi Seb,
Sorry, I missed your previous email, your v2 was the right one.
We do have a single INTC in every OMAP, there is no point to repeat the
same data hundred times.
The DTS are already big enough.
On 10/24/2012 09:07 AM, Sebastien Guiriec wrote:
> Since kernel 3.7 the DTS data are not overwriten by hwmod data we can add the address space
> and interrupt line description inside dtsi file for OMAP5. This serie is updating the
> current OMAP5 IP with missing entry.
>
> It has been tested on OMAP5 with 3.7-audio-display feature tree.
> - MMC is probing and functional
> - TWL6041 probing (GPIO/I2C)
> - booting (UART)
>
> Update since v1:
> - Add Ack and review
> - Fix up commit messages.
>
> Update since v2:
> - Add interrupt-parent.
I will take the previous one to avoid the duplication of attributes.
On top of that I will remove the ones introduce in audio IPs for
consistency on OMAP3/4/5 platforms.
Regards,
Benoit
next prev parent reply other threads:[~2012-10-24 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 7:07 [PATCH v3 0/4] ARM: dts: Update OMAP5 with address space and interrupts Sebastien Guiriec
2012-10-24 7:07 ` [PATCH v3 1/4] ARM: dts: omap5: Update GPIO " Sebastien Guiriec
2012-10-24 7:07 ` [PATCH v3 2/4] ARM: dts: omap5: Update I2C " Sebastien Guiriec
2012-10-24 7:07 ` [PATCH v3 3/4] ARM: dts: omap5: Update UART " Sebastien Guiriec
2012-10-24 7:07 ` [PATCH v3 4/4] ARM: dts: omap5: Update MMC " Sebastien Guiriec
2012-10-24 9:15 ` Benoit Cousson [this message]
2012-10-24 9:27 ` [PATCH v3 0/4] ARM: dts: Update OMAP5 " Sebastien Guiriec
2012-10-24 10:09 ` Benoit Cousson
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=5087B196.7090804@ti.com \
--to=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).