From: pawelo@king.net.pl (Paul Osmialowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/9] arm: twr-k70f120m: IOMUX driver for Kinetis SoC
Date: Tue, 8 Sep 2015 10:04:19 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1509080953390.31192@localhost.localdomain> (raw)
In-Reply-To: <CACRpkdYHBt7YJWM3Bg8ENfw7uL4fuENqW+g8YaO+P6UPBCX4HQ@mail.gmail.com>
Hi Linus,
On Tue, 14 Jul 2015, Linus Walleij wrote:
> OK...
>
> I want Shawn and Sascha to look at this as they worked with
> other Freescale pin controllers. Especially I want to know if this
> is a sibling to the other Freescale controllers or a separate hardware.
>
> If it is *not* a sibling I will *insist* that it use more generic pin
> control bindings and move away from the older Freescale-specific
> stuff.
No one answered me about that. However, I looked at other Freescale
pinctrl drivers and realised that no one of them (IMX, IMX1, MXS) is
similar to what I need to do for Kinetis, also positions of configuration
bits differ significantly.
>
> There exist generic pin config bindings, see
> Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
>
> I suggest to to function+group paring and then use generic pin config
> with this driver unless it is a very close sibling to the existing Freescale
> pin controllers.
>
> Hint: if it is a sibling, it should share code with them.
>
> There are several drivers doing generic pin control/pin config in the kernel
> tree.
>
I tried to analyze few of the drivers (e.g. zynq family) and can't find
how can I assing clock gate (clock device) to each port (PORTA, PORTB,
PORTC,...) which is required for Kinetis. Is generic pin control capable
to express that requirement or is it a time to desing my own pinctrl
driver (maybe somewhat improved than the one I presented so far)?
This pinctrl component is somwehat critical part of BSP. Until it is not
sorted, I don't see a point in releasing what was developed so far.
Best regards,
Paul
next prev parent reply other threads:[~2015-09-08 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1435094387-20146-1-git-send-email-pawelo@king.net.pl>
[not found] ` <1435094387-20146-2-git-send-email-pawelo@king.net.pl>
2015-06-23 21:48 ` [PATCH 1/9] arm: select different compiler flags for ARM CortexM3 Russell King - ARM Linux
2015-06-24 4:22 ` Paul Osmialowski
[not found] ` <1435094387-20146-4-git-send-email-pawelo@king.net.pl>
2015-06-23 21:51 ` [PATCH 3/9] arm: add call to CPU idle quirks handler Russell King - ARM Linux
[not found] ` <1435094387-20146-8-git-send-email-pawelo@king.net.pl>
2015-07-14 8:53 ` [PATCH 7/9] arm: twr-k70f120m: IOMUX driver for Kinetis SoC Linus Walleij
2015-09-08 8:04 ` Paul Osmialowski [this message]
2015-09-08 14:28 ` Linus Walleij
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=alpine.LNX.2.00.1509080953390.31192@localhost.localdomain \
--to=pawelo@king.net.pl \
--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