public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Liam Beguin <liambeguin@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ZynqMP qspi
Date: Tue, 26 Sep 2017 07:24:43 -0400	[thread overview]
Message-ID: <234cbfad-954d-9970-0539-1ef3f1cc3eac@gmail.com> (raw)
In-Reply-To: <CO1PR02MB240A739D765D71D9AE1CD8AD97B0@CO1PR02MB240.namprd02.prod.outlook.com>

Hi,

On 26/09/17 01:28 AM, Siva Durga Prasad Paladugu wrote:
> Hi,
> 
>> -----Original Message-----
>> From: Jagan Teki [mailto:jagannadh.teki at gmail.com]
>> Sent: Tuesday, September 26, 2017 10:17 AM
>> To: Liam Beguin <liambeguin@gmail.com>
>> Cc: u-boot at lists.denx.de; Michal Simek <michals@xilinx.com>; Siva Durga
>> Prasad Paladugu <sivadur@xilinx.com>
>> Subject: Re: [U-Boot] ZynqMP qspi
>>
>> On Tue, Sep 26, 2017 at 9:07 AM, Liam Beguin <liambeguin@gmail.com>
>> wrote:
>>>
>>> Resending with proper CC since the email came back.
>>>
>>> On 24/09/17 09:36 PM, Liam Beguin wrote:
>>>> Hi,
>>>>
>>>> I'm testing a new Xilinx zynqmp dev board and was not able to probe
>>>> the qspi with the latest mainline U-Boot. I see that there is a
>> 'zynqmp_qspi'
>>>> driver in the Xilinx tree [1] but nothing in mainline. After a little
>>>> digging, I found a thread on the list [2] (and [3]) and was wondering
>>>> in what state this was now.
> 
> I am planning to send the new series in 1-2 weeks, probably you can wait till then or
> you can try with the patch[2] and see if you are able to get it working with those( those
> are known to be working when I sent ). Also, please note that as of now iam  targeting
> only for qspi single mode not the dual modes.
> 

Great, I'll wait for your series and test it as soon as it comes out.

Thanks,
Liam

> Thanks,
> Siva
> 
>>>>
>>>> [1]
>>>> https://github.com/Xilinx/u-boot-
>> xlnx/blob/master/drivers/spi/zynqmp_
>>>> qspi.c [2]
>>>> https://lists.denx.de/pipermail/u-boot/2016-July/261003.html
>>>> [3] https://lists.denx.de/pipermail/u-boot/2016-
>> November/273650.html
>>
>> I think, Siva is working on it. and he would be best to comment this.
>>
>> thanks!
>> --
>> Jagan Teki
>> Free Software Engineer | www.openedev.com U-Boot, Linux | Upstream
>> Maintainer Hyderabad, India.

  reply	other threads:[~2017-09-26 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25  1:36 [U-Boot] ZynqMP qspi Liam Beguin
2017-09-26  3:37 ` Liam Beguin
2017-09-26  4:46   ` Jagan Teki
2017-09-26  5:28     ` Siva Durga Prasad Paladugu
2017-09-26 11:24       ` Liam Beguin [this message]
2017-10-21 18:02       ` Liam Beguin
2017-10-23  5:59         ` Siva Durga Prasad Paladugu
2017-10-24  3:02           ` Liam Beguin

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=234cbfad-954d-9970-0539-1ef3f1cc3eac@gmail.com \
    --to=liambeguin@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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