From: Javier Martinez Canillas <javier@dowhile0.org>
To: Enric Balletbo i Serra <eballetbo@iseebcn.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 01/11] ARM: dts: omap3-igep00x0: Fix UART2 pins that aren't common.
Date: Sat, 8 Nov 2014 21:32:49 +0100 [thread overview]
Message-ID: <CABxcv==J_uFRe-47GH9-6GS5PafwOnnkDhTALhHCxRjy4LKFtw@mail.gmail.com> (raw)
In-Reply-To: <1415275311-6857-2-git-send-email-eballetbo@iseebcn.com>
Hello Enric,
On Thu, Nov 6, 2014 at 1:01 PM, Enric Balletbo i Serra
<eballetbo@iseebcn.com> wrote:
> UART2 is used to connect the processor with the bluetooth chip, these pins
> are not common between IGEPv2 boards and IGEP COM MODULE boards. This patch
> muxes the correct pins for every board and removes UART2 configuration from
> common omap3-igep.dtsi file.
Acked-by: Javier Martinez Canillas <javier@dowhile0.org>
Best regards,
Javier
next prev parent reply other threads:[~2014-11-08 20:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 12:01 [PATCH 00/11] ARM: dts: igep00x0: Add support for new hardware revisions Enric Balletbo i Serra
2014-11-06 12:01 ` [PATCH 01/11] ARM: dts: omap3-igep00x0: Fix UART2 pins that aren't common Enric Balletbo i Serra
2014-11-08 20:32 ` Javier Martinez Canillas [this message]
2014-11-06 12:01 ` [PATCH 02/11] ARM: dts: omap3-igep00x0: Move NAND configuration to a common place Enric Balletbo i Serra
2014-11-09 8:17 ` Javier Martinez Canillas
2014-11-06 12:01 ` [PATCH 03/11] ARM: dts: omap3-igep0030: Specify IGEP COM revision in device tree Enric Balletbo i Serra
2014-11-09 9:51 ` Javier Martinez Canillas
2014-11-06 12:01 ` [PATCH 04/11] ARM: dts: omap3-igep0020: Specify IGEPv2 " Enric Balletbo i Serra
2014-11-09 10:03 ` Javier Martinez Canillas
2014-11-06 12:01 ` [PATCH 05/11] ARM: dts: omap3-igep00x0: Move outside common file the on board Wifi module Enric Balletbo i Serra
2014-11-09 10:05 ` Javier Martinez Canillas
[not found] ` <1415275311-6857-1-git-send-email-eballetbo-VIneJrwqLopBDgjK7y7TUQ@public.gmane.org>
2014-11-06 12:01 ` [PATCH 06/11] ARM: dts: omap3-igep0030-common: Introduce igep0030 common dtsi file Enric Balletbo i Serra
2014-11-09 10:06 ` Javier Martinez Canillas
2014-11-06 12:01 ` [PATCH 07/11] ARM: dts: omap3-igep0030-rev-g: Support IGEP COM MODULE Rev. G Enric Balletbo i Serra
2014-11-09 10:08 ` Javier Martinez Canillas
2014-11-06 12:01 ` [PATCH 08/11] ARM: dts: omap3-igep0020-common: Introduce igep0020 common dtsi file Enric Balletbo i Serra
2014-11-09 10:09 ` Javier Martinez Canillas
2014-11-06 12:01 ` [PATCH 09/11] ARM: dts: omap3-igep0020-rev-f: Support IGEPv2 Rev. F Enric Balletbo i Serra
2014-11-09 10:16 ` Javier Martinez Canillas
2014-11-06 12:01 ` [PATCH 10/11] ARM: dts: omap3-igep00x0: Remove i2c2 node Enric Balletbo i Serra
2014-11-09 10:17 ` Javier Martinez Canillas
2014-11-06 12:01 ` [PATCH 11/11] ARM: OMAP2+: igep00x0: Add pdata-quirks for the btwilink device Enric Balletbo i Serra
2014-11-09 10:23 ` Javier Martinez Canillas
2014-11-10 23:42 ` [PATCH 00/11] ARM: dts: igep00x0: Add support for new hardware revisions 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='CABxcv==J_uFRe-47GH9-6GS5PafwOnnkDhTALhHCxRjy4LKFtw@mail.gmail.com' \
--to=javier@dowhile0.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetbo@iseebcn.com \
--cc=linux-omap@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).