linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefan.mavrodiev@gmail.com (Stefan Mavrodiev)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] arm: sunxi: Add alternative pins for spi0
Date: Mon, 18 Dec 2017 08:24:21 +0200	[thread overview]
Message-ID: <ca648552-cefb-e19d-72cf-8b56e97b013d@gmail.com> (raw)
In-Reply-To: <20171215150823.jplgknururmkvp2t@flea.lan>

On 12/15/2017 05:08 PM, Maxime Ripard wrote:
> Hi,
>
> On Thu, Dec 14, 2017 at 08:24:54AM +0200, Stefan Mavrodiev wrote:
>> On 12/13/2017 05:40 PM, Maxime Ripard wrote:
>>> Hi,
>>>
>>> On Wed, Dec 13, 2017 at 09:44:34AM +0200, Stefan Mavrodiev wrote:
>>>> Allwinner A10/A13/A20 SoCs have pinmux for spi0
>>>> on port C. The patch adds these pins in the respective
>>>> dts includes.
>>>>
>>>> Signed-off-by: Stefan Mavrodiev <stefan@olimex.com>
>>> Do you have any boards that are using these?
>>>
>>> We won't merge that patch if there's no users for it.
>> A20-OLinuXino-Lime/Lime2 and A10-OLinuXino-Lime with spi flash.
>> For A13 we still doesn't have that option.
> If this bus is exposed on the headers, you can add those to the DT but
> leave them disabled if you want. Buf if there's no users of those
> nodes, our policy is not to merge them.
So basically I should resend the patch, enabling the those pins only for
sun4i and sun7i platform?
>
> Thanks!
> Maxime
>
Regards,
Stefan Mavrodiev

  reply	other threads:[~2017-12-18  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  7:44 [PATCH 1/1] arm: sunxi: Add alternative pins for spi0 Stefan Mavrodiev
2017-12-13 15:40 ` Maxime Ripard
2017-12-14  6:24   ` Stefan Mavrodiev
2017-12-15 15:08     ` Maxime Ripard
2017-12-18  6:24       ` Stefan Mavrodiev [this message]
2017-12-18  9:28         ` Maxime Ripard
2017-12-18 11:00           ` Stefan Mavrodiev

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=ca648552-cefb-e19d-72cf-8b56e97b013d@gmail.com \
    --to=stefan.mavrodiev@gmail.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 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).