On 2018년 03월 07일 11:12, Chanwoo Choi wrote:
> Hi Rob and Andrzej,
> On 2018년 03월 06일 21:53, Andrzej Hajda wrote:
>> Hi Rob, Chanwoo, Krzysztof,
>> On 27.02.2018 08:11, Andrzej Hajda wrote:
>>> Thanks for reviews of previous iterations.
>>> This patchset introduces USB physical connector bindings, together with
>>> working example.
>>> I have removed RFC prefix - the patchset seems to be heading
>>> to a happy end :)
>>> v5: fixed extra parenthesis in dts, renamed extcon function.
>>> v4: improved binding descriptions, added missing reg in dts.
>>> v3: Separate binding for Samsung 11-pin connector, added full-blown USB-C
>>> v2: I have addressed comments by Rob and Laurent, thanks
>>> Changes in datail are described in the patches.
>>> Andrzej Hajda (5):
>>> dt-bindings: add bindings for USB physical connector
>>> dt-bindings: add bindings for Samsung micro-USB 11-pin connector
>>> arm64: dts: exynos: add micro-USB connector node to TM2 platforms
>>> arm64: dts: exynos: add OF graph between MHL and USB connector
>>> extcon: add possibility to get extcon device by OF node
>>> Maciej Purski (1):
>>> drm/bridge/sii8620: use micro-USB cable detection logic to detect MHL
>> It looks like all patches received R-B or acks (I forgot add Krzysztof's
>> acks for dts part).
>> Now I have a question how to merge them.
>> The only functional dependency is between bridge and extcon, and from
>> the formal PoV bindings should be merged 1st.
>> I can merge it:
>> 1. All patches via drm-misc tree.
>> 2. All patches except dts via drm-misc, and Krzysztof will merge dts via
>> samsung-soc tree.
>> Is it OK, for all? Better ideas?
> Krzysztof picked the dts patches. I'll make the immutable branch based on
> and apply them except for dts patchs. And I'll send the immutable branch to
> Rob and Andrzej.
I made the immutable branch as following: If you agree, I'll send pull
Or you can make the immutable branch and send pull request to Rob and me.
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html