All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>,
	linux-omap@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: dra7xx driver status
Date: Fri, 5 Feb 2016 21:31:17 +0530	[thread overview]
Message-ID: <56B4C74D.9010408@ti.com> (raw)
In-Reply-To: <20160205155215.GA29306@localhost>

Hi Bjorn,

On Friday 05 February 2016 09:22 PM, Bjorn Helgaas wrote:
> On Fri, Feb 05, 2016 at 09:45:29AM +0530, Kishon Vijay Abraham I wrote:
>> Hi Bjorn,
>>
>> On Friday 05 February 2016 02:15 AM, Bjorn Helgaas wrote:
>>> Hi Kishon,
>>>
>>> What's the state of dra7xx?  In my tree, it's still marked with
>>> CONFIG_BROKEN.  Last I heard there was a reset issue that needed to
>>> be worked out, but I don't know whether that's been done yet.
>>
>> I've posted pdata-quirks mechanism to do the reset (which will get PCIe
>> working). Tony had some comments and we are expecting feedback from Paul. I'll
>> ping him again in that thread.
> 
> Great, thanks, can you cc me as well?  I want to make sure we don't

you seem to be already copied in that thread. Check with $subject=[PATCH v3
3/3] pci: dra7xx: use pdata callbacks to perform reset.

Thanks
Kishon
> carry dra7xx around forever marked as broken.  I'd like to either
> make progress or remove it.
> 
> Bjorn
> 

WARNING: multiple messages have this Message-ID (diff)
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>,
	<linux-omap@vger.kernel.org>, <linux-pci@vger.kernel.org>
Subject: Re: dra7xx driver status
Date: Fri, 5 Feb 2016 21:31:17 +0530	[thread overview]
Message-ID: <56B4C74D.9010408@ti.com> (raw)
In-Reply-To: <20160205155215.GA29306@localhost>

Hi Bjorn,

On Friday 05 February 2016 09:22 PM, Bjorn Helgaas wrote:
> On Fri, Feb 05, 2016 at 09:45:29AM +0530, Kishon Vijay Abraham I wrote:
>> Hi Bjorn,
>>
>> On Friday 05 February 2016 02:15 AM, Bjorn Helgaas wrote:
>>> Hi Kishon,
>>>
>>> What's the state of dra7xx?  In my tree, it's still marked with
>>> CONFIG_BROKEN.  Last I heard there was a reset issue that needed to
>>> be worked out, but I don't know whether that's been done yet.
>>
>> I've posted pdata-quirks mechanism to do the reset (which will get PCIe
>> working). Tony had some comments and we are expecting feedback from Paul. I'll
>> ping him again in that thread.
> 
> Great, thanks, can you cc me as well?  I want to make sure we don't

you seem to be already copied in that thread. Check with $subject=[PATCH v3
3/3] pci: dra7xx: use pdata callbacks to perform reset.

Thanks
Kishon
> carry dra7xx around forever marked as broken.  I'd like to either
> make progress or remove it.
> 
> Bjorn
> 

  reply	other threads:[~2016-02-05 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 20:45 dra7xx driver status Bjorn Helgaas
2016-02-05  4:15 ` Kishon Vijay Abraham I
2016-02-05  4:15   ` Kishon Vijay Abraham I
2016-02-05 15:52   ` Bjorn Helgaas
2016-02-05 16:01     ` Kishon Vijay Abraham I [this message]
2016-02-05 16:01       ` Kishon Vijay Abraham I

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=56B4C74D.9010408@ti.com \
    --to=kishon@ti.com \
    --cc=helgaas@kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.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.