mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Appana Durga Kedareswara Rao <appana.durga.rao@xilinx.com>
To: "monstr@monstr.eu" <monstr@monstr.eu>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "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>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"grant.likely@linaro.org" <grant.likely@linaro.org>,
	Michal Simek <michals@xilinx.com>,
	"wg@grandegger.com" <wg@grandegger.com>,
	"fengguang.wu@intel.com" <fengguang.wu@intel.com>
Subject: RE: [PATCH v5] can: xilinx CAN controller support.
Date: Thu, 20 Mar 2014 04:41:56 +0000	[thread overview]
Message-ID: <45bec219-6349-4bcf-be8a-7ee1dfd1bcb9@TX2EHSMHS014.ehs.local> (raw)
In-Reply-To: <53203088.2070605@monstr.eu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2934 bytes --]

Hi Marc,

> -----Original Message-----
> From: Michal Simek [mailto:monstr@monstr.eu]
> Sent: Wednesday, March 12, 2014 3:32 PM
> To: Marc Kleine-Budde
> Cc: Appana Durga Kedareswara Rao; linux-can@vger.kernel.org;
> netdev@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> kernel@vger.kernel.org; devicetree@vger.kernel.org; robh+dt@kernel.org;
> grant.likely@linaro.org; Michal Simek; wg@grandegger.com;
> fengguang.wu@intel.com
> Subject: Re: [PATCH v5] can: xilinx CAN controller support.
>
> On 03/11/2014 01:48 PM, Marc Kleine-Budde wrote:
> > On 03/11/2014 01:34 PM, Appana Durga Kedareswara Rao wrote:
> >
> >>>> diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig
> >>>> index
> >>>> 9e7d95d..b180239 100644
> >>>> --- a/drivers/net/can/Kconfig
> >>>> +++ b/drivers/net/can/Kconfig
> >>>> @@ -125,6 +125,13 @@ config CAN_GRCAN
> >>>>       endian syntheses of the cores would need some modifications on
> >>>>       the hardware level to work.
> >>>>
> >>>> +config CAN_XILINXCAN
> >>>> +   tristate "Xilinx CAN"
> >>>> +   depends on ARCH_ZYNQ || MICROBLAZE
> >>>
> >>> Is Zynq multiarch already?
> >> Discussions are going on this
> >> So the final thing that Fengguang ( fengguang.wu@intel.com) Proposed
> >> is
> >>         config CAN_XILINX
> >>         tristate "Xilinx CAN"
> >>         depends on ARCH_ZYNQ || MICROBLAZE || COMPILE_TEST
> >>         depends on COMMON_CLK && HAS_MMIO  # whatever you need for
> >> other architectures
> >
> >> Are you Ok for this?
> >
> > You have to fill the 2nd depends on with some sane values, though.
>
> This should be that one
> config CAN_XILINX
>          tristate "Xilinx CAN"
>          depends on ARCH_ZYNQ || MICROBLAZE || COMPILE_TEST
>          depends on COMMON_CLK && HAS_IOMEM
>
>
> Is there any driver which is in CAN which not use MMIO accesses?
> If not, maybe we should just add dependency to



Can you please comment on this?
I had update driver with all the other comments I had a little confusion regarding
Which Kconfig options I need to use.

Regards,
Kedar.


> Thanks,
> Michal
>
>
>
> --
> Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
> w: www.monstr.eu p: +42-0-721842854
> Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
> Maintainer of Linux kernel - Xilinx Zynq ARM architecture Microblaze U-
> BOOT custodian and responsible for u-boot arm zynq platform
>



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.



ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2014-03-20  4:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 13:20 Kedareswara rao Appana
2014-03-04 23:51 ` Sören Brinkmann
2014-03-05  6:58   ` Oliver Hartkopp
2014-03-05  7:04     ` Appana Durga Kedareswara Rao
     [not found] ` <20140304235115.GN13293@xsjandreislx>
2014-03-05  7:03   ` Appana Durga Kedareswara Rao
2014-03-10 14:57 ` Marc Kleine-Budde
2014-03-10 15:04   ` Michal Simek
2014-03-10 15:10     ` Marc Kleine-Budde
2014-03-10 15:15       ` Arnd Bergmann
2014-03-10 15:26         ` Michal Simek
2014-03-11  4:45           ` Fengguang Wu
2014-03-11  9:38             ` Michal Simek
2014-03-13 11:21               ` Fengguang Wu
2014-03-11 12:34   ` Appana Durga Kedareswara Rao
2014-03-11 12:48     ` Marc Kleine-Budde
2014-03-11 14:08       ` Appana Durga Kedareswara Rao
2014-03-11 14:31         ` Marc Kleine-Budde
2014-03-12 10:18           ` Michal Simek
2014-03-12 16:18             ` Sören Brinkmann
2014-03-12 10:01       ` Michal Simek
2014-03-20  4:41         ` Appana Durga Kedareswara Rao [this message]
2014-03-10 15:15 ` Rob Herring
2014-03-10 15:22   ` Michal Simek
     [not found]   ` <531DD8C3.5050006@xilinx.com>
2014-03-11 12:35     ` Appana Durga Kedareswara Rao
     [not found] <1393939253-30245-1-git-send-email-appanad@xilinx.com>
2014-03-10  7:12 ` Appana Durga Kedareswara Rao

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=45bec219-6349-4bcf-be8a-7ee1dfd1bcb9@TX2EHSMHS014.ehs.local \
    --to=appana.durga.rao@xilinx.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fengguang.wu@intel.com \
    --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=michals@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome