From: Roger Quadros <rogerq@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: wg@grandegger.com, mkl@pengutronix.de, wsa@the-dreams.de,
mugunthanvnm@ti.com, george.cherian@ti.com, balbi@ti.com,
nsekhar@ti.comnm@ti.com, sergei.shtylyov@cogentembedded.com,
linux-omap@vger.kernel.org, linux-can@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 00/10] ARM: dts: TI: Add CAN support
Date: Fri, 7 Nov 2014 14:44:28 +0200 [thread overview]
Message-ID: <545CBEAC.4050601@ti.com> (raw)
In-Reply-To: <20141105184953.GX31454@atomide.com>
On 11/05/2014 08:49 PM, Tony Lindgren wrote:
> * Roger Quadros <rogerq@ti.com> [141105 03:08]:
>> On 11/04/2014 05:55 PM, Tony Lindgren wrote:
>>> * Roger Quadros <rogerq@ti.com> [141104 02:50]:
>>>> Hi Tony,
>>>>
>>>> These patches add CAN support for am33xx, am43xx and dra7 platforms.
>>>> They must go in together with CAN driver RAMINIT Syscon support [1].
>>>
>>> Can you make this series not depend on [1] for most part without
>>> breaking existing functionality?
>>
>> I just checked that we haven't enabled DCAN on any of the boards
>> so we don't risk breaking anything even if these 2 series don't go in
>> together.
>
> OK
>
>>> Then we can do a single follow-up patch to enable things after [1]
>>> has been merged.
>>>
>>> That would remove a dependency between driver changes and .dts changes.
>>
>> Apart from patches 1, 3 and 8, that add the control module nodes the rest
>> pretty much depend on the driver DT binding changes.
>>
>> I can send them separately if needed.
>
> Well sounds like I can already apply the .dts changes without
> affecting anything until the driver changes are merged.
>
> Let me know if that's the case and I'll apply these assuming
> the binding is OK and not going to change.
There is one change in the binding so I'll have to post a v4.
cheers,
-roger
prev parent reply other threads:[~2014-11-07 12:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 10:48 [PATCH v3 00/10] ARM: dts: TI: Add CAN support Roger Quadros
2014-11-04 10:48 ` [PATCH v3 01/10] ARM: dts: dra7: Add syscon regmap for CORE CONTROL area Roger Quadros
2014-11-04 10:48 ` [PATCH v3 02/10] ARM: dts: DRA7: Add DCAN nodes Roger Quadros
2014-11-04 10:48 ` [PATCH v3 03/10] ARM: dts: dra7-evm: Add CAN support Roger Quadros
2014-11-04 10:48 ` [PATCH v3 04/10] ARM: dts: dra72-evm: " Roger Quadros
2014-11-04 10:48 ` [PATCH v3 05/10] ARM: dts: am4372: Add control module syscon node Roger Quadros
2014-11-04 10:48 ` [PATCH v3 06/10] ARM: dts: am4372: Add DCAN nodes Roger Quadros
2014-11-04 10:48 ` [PATCH v3 07/10] arm: dts: am437x-gp: Add dcan support Roger Quadros
2014-11-04 10:48 ` [PATCH v3 08/10] ARM: dts: am33xx: Add control module syscon node Roger Quadros
2014-11-04 10:48 ` [PATCH v3 09/10] ARM: dts: am33xx: Update DCAN nodes Roger Quadros
2014-11-04 10:48 ` [PATCH v3 10/10] ARM: dts: am335x-evm: Add DCAN1 details Roger Quadros
2014-11-04 15:55 ` [PATCH v3 00/10] ARM: dts: TI: Add CAN support Tony Lindgren
2014-11-05 11:06 ` Roger Quadros
2014-11-05 18:49 ` Tony Lindgren
2014-11-07 12:44 ` Roger Quadros [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=545CBEAC.4050601@ti.com \
--to=rogerq@ti.com \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--cc=mkl@pengutronix.de \
--cc=mugunthanvnm@ti.com \
--cc=nsekhar@ti.comnm \
--cc=tony@atomide.com \
--cc=wg@grandegger.com \
--cc=wsa@the-dreams.de \
/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).