mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Arnd Bergmann <arnd@arndb.de>, Michal Simek <michal.simek@xilinx.com>
Cc: Dhaval Shah <dhaval.shah@xilinx.com>,
	gregkh <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	DTML <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hyun Kwon <hyunk@xilinx.com>, Dhaval Shah <dshah@xilinx.com>
Subject: Re: [PATCH v4 2/2] misc: xlnx_vcu: Add Xilinx ZYNQMP VCU logicoreIP init driver
Date: Tue, 19 Dec 2017 14:24:55 +0100	[thread overview]
Message-ID: <f11d2f97-3eda-d43d-2cbd-96d2c331fd47@xilinx.com> (raw)
In-Reply-To: <CAK8P3a0z6HF8Rg08HUj7_T+7ZxxnHoReiu68bNzF6CnEooQSdA@mail.gmail.com>

On 18.12.2017 15:05, Arnd Bergmann wrote:
> On Mon, Dec 18, 2017 at 2:13 PM, Michal Simek <michal.simek@xilinx.com> wrote:
>> On 15.12.2017 14:26, Arnd Bergmann wrote:
>>> In Fri, Dec 15, 2017 at 8:24 AM, Dhaval Shah <dhaval.shah@xilinx.com> wrote:
>>>> Xilinx ZYNQMP logicoreIP Init driver is based on the new
>>>> LogiCoreIP design created. This driver provides the processing system
>>>> and programmable logic isolation. Set the frequency based on the clock
>>>> information get from the logicoreIP register set.
>>>>
>>>> It is put in drivers/misc as there is no subsystem for this logicoreIP.
>>>>
>>>> Signed-off-by: Dhaval Shah <dshah@xilinx.com>
>>>
>>> After giving this some more thought, I'd suggest you move the driver to
>>> drivers/soc/xilinx or drivers/soc/zynq instead of drivers/misc/, and have
>>> it merged by Michal Simek as a driver patch that will go through arm-soc.
>>
>> I have not a problem of creating drivers/soc/xilinx/ location for this
>> driver. It is not zynq (arm32) but zynqmp(arm64) device where this
>> driver can be used. As far as I understand it is memory mapped soft IP
>> which could be also accessed by soft core CPU.
> 
> Ok. I wouldn't be worried about having a zynq directory for stuff that
> is common between zynq and zynqmp, but the soft code CPU case
> wouldn't make that ideal.
> 
>> It means drivers/soc/xilinx could be shared by all xilinx platforms anyway.
>> We have been discussing that openrisc cases and for sure if someone
>> wants to enable this driver there using misc location would be one
>> option but I also think that using drivers/soc/xilinx location is not a
>> bad option because it is very unlikely that anybody tries it.
>>
>> Arnd: misc or drivers/soc/xilinx?
> 
> drivers/soc/xilinx please, thanks for the clarification.
> 

ok. I have sent patch which prepare structures in drivers/soc/xilinx.

Dhaval: Please rebase your patch based on this and put driver to this
location.

Thanks,
Michal

  reply	other threads:[~2017-12-19 13:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703.nxabyfcjbswwbp4v@rob-hp-laptop>
2017-12-14  5:55 ` [PATCH v3 0/2] Documentation and driver of logicoreIP Dhaval Shah
2017-12-14  5:55   ` [PATCH v3 1/2] dt-bindings: misc: Add DT bindings to xlnx_vcu driver Dhaval Shah
2017-12-14  5:55   ` [PATCH v3 2/2] misc: Add Xilinx ZYNQMP VCU logicoreIP init driver Dhaval Shah
2017-12-14 18:42     ` Randy Dunlap
2017-12-15  6:00       ` Dhaval Rajeshbhai Shah
2017-12-15  7:24       ` [PATCH v4 0/2] Documentation and driver of logicoreIP Dhaval Shah
2017-12-15  7:24         ` [PATCH v4 1/2] dt-bindings: misc: Add DT bindings to xlnx_vcu driver Dhaval Shah
2017-12-16 18:20           ` Rob Herring
2017-12-15  7:24         ` [PATCH v4 2/2] misc: xlnx_vcu: Add Xilinx ZYNQMP VCU logicoreIP init driver Dhaval Shah
2017-12-15 13:26           ` Arnd Bergmann
2017-12-18 13:13             ` Michal Simek
2017-12-18 14:05               ` Arnd Bergmann
2017-12-19 13:24                 ` Michal Simek [this message]
2017-12-21 18:33                 ` [PATCH v6 0/2] Documentation and driver of logicoreIP Dhaval Shah
2017-12-21 18:33                   ` [PATCH v6 1/2] dt-bindings: soc: xilinx: Add DT bindings to xlnx_vcu driver Dhaval Shah
2017-12-21 18:33                   ` [PATCH v6 2/2] soc: xilinx: xlnx_vcu: Add Xilinx ZYNQMP VCU logicoreIP init driver Dhaval Shah
2018-01-08 12:43                   ` [PATCH v6 0/2] Documentation and driver of logicoreIP Michal Simek
2017-12-16 22:18           ` [PATCH v4 2/2] misc: xlnx_vcu: Add Xilinx ZYNQMP VCU logicoreIP init driver Randy Dunlap
2017-12-17  6:07             ` Dhaval Rajeshbhai Shah
2017-12-17 17:40               ` Randy Dunlap
2017-12-18  5:37                 ` Dhaval Rajeshbhai Shah
2017-12-18  6:15                 ` [PATCH v5 0/2] Documentation and driver of logicoreIP Dhaval Shah
2017-12-18  6:15                   ` [PATCH v5 1/2] dt-bindings: misc: Add DT bindings to xlnx_vcu driver Dhaval Shah
2017-12-19 23:09                     ` Rob Herring
2017-12-20  3:00                       ` Dhaval Rajeshbhai Shah
2017-12-18  6:15                   ` [PATCH v5 2/2] misc: xlnx_vcu: Add Xilinx ZYNQMP VCU logicoreIP init driver Dhaval Shah

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=f11d2f97-3eda-d43d-2cbd-96d2c331fd47@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dhaval.shah@xilinx.com \
    --cc=dshah@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hyunk@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.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

all inboxes | Powered by JetHome®