linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.coquelin@st.com (Maxime Coquelin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/8] phy: miphy28lp: Add PHY header file for DT x Driver defines
Date: Thu, 6 Nov 2014 17:17:25 +0100	[thread overview]
Message-ID: <545B9F15.5070404@st.com> (raw)
In-Reply-To: <20141106153659.GD26543@x1>


On 11/06/2014 04:36 PM, Lee Jones wrote:
> On Thu, 06 Nov 2014, Maxime Coquelin wrote:
>> On 11/06/2014 12:28 PM, Lee Jones wrote:
>>> On Thu, 06 Nov 2014, Maxime Coquelin wrote:
>>>
>>>> Hi Kishon,
>>>> On 11/06/2014 07:59 AM, Kishon Vijay Abraham I wrote:
>>>>> Hi,
>>>>>
>>>>> On Tuesday 04 November 2014 04:21 PM, Gabriel FERNANDEZ wrote:
>>>>>> This provides the shared header file which will be reference from both
>>>>>> PHY driver and its associated Device Tree node(s).
>>>>>>
>>>>>> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@linaro.org>
>>>>>> ---
>>>>>>   include/dt-bindings/phy/phy.h | 18 ++++++++++++++++++
>>>>> I don't see this being used in device tree file. Are you planning to add this
>>>>> after -rc1 is tagged. Or else I have to create a separate branch for this file
>>>>> which will be merged by both me and the dt maintainer. Let me know.
>>>> I think we don't need to create a branch we will merged by both of us.
>>>>
>>>> What we can do that both of us apply this patch in our trees.
>>>> It will avoid dependencies on each others.
>>>>
>>>> What do you think?
>>> This makes no sense to me.  Can you find another way to explain this
>>> please?
>> I apply the patch on my STi tree.
>> Kishon applies the patch on his phy tree.
>>
>> At the end, both STi and phy branches will be merged in Linus tree,
>> with no conflicts.
>>
>> This is what we are doing for the STiH407 reset DT bindings with Philipp Z.
> If you do that, you will almost certainly get conflicts.  The commits
> have to share the same SHA1 for Git to know for sure that they are the
> same patch.  One of you needs to create a branch and tag it.  The
> other can then merge the tag _then_ you won't get conflicts.

Just made the test on my side, and I don't get any conflict.
In my test, the two SHA-1 were different.

>>>>> Thanks
>>>>> Kishon
>>>>>>   1 file changed, 18 insertions(+)
>>>>>>   create mode 100644 include/dt-bindings/phy/phy.h
>>>>>>
>>>>>> diff --git a/include/dt-bindings/phy/phy.h b/include/dt-bindings/phy/phy.h
>>>>>> new file mode 100644
>>>>>> index 0000000..e8c6a3f
>>>>>> --- /dev/null
>>>>>> +++ b/include/dt-bindings/phy/phy.h
>>>>>> @@ -0,0 +1,18 @@
>>>>>> +/*
>>>>>> + *
>>>>>> + * This header provides constants for the phy framework
>>>>>> + *
>>>>>> + * Copyright (C) 2014 STMicroelectronics
>>>>>> + * Author: Gabriel Fernandez <gabriel.fernandez@st.com>
>>>>>> + * License terms:  GNU General Public License (GPL), version 2
>>>>>> + */
>>>>>> +
>>>>>> +#ifndef _DT_BINDINGS_PHY
>>>>>> +#define _DT_BINDINGS_PHY
>>>>>> +
>>>>>> +#define PHY_TYPE_SATA		1
>>>>>> +#define PHY_TYPE_PCIE		2
>>>>>> +#define PHY_TYPE_USB2		3
>>>>>> +#define PHY_TYPE_USB3		4
>>>>>> +
>>>>>> +#endif /* _DT_BINDINGS_PHY */
>>>>>>

  reply	other threads:[~2014-11-06 16:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 10:51 [PATCH v5 0/8] phy: miphy28lp: Introduce support for MiPHY28lp Gabriel FERNANDEZ
2014-11-04 10:51 ` [PATCH v5 1/8] phy: miphy28lp: Add Device Tree bindings for the MiPHY28lp Gabriel FERNANDEZ
2014-11-04 10:51 ` [PATCH v5 2/8] phy: miphy28lp: Add PHY header file for DT x Driver defines Gabriel FERNANDEZ
2014-11-06  6:59   ` Kishon Vijay Abraham I
2014-11-06  9:30     ` Maxime Coquelin
2014-11-06 11:28       ` Lee Jones
2014-11-06 11:53         ` Maxime Coquelin
2014-11-06 15:36           ` Lee Jones
2014-11-06 16:17             ` Maxime Coquelin [this message]
2014-11-07 13:05               ` Lee Jones
2014-11-10 10:39                 ` Maxime Coquelin
2014-11-11  5:20                   ` Kishon Vijay Abraham I
2014-11-11 10:46                   ` Kishon Vijay Abraham I
2014-11-04 10:51 ` [PATCH v5 3/8] phy: miphy28lp: Provide support for the MiPHY28lp Generic PHY Gabriel FERNANDEZ
2014-11-04 10:51 ` [PATCH v5 4/8] ARM: DT: STi: STiH407: Add DT node for MiPHY28lp Gabriel FERNANDEZ
2014-11-18 11:51   ` Maxime Coquelin
2014-11-04 10:51 ` [PATCH v5 5/8] phy: miphy28lp: Add SSC support for SATA Gabriel FERNANDEZ
2014-11-04 10:51 ` [PATCH v5 6/8] phy: miphy28lp: Add SSC support for PCIE Gabriel FERNANDEZ
2014-11-04 10:51 ` [PATCH v5 7/8] phy: miphy28lp: Tune tx impedance across Soc cuts Gabriel FERNANDEZ
2014-11-04 10:51 ` [PATCH v5 8/8] ARM: multi_v7_defconfig: Enable MiPHY28lp - ST's Generic (SATA, PCIe & USB3) PHY Gabriel FERNANDEZ

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=545B9F15.5070404@st.com \
    --to=maxime.coquelin@st.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).