public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net•org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/6] ARM: OMAP2+: Remove board-omap4panda.c
Date: Mon, 17 Jun 2013 11:46:11 +0200	[thread overview]
Message-ID: <87li69qdcs.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <20130617082458.GH20992@atomide.com> (Tony Lindgren's message of "Mon, 17 Jun 2013 01:24:59 -0700")

Tony Lindgren <tony@atomide•com> writes:

Hi,

> * Arnaud Patard <arnaud.patard@rtp-net•org> [130617 01:13]:
>> 
>> I hoped to have missed some mails and that people were testing pandabard
>> support with full support but given what I see, the ethernet support is
>> not there yet. This thread is about removing the non-DT boot. I see some
>> contradiction here. Please, look again at what Thomas said in the IGEP thread:
>> breaking existing support is bad and removing non-DT boot for panda with
>> not-working ethernet would exactly to that.
>
> Hmm yes I guess the panda needs the aux clock and there are various
> patches posted for that for quite a while but have not gotten merged.

yes, it needs aux clock, see: https://lkml.org/lkml/2013/4/19/124

>
> When I did my patches it seemed that Nishant's and my solution for
> getting the auxclk via DT was acceptable. Then Mike started doing
> all the clocks in DT and things changed.
>
> Mike, got any solution for us for v3.11 for the DT defined auxclk?
>  
>> Yeah, I'm aware that some extra patches are being developped like the
>> omap clocks one: https://patchwork.kernel.org/patch/2541331/ but they
>> don't seem to be in -next. So, again, please, wait that all needed bits
>> are merged mainline before killing non-DT support (or provide 'mixed'
>> support like what is/was done on kirkwood)
>
> The ethernet issue can be fixed with the legacy mode support in the
> worst case, but probably just adding a clock alias for it does the
> trick.
>
> I'd rather not postpone making omap4 DT only because I think at this
> point fixing the any DT related issues is way less work compared to
> maintaining and testing both legacy boot and DT boot.

I understand your concerns but, please, cope with reality: the clock
work is not in -next so this tends to make me think it won't reach
3.11. We're at -rc6 after all. Telling users that their system doesn't
have any network because it was easier to maintain, is not something
they will understand imho.

Regards,
Arnaud

  reply	other threads:[~2013-06-17  9:46 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 19:17 [PATCH 0/6] Drop legacy booting for omap4 for v3.11, boot with device tree only Tony Lindgren
2013-05-17 19:17 ` [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c Tony Lindgren
2013-05-20  9:54   ` Russell King - ARM Linux
2013-05-20 17:10     ` Tony Lindgren
2013-07-06 13:10     ` Russell King - ARM Linux
2013-07-06 13:36       ` Russell King - ARM Linux
2013-07-08  9:34         ` Tony Lindgren
2013-07-08 14:21           ` Russell King - ARM Linux
2013-07-09  8:23             ` Tony Lindgren
2013-07-12  9:09               ` Peter Ujfalusi
2013-07-22  9:40             ` Tomi Valkeinen
2013-10-27 13:26               ` Javier Martinez Canillas
2013-10-28 13:32                 ` Tomi Valkeinen
2013-10-28 14:25                   ` Javier Martinez Canillas
2013-07-13  2:31         ` Olof Johansson
2013-07-13  3:10           ` Olof Johansson
2013-07-15  6:55             ` Tony Lindgren
2013-07-06 21:36       ` Arnd Bergmann
2013-07-06 23:37         ` debugging options (was: Re: [PATCH 1/6] ARM: OMAP2+: Remove board-4430sdp.c) Russell King - ARM Linux
2013-05-17 19:17 ` [PATCH 2/6] ARM: OMAP2+: Remove board-omap4panda.c Tony Lindgren
2013-06-03 15:28   ` Ming Lei
2013-06-12 16:31     ` Tony Lindgren
2013-06-12 17:14       ` Tony Lindgren
2013-06-13  9:21         ` Sricharan R
2013-06-13 10:12           ` Sricharan R
2013-06-13 11:05             ` Tony Lindgren
2013-06-13 13:36               ` Ming Lei
2013-06-14 13:31             ` Ming Lei
2013-06-14 13:58               ` Ming Lei
2013-06-17  7:42                 ` Sricharan R
2013-06-17  8:06                   ` Arnaud Patard (Rtp)
2013-06-17  8:16                     ` Ming Lei
2013-06-17  8:27                       ` Tony Lindgren
2013-06-17  8:41                         ` Ming Lei
2013-06-17  8:49                           ` Tony Lindgren
2013-06-17  8:24                     ` Tony Lindgren
2013-06-17  9:46                       ` Arnaud Patard (Rtp) [this message]
2013-06-17 10:26                         ` Tony Lindgren
2013-06-18 11:27                           ` Tony Lindgren
2013-06-19  9:45                             ` Arnaud Patard (Rtp)
2013-06-19  9:58                               ` Tony Lindgren
2013-06-20  7:29                                 ` Arnaud Patard (Rtp)
2013-06-21  6:01                                   ` Tony Lindgren
2013-05-17 19:17 ` [PATCH 3/6] ARM: OMAP2+: Remove legacy mux data for omap4 Tony Lindgren
2013-05-17 19:17 ` [PATCH 4/6] ARM: OMAP2+: Remove omap4 pdata from hsmmc.c Tony Lindgren
2013-05-17 19:18 ` [PATCH 5/6] ARM: OMAP2+: Remove omap4 pdata for USB Tony Lindgren
2013-05-17 19:18 ` [PATCH 6/6] ARM: OMAP2+: Remove omap4 ocp2scp pdata Tony Lindgren
2013-05-17 20:05   ` Felipe Balbi
2013-05-21 11:53   ` Kishon Vijay Abraham I
2013-06-07 10:05 ` [PATCH 0/6] Drop legacy booting for omap4 for v3.11, boot with device tree only Tomi Valkeinen

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=87li69qdcs.fsf@lebrac.rtp-net.org \
    --to=arnaud.patard@rtp-net$(echo .)org \
    --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