All of lore.kernel.org
 help / color / mirror / Atom feed
From: mans@mansr.com (Måns Rullgård)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 1/2] arm-soc: Import initial tango4 device tree
Date: Wed, 18 Nov 2015 17:18:39 +0000	[thread overview]
Message-ID: <yw1xio4zfcpc.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <CAOesGMjCw_DYB3OktnQvthqBAQxqeH6F0bXR-KW_36Y9sDh+fg@mail.gmail.com> (Olof Johansson's message of "Wed, 18 Nov 2015 09:11:54 -0800")

Olof Johansson <olof@lixom.net> writes:

> On Wed, Nov 18, 2015 at 8:38 AM, M?ns Rullg?rd <mans@mansr.com> wrote:
>> Marc Gonzalez <marc_gonzalez@sigmadesigns.com> writes:
>>
>>> On 18/11/2015 17:05, M?ns Rullg?rd wrote:
>>>
>>>> Marc Gonzalez wrote:
>>>>
>>>>> +           clkgen: clkgen at 10000 {
>>>>> +                   compatible = "sigma,tango4-clkgen";
>>>>> +                   reg = <0x10000 0x40>;
>>>>> +                   clocks = <&xtal>;
>>>>> +                   clock-output-names = "cpuclk", "sysclk";
>>>>> +                   #clock-cells = <1>;
>>>>> +           };
>>>>
>>>> Would you please consider using my clock driver that matches the actual
>>>> hardware, supports all the clock outputs required for USB, SATA, etc,
>>>> and works on tango3 as well?
>>>
>>> I was hoping to take baby steps to work up to a fully-functional port.
>>> The first step (in my mind) is this submission: a minimal port which
>>> only requires the two "main" clocks.
>>>
>>> The next step will add to the minimal port by supporting as many
>>> peripherals as possible, as well as their required clocks.
>>
>> But the code already exists.  Why start over?
>
> M?ns, I don't understand your role in this. Can you clarify?

Oh, I'm just the guy who did all the work and then got screwed over by
Sigma.

> If you've already done a port, why haven't you contributed it
> yourself?

Because it's not yet in a shape to be contributed, just like Marc's
isn't.

> Why are you driving Marc's work from the back seat like this instead
> of submitting your own work?

I have submitted bits and pieces.  It's a slow process.

-- 
M?ns Rullg?rd
mans at mansr.com

  reply	other threads:[~2015-11-18 17:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 15:09 [PATCH v9 0/2] Sigma Designs Tango4 port Marc Gonzalez
2015-11-18 15:10 ` [PATCH v9 1/2] arm-soc: Import initial tango4 device tree Marc Gonzalez
2015-11-18 16:05   ` Måns Rullgård
2015-11-18 16:34     ` Marc Gonzalez
2015-11-18 16:38       ` Måns Rullgård
2015-11-18 17:11         ` Olof Johansson
2015-11-18 17:18           ` Måns Rullgård [this message]
2015-11-19 13:53             ` Marc Gonzalez
2015-11-19 14:43               ` Måns Rullgård
     [not found]                 ` <564EFB18.3050104@sigmadesigns.com>
2015-11-20 12:08                   ` Tango4 clkgen block Måns Rullgård
2015-11-18 15:12 ` [PATCH v9 2/2] arm-soc: Add support for tango4 platforms Marc Gonzalez
2015-11-18 18:04   ` Kevin Hilman
2015-11-18 18:16     ` Måns Rullgård
2015-11-18 19:39       ` Kevin Hilman
2015-11-19 17:24     ` Marc Gonzalez
2015-11-19 19:32       ` Kevin Hilman
2015-11-19 19:49   ` Kevin Hilman
2015-11-20 10:04     ` Marc Gonzalez
2015-11-24 18:05       ` Kevin Hilman

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=yw1xio4zfcpc.fsf@unicorn.mansr.com \
    --to=mans@mansr.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.