public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Angus Ainslie <angus@akkea.ca>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: robh+dt@kernel.org, linux-usb@vger.kernel.org,
	devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org,
	nikolaus.voss@loewensteinmedical.de,
	andriy.shevchenko@linux.intel.com, garsilva@embeddedor.com,
	keescook@chromium.org, linux-usb-owner@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add TI tps6598x DT binding and probe
Date: Fri, 8 May 2020 15:47:48 +0100	[thread overview]
Message-ID: <f6bd2b0b-1eda-8ea4-abf2-e17131b944d4@linaro.org> (raw)
In-Reply-To: <e1f5fac00b4d574edf187f2ccd19ebe2@akkea.ca>

On 08/05/2020 15:22, Angus Ainslie wrote:
> Hi,
> 
> On 2020-05-08 07:01, Heikki Krogerus wrote:
>> Hi,
>>
>> On Thu, May 07, 2020 at 10:47:31PM +0100, Bryan O'Donoghue wrote:
>>> V2:
>>> - Put myself down as sole schema maintainer as suggested - Andy
>>> - Fixed whitespace typo - Andy
>>> - Removed ifdef and of_match_ptr() - Andy
>>>
>>> V1:
>>> This simple series adds DT binding yaml and a DT lookup table for the
>>> tps6598x.
>>>
>>> Its possible to use i2c id_table to match the 'compatible = 
>>> "ti,tps6598x"
>>> and probe that way, however I think it is worthwhile adding a 
>>> specific OF
>>> way of doing it and having an accompanying yaml as an example.
>>>
>>> Bryan O'Donoghue (2):
>>>   dt-bindings: usb: Add TI tps6598x device tree binding documentation
>>>   usb: typec: tps6598x: Add OF probe binding
>>>
>>>  .../devicetree/bindings/usb/ti,tps6598x.yaml  | 64 +++++++++++++++++++
>>>  drivers/usb/typec/tps6598x.c                  |  7 ++
>>>  2 files changed, 71 insertions(+)
>>>  create mode 100644 
>>> Documentation/devicetree/bindings/usb/ti,tps6598x.yaml
>>
>> There was already a series from Angus [1] for this. The bindings
>> looked a bit different, but I think we should use these, because in
>> the DT bindings from Angus there appeared to be definitions for OF
>> graph that was not used. Or maybe I got it wrong?
>>
> 
> I was trying to include optional components but was not sure of the 
> syntax so that might have been wrong.
> 
>> Angus, is it OK if we use these patches instead the ones from you?
>>
> 
> Yeah these ones will work great for what we need.
> 
> Sorry Bryan I didn't realize there was a patch already in progress.
> 
> @Bryan, I'm going to send up some extcon patches for the tps6598x soon 
> but maybe I should check and make sure you don't already have anything 
> planned there.
> 
> It still needs to be retested after cleaning up but it's the top 9 
> patches here:
> 
> https://source.puri.sm/angus.ainslie/linux-next/-/commits/next/extcon

Makes me glad I didn't try to touch the PDO stuff :)

That series looks fine to me.

The only other modification I have is here.

https://lore.kernel.org/linux-usb/20200507215938.1983363-2-bryan.odonoghue@linaro.org/T/#u

which is about data-role switching.

---
bod


  reply	other threads:[~2020-05-08 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 21:47 [PATCH v2 0/2] Add TI tps6598x DT binding and probe Bryan O'Donoghue
2020-05-07 21:47 ` [PATCH v2 1/2] dt-bindings: usb: Add TI tps6598x device tree binding documentation Bryan O'Donoghue
2020-05-15  3:09   ` Rob Herring
2020-05-07 21:47 ` [PATCH v2 2/2] usb: typec: tps6598x: Add OF probe binding Bryan O'Donoghue
2020-05-09  7:59   ` Martin Kepplinger
2020-05-11 10:29   ` Heikki Krogerus
2020-05-08 14:01 ` [PATCH v2 0/2] Add TI tps6598x DT binding and probe Heikki Krogerus
2020-05-08 14:22   ` Angus Ainslie
2020-05-08 14:47     ` Bryan O'Donoghue [this message]
2020-05-08 16:21       ` Angus Ainslie

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=f6bd2b0b-1eda-8ea4-abf2-e17131b944d4@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=angus@akkea.ca \
    --cc=devicetree@vger.kernel.org \
    --cc=garsilva@embeddedor.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-owner@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nikolaus.voss@loewensteinmedical.de \
    --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