ARM: dts: cygnus: Add HWRNG node
Subsystems (2)
PATCH 1/1 ARM: dts: cygnus: Add HWRNG node
From: Cl?ment Peron <[email protected]>
There is a HWRNG in Broadcom Cygnus SoC, so enable it.
--- arch/arm/boot/dts/bcm-cygnus.dtsi | 5 +++++ 1 file changed, 5 insertions(+)
arch/arm/boot/dts/bcm-cygnus.dtsi +5 -0
@@ -452,6 +452,11 @@ status = "disabled"; }; + hwrng: hwrng at 18032000 { + compatible = "brcm,iproc-rng200"; + reg = <0x18032000 0x28>; + }; + sdhci0: sdhci at 18041000 { compatible = "brcm,sdhci-iproc-cygnus"; reg = <0x18041000 0x100>;
Signature · 1 line
2.17.1
Hi Clement,
Quoted 5 lines · Cl?ment P?ron
From: Cl?ment Peron <[email protected]>
There is a HWRNG in Broadcom Cygnus SoC, so enable it.
Signed-off-by Cl?ment Peron <[email protected]>
Thanks for upstreaming some missing Cygnus components.
But, the problem is the tarball release from Broadcom you are extracting these changes from does not contain git history; so, you are missing the original authors and signed-off's.
I checked our internal git repository and for this commit the author is:
Mohamed Ismail Abdul Packir Mohamed <[email protected]>
Please adjust author and signed-off appropriately.? If there are other changes you are extracting from the source tarballs you have please contact me so we can construct patch appropriately.
Regards,
Scott
Quoted 20 lines
--- arch/arm/boot/dts/bcm-cygnus.dtsi | 5 +++++ 1 file changed, 5 insertions(+)arch/arm/boot/dts/bcm-cygnus.dtsi +5
-0@@ -452,6 +452,11 @@ status = "disabled"; }; + hwrng: hwrng at 18032000 { + compatible = "brcm,iproc-rng200"; + reg = <0x18032000 0x28>; + }; + sdhci0: sdhci at 18041000 { compatible = "brcm,sdhci-iproc-cygnus"; reg = <0x18041000 0x100>;
Quoted 17 lines · Scott Branden
Hi Clement,
Quoted 5 lines · Cl?ment P?ron
From: Cl?ment Peron <[email protected]>
There is a HWRNG in Broadcom Cygnus SoC, so enable it.
Signed-off-by Cl?ment Peron <[email protected]>Thanks for upstreaming some missing Cygnus components.
But, the problem is the tarball release from Broadcom you are extracting these changes from does not contain git history; so, you are missing the original authors and signed-off's.
I checked our internal git repository and for this commit the author is:
Mohamed Ismail Abdul Packir Mohamed <[email protected]>
Quoted 3 lines
Please adjust author and signed-off appropriately.? If there are other changes you are extracting from the source tarballs you have please contact me so we can construct patch appropriately.
If you want the original author's Signed-off-by to be preserved, why don't you extract it from your internal git tree and submit the patch on Mohamed's behalf?
AFAICT what Clement is doing here is permissible given the Linux developer certificate of origin though I am not a lawyer of course.
Signature · 1 line
Florian
Hi Scott, Florian,
Quoted 23 lines · Florian Fainelli
Quoted 17 lines · Scott Branden
Hi Clement,
Quoted 5 lines · Cl?ment P?ron
From: Cl?ment Peron <[email protected]>
There is a HWRNG in Broadcom Cygnus SoC, so enable it.
Signed-off-by Cl?ment Peron <[email protected]>Thanks for upstreaming some missing Cygnus components.
But, the problem is the tarball release from Broadcom you are extracting these changes from does not contain git history; so, you are missing the original authors and signed-off's.
I checked our internal git repository and for this commit the author is:
Mohamed Ismail Abdul Packir Mohamed <[email protected]>Quoted 3 lines
Please adjust author and signed-off appropriately. If there are other changes you are extracting from the source tarballs you have please contact me so we can construct patch appropriately.
Quoted 8 lines
If you want the original author's Signed-off-by to be preserved, why don't you extract it from your internal git tree and submit the patch on Mohamed's behalf?
AFAICT what Clement is doing here is permissible given the Linux developer certificate of origin though I am not a lawyer of course. --
Florian
Totally not my goal to steal the author and agree to keep track of the original author
as soon as it's possible. I didn't though it was important for this patch as the same
code is available in the dt-bindings documentation.
Actually there are still some buggy components like DSA (Arun proposed a patch this morning)
the PWM (config and delay aren't correct) and I2C. These are mainlined but can't be used
and need a minimal effort to correctly work on Cygnus.
Also there are some important components like USB Phy or Mailbox that were proposed and
almost made it, but just need a small modification to be accepted.
My idea was just to submit small patches that are trivial to review. In order to avoid keeping
lots of patches in our kernel and also have something functional when building a mainline kernel.
Regards,
Clement
Quoted 38 lines · Cl?ment P?ron
Hi Scott, Florian,
Quoted 21 lines · Florian Fainelli
Quoted 17 lines · Scott Branden
Hi Clement,
Quoted 5 lines · Cl?ment P?ron
From: Cl?ment Peron <[email protected]>
There is a HWRNG in Broadcom Cygnus SoC, so enable it.
Signed-off-by Cl?ment Peron <[email protected]>Thanks for upstreaming some missing Cygnus components.
But, the problem is the tarball release from Broadcom you are extracting these changes from does not contain git history; so, you are missing the original authors and signed-off's.
I checked our internal git repository and for this commit the author is:
Mohamed Ismail Abdul Packir Mohamed <[email protected]>Quoted 3 lines
Please adjust author and signed-off appropriately. If there are other changes you are extracting from the source tarballs you have please contact me so we can construct patch appropriately.
Quoted 8 lines
If you want the original author's Signed-off-by to be preserved, why don't you extract it from your internal git tree and submit the patch on Mohamed's behalf?
AFAICT what Clement is doing here is permissible given the Linux developer certificate of origin though I am not a lawyer of course. --
FlorianTotally not my goal to steal the author and agree to keep track of the original author
as soon as it's possible. I didn't though it was important for this patch as the same
code is available in the dt-bindings documentation.
Quoted 5 lines
Actually there are still some buggy components like DSA (Arun proposed a patch this morning)
the PWM (config and delay aren't correct) and I2C. These are mainlined but can't be used
and need a minimal effort to correctly work on Cygnus.
We have internal versions of most everything.? It's a matter of getting people to push the appropriate patches out for upstream version to work. Please contact the bcm-kernel-feedback list with issues and we can work through common solution (or, likely already have a solution just not upstreamed).
Quoted 4 lines
Also there are some important components like USB Phy or Mailbox that were proposed and
almost made it, but just need a small modification to be accepted.
Again - we may have internal solution already.? Yes, mailbox was submitted upstream a long time ago and I think got stalled being accepted upstream.? We can work through upstream solution by starting with sending to bcm-kernel-feedback-list to discuss details.
Quoted 5 lines
My idea was just to submit small patches that are trivial to review. In order to avoid keeping
lots of patches in our kernel and also have something functional when building a mainline kernel.
I understand the difficulty you would have if you're trying to work with a different kernel version in our release.? If you send me a list directly of the drivers you use in Cygnus that will help me get those changes prioritized to be pushed upstream.? And/or we can work together on that.
Quoted 3 lines
Regards,
Clement
Thanks,
?Scott
Quoted 18 lines · Florian Fainelli
Quoted 17 lines · Scott Branden
Hi Clement,
Quoted 5 lines · Cl?ment P?ron
From: Cl?ment Peron <[email protected]>
There is a HWRNG in Broadcom Cygnus SoC, so enable it.
Signed-off-by Cl?ment Peron <[email protected]>Thanks for upstreaming some missing Cygnus components.
But, the problem is the tarball release from Broadcom you are extracting these changes from does not contain git history; so, you are missing the original authors and signed-off's.
I checked our internal git repository and for this commit the author is:
Mohamed Ismail Abdul Packir Mohamed <[email protected]>
Quoted 6 lines
Quoted 3 lines
Please adjust author and signed-off appropriately.? If there are other changes you are extracting from the source tarballs you have please contact me so we can construct patch appropriately.
If you want the original author's Signed-off-by to be preserved, why don't you extract it from your internal git tree and submit the patch on Mohamed's behalf?
Sure, I can submit the original patch to keep things simple and avoid finding a lawyer right now.
Quoted 3 lines
AFAICT what Clement is doing here is permissible given the Linux developer certificate of origin though I am not a lawyer of course.
But, It would be great to get some guidance and clarification on this for sure.
I'm reading:
https://www.kernel.org/doc/html/v4.16/process/submitting-patches.html
The change was created entirely by Broadcom, so seems difficult for somebody else to upstream change without appropriate authorship and signed off from copyright holder.? Point a) and b) are not met in Developer's Certificate of Origin while point c) is being attempted (without a or b being certified).
Quoted 32 lines · Scott Branden
Quoted 18 lines · Florian Fainelli
Quoted 17 lines · Scott Branden
Hi Clement,
Quoted 5 lines · Cl?ment P?ron
From: Cl?ment Peron <[email protected]>
There is a HWRNG in Broadcom Cygnus SoC, so enable it.
Signed-off-by Cl?ment Peron <[email protected]>Thanks for upstreaming some missing Cygnus components.
But, the problem is the tarball release from Broadcom you are extracting these changes from does not contain git history; so, you are missing the original authors and signed-off's.
I checked our internal git repository and for this commit the author is:
Mohamed Ismail Abdul Packir Mohamed <[email protected]>Quoted 6 lines
Quoted 3 lines
Please adjust author and signed-off appropriately.? If there are other changes you are extracting from the source tarballs you have please contact me so we can construct patch appropriately.
If you want the original author's Signed-off-by to be preserved, why don't you extract it from your internal git tree and submit the patch on Mohamed's behalf?
Sure, I can submit the original patch to keep things simple and avoid finding a lawyer right now.
Quoted 3 lines
AFAICT what Clement is doing here is permissible given the Linux developer certificate of origin though I am not a lawyer of course.
Quoted 8 lines
But, It would be great to get some guidance and clarification on this for sure.
I'm reading:
https://www.kernel.org/doc/html/v4.16/process/submitting-patches.htmlThe change was created entirely by Broadcom, so seems difficult for somebody else to upstream change without appropriate authorship and signed off from copyright holder.
Indeed, but it is effectively Broadcom's fault for not providing a git tree for the customer to pull from in order to preserve the original authorship, if what was distributed is a tarball of changes against a vanilla kernel (which is likely to be the case), then all author attributions are lost.
Not suggesting you change how you deliver code to customers, we have the same issue in the STB/CM group, except maybe customers care less about upstreaming so we can do it ourselves at our own pace and using our own attributions.
Quoted 3 lines
Point a) and b) are not met in
Developer's Certificate of Origin while point c) is being attempted (without a or b being certified).
I would think that point a) and b) are met by the very fact that the Cygnus kernel port is GPLv2 code, being a derivative work of the Linux kernel, and that should be enough.
This is kind of well established things, this has happened for many Broadcom product lines unfortunately because not everyone is active like you in getting things upstreamed. Those contributions were still entirely valid and acceptable for the kernel community.
Maybe we do need a lawyer, Saul Goodman, are you here?
Signature · 1 line
Florian