From: hvaibhav@ti•com (Vaibhav Hiremath)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH RESEND v5 0/4] OMAP GPMC DT bindings
Date: Fri, 30 Nov 2012 11:23:43 +0530 [thread overview]
Message-ID: <50B849E7.30600@ti.com> (raw)
In-Reply-To: <50B77DD5.4090001@gmail.com>
On 11/29/2012 8:53 PM, Daniel Mack wrote:
> On 29.11.2012 16:08, Philip, Avinash wrote:
>> On Thu, Nov 29, 2012 at 17:28:04, Daniel Mack wrote:
>>> Hi Avinash,
>>>
>>> On 29.11.2012 06:24, Philip, Avinash wrote:
>>>> On Wed, Nov 28, 2012 at 22:28:55, Daniel Mack wrote:
>>>>> [Resending +devicetree-discuss, +Rob, +Grant]
>>>>>
>>>>>
>>>>> This is a series of patches to support GPMC peripherals on OMAP boards.
>>>>>
>>>>> Depends on Linus' master +
>>>>> omap-next (branch omap-for-v3.8/cleanup-headers-gpmc)
>>>>
>>>> Can you resend this series on top of linux_next?
>>>
>>> The only branch these patches depend on is the
>>> "omap-for-v3.8/cleanup-headers-gpmc" branch from omap_next. Are you
>>> actually seeing any merge conflicts with my series? If so, which branch
>>> are you referring to exactly?
>>>
>>>> Some of the missing items I seen
>>>> 1. Of_node not populated in omap_nand_platform_data structure.
>>>
>>> Hmm - gpmc_probe_nand_child() from 4/4 adds
>>>
>>> gpmc_nand_data->of_node = child;
>>>
>>> Do I miss anything?
>>
>> I didn't found definition for of_node member in omap_nand_platform_data
>> structure. This also might be missing in liniux-next?
>
> Ah, right. I got that entry from your patch ("mtd: nand: omap2: Support
> for hardware BCH error correction"). But you're right, it should be part
> of my series. Will add that when resending, but note that your ELM
> series will then cause a (trivial) merge conflict.
>
>>>> 2. Remove platform device creation from hwmod as GPMC DT is populating.
>>>> Currently GPMC device creaing from DT & HWMOD.
>>>
>>> This is already addressed in cd00b0530 ("ARM: OMAP2+: gpmc: Fix kernel
>>> BUG for DT boot mode") by Vaibhav Hiremath, which I got via Afzal's USB
>>> branch:
>>
>> Purpose of VH's patch was to get beagle bone booting, but Jon sent another
>> patch that made beagle bone boot and it has reached mainline by v3.7-rc2,
>> hence the patch you are referring to is currently not going upstream. Still to
>> have GPMC DT work, we need that patch as other wise there would be two GPMC
>> devices. In earlier versions of your series, you had a similar patch, it is
>> required, can you please add it to your series as otherwise with your series
>> GPMC DT won't work.
>
> Ok, fine. Will do.
>
Feel free to take that patch forward, merge into your series.
Thanks,
Vaibhav
>
> Daniel
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-11-30 5:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 16:58 [PATCH RESEND v5 0/4] OMAP GPMC DT bindings Daniel Mack
2012-11-28 16:58 ` [PATCH v5 1/4] mtd: omap-nand: pass device_node in platform data Daniel Mack
2012-11-28 16:58 ` [PATCH v5 2/4] ARM: OMAP: gpmc-nand: drop __init annotation Daniel Mack
2012-11-28 16:58 ` [PATCH v5 3/4] ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs Daniel Mack
2012-11-28 16:58 ` [PATCH v5 4/4] ARM: OMAP: gpmc: add DT bindings for GPMC timings and NAND Daniel Mack
2012-11-29 12:36 ` Philip, Avinash
2012-11-29 12:41 ` Daniel Mack
2012-11-29 14:59 ` Philip, Avinash
2012-11-29 15:07 ` Daniel Mack
2012-11-29 15:24 ` Philip, Avinash
2012-11-29 5:24 ` [PATCH RESEND v5 0/4] OMAP GPMC DT bindings Philip, Avinash
2012-11-29 11:58 ` Daniel Mack
2012-11-29 15:08 ` Philip, Avinash
2012-11-29 15:23 ` Daniel Mack
2012-11-30 5:53 ` Vaibhav Hiremath [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=50B849E7.30600@ti.com \
--to=hvaibhav@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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