From: Arnd Bergmann <arnd@arndb.de>
To: monstr@monstr.eu
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Michal Simek <michal.simek@xilinx.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Appana Durga Kedareswara Rao <appana.durga.rao@xilinx.com>,
"wg@grandegger.com" <wg@grandegger.com>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] can: xilinx CAN controller support.
Date: Tue, 11 Feb 2014 15:12:45 +0100 [thread overview]
Message-ID: <201402111512.45678.arnd@arndb.de> (raw)
In-Reply-To: <52FA2419.70102@monstr.eu>
On Tuesday 11 February 2014, Michal Simek wrote:
> >> The only remaining question is if we should create generic DT binding
> >> for fifo depth. Arnd, Rob: Any opinion about it?
> >> Definitely will be worth to have one generic binding if this is generic feature.
> >> But if this is just specific feature for us then current properties should
> >> be fine.
> >>
> >> In general all these xlnx,XXX properties just reflect all configurable options
> >> which you can setup in design tool which means that provide full hw description
> >> with all variants and they are automatically generated from tools.
> >>
> >> Please let me know what you think.
> >
> > I like:
> >
> > rx-fifo-depth
> > tx-fifo-depth
>
> No problem with that. Let Kedar to fix it according this and he will send v2 with this.
>
Sounds reasonable to me too.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] can: xilinx CAN controller support.
Date: Tue, 11 Feb 2014 15:12:45 +0100 [thread overview]
Message-ID: <201402111512.45678.arnd@arndb.de> (raw)
In-Reply-To: <52FA2419.70102@monstr.eu>
On Tuesday 11 February 2014, Michal Simek wrote:
> >> The only remaining question is if we should create generic DT binding
> >> for fifo depth. Arnd, Rob: Any opinion about it?
> >> Definitely will be worth to have one generic binding if this is generic feature.
> >> But if this is just specific feature for us then current properties should
> >> be fine.
> >>
> >> In general all these xlnx,XXX properties just reflect all configurable options
> >> which you can setup in design tool which means that provide full hw description
> >> with all variants and they are automatically generated from tools.
> >>
> >> Please let me know what you think.
> >
> > I like:
> >
> > rx-fifo-depth
> > tx-fifo-depth
>
> No problem with that. Let Kedar to fix it according this and he will send v2 with this.
>
Sounds reasonable to me too.
Arnd
next prev parent reply other threads:[~2014-02-11 14:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 10:19 [PATCH] can: xilinx CAN controller support Kedareswara rao Appana
2014-02-06 10:19 ` Kedareswara rao Appana
2014-02-06 10:19 ` Kedareswara rao Appana
2014-02-06 10:19 ` Kedareswara rao Appana
2014-02-06 12:40 ` Marc Kleine-Budde
2014-02-06 12:40 ` Marc Kleine-Budde
2014-02-07 8:42 ` Appana Durga Kedareswara Rao
2014-02-07 8:42 ` Appana Durga Kedareswara Rao
2014-02-07 8:42 ` Appana Durga Kedareswara Rao
2014-02-07 9:37 ` Marc Kleine-Budde
2014-02-07 9:37 ` Marc Kleine-Budde
2014-02-11 11:45 ` Michal Simek
2014-02-11 11:45 ` Michal Simek
2014-02-11 12:35 ` Marc Kleine-Budde
2014-02-11 12:35 ` Marc Kleine-Budde
2014-02-11 13:22 ` Michal Simek
2014-02-11 13:22 ` Michal Simek
2014-02-11 14:12 ` Arnd Bergmann [this message]
2014-02-11 14:12 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2014-02-17 9:23 Kedareswara rao Appana
2014-02-17 9:23 ` Kedareswara rao Appana
2014-02-17 9:23 ` Kedareswara rao Appana
2014-02-17 9:23 ` Kedareswara rao Appana
2014-02-17 9:37 ` Marc Kleine-Budde
2014-02-17 9:37 ` Marc Kleine-Budde
2014-02-17 9:42 ` Marc Kleine-Budde
2014-02-17 9:42 ` Marc Kleine-Budde
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=201402111512.45678.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=appana.durga.rao@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mkl@pengutronix.de \
--cc=monstr@monstr.eu \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wg@grandegger.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 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.