public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aida Mynzhasova <aida.mynzhasova@skitlab.ru>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com,
	linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Broken DM816x support in Linux 3.10-rc4
Date: Thu, 06 Jun 2013 10:03:42 +0400	[thread overview]
Message-ID: <51B0263E.6000109@skitlab.ru> (raw)
In-Reply-To: <alpine.DEB.2.02.1306060346390.15042@utopia.booyaka.com>

On 06.06.2013 07:54, Paul Walmsley wrote:
> здравствуйте,
>
> On Wed, 5 Jun 2013, Aida Mynzhasova wrote:
>
>> Not so long ago I tried to boot Linux 3.10-rc4 kernel on DM816x EVM
>> board. Unfortunately, my attempts were failed by reason of poor
>> support of DM81xx-based devices in new kernels.
>
> Yeah, TI pretty much gave up on trying to get support for that chip
> upstream a few years ago.  Same for DM814x.
>
>> So, I suggest you this patch series, which fixes that kernel crush and
>> adds new functions/structures, required for early initialization on
>> DM816x (power and clock domains, hwmods). After applying these patches
>> the kernel is able to successfully continue booting till clock
>> initialization (will be added later).
>
> OK, it will be great to get my DM8168EVM booting on mainline.  But there
> are a few preliminary issues with the patches:
>
> 1. All new chip and board support needs to be DT-only.  So, no new board
> files.  Also, all the hwmod data shouldn't have IRQ, DMA, etc. data - that
> should come from DT.  See for example the recently posted patch "[PATCH
> 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up"
>
> 2. Looks like patch 2 is missing from the list.  If it's too big for the
> list, please break it down into smaller patches.
>
> 3. Did you write this code and data, hwmods, etc., or did it come from a
> TI kernel?  Please note this clearly in the patch descriptions.
>
>
> - Paul
>

Hi!

Thanks for reply!
ok, I'll rewrite code by means of DT and add some additional notes to 
patch description.

Aida.

  reply	other threads:[~2013-06-06  6:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 15:29 [PATCH 0/5] Broken DM816x support in Linux 3.10-rc4 Aida Mynzhasova
2013-06-05 15:29 ` [PATCH 1/5] ARM: OMAP: DM81xx: multiple renames for DM81xx platform Aida Mynzhasova
2013-06-05 15:29 ` [PATCH 2/5] ARM: OMAP: AM33xx: multiple renames for early initialization Aida Mynzhasova
2013-06-05 15:29 ` [PATCH 3/5] ARM: OMAP: DM816x: add powerdomains for DM816x Aida Mynzhasova
2013-06-05 15:29 ` [PATCH 4/5] ARM: OMAP: DM816x: add clock domain support " Aida Mynzhasova
2013-06-05 15:29 ` [PATCH 5/5] ARM: OMAP: DM816x: add hwmod support for DM81xx Aida Mynzhasova
2013-06-06  3:54 ` [PATCH 0/5] Broken DM816x support in Linux 3.10-rc4 Paul Walmsley
2013-06-06  6:03   ` Aida Mynzhasova [this message]
2013-06-06  4:16 ` Paul Walmsley
2013-06-06 15:55   ` 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=51B0263E.6000109@skitlab.ru \
    --to=aida.mynzhasova@skitlab.ru \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --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