From: Florian Fainelli <f.fainelli@gmail.com>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] leds: bcm63x8: improve read and write functions
Date: Wed, 24 Feb 2021 09:43:08 -0800 [thread overview]
Message-ID: <f94b922f-b720-1ea1-e1d1-405e7bb475de@gmail.com> (raw)
In-Reply-To: <B9E7BB0F-00E7-40CC-9571-E17E574E1C3F@gmail.com>
On 2/24/2021 7:54 AM, Álvaro Fernández Rojas wrote:
> Hi Florian,
>
>> El 24 feb 2021, a las 16:45, Florian Fainelli <f.fainelli@gmail.com> escribió:
>>
>>
>>
>> On 2/24/2021 2:11 AM, Álvaro Fernández Rojas wrote:
>>> This code is proven to work in BMIPS BE/LE and ARM BE/LE.
>>> See bcm2835-rng and bcmgenet.c:
>>> https://github.com/torvalds/linux/blob/3b9cdafb5358eb9f3790de2f728f765fef100731/drivers/char/hw_random/bcm2835-rng.c#L42-L60
>>> https://github.com/torvalds/linux/blob/3b9cdafb5358eb9f3790de2f728f765fef100731/drivers/net/ethernet/broadcom/genet/bcmgenet.c#L71-L88
>>
>> What is the motivation for doing this? bcm2835-rng and bcmgenet are used
>> across MIPS and ARM platforms therefore they need to be compatible with
>> both, but these two LEDs drivers are super specialized, are you working
>> on porting the 6328 LED driver to the newer ARM-based DSL SoCs such as
>> 63138 and 63148?
>
> I just wanted to have all bmips drivers in line (at least regarding read/write).
> If I remember correctly someone told me that this controller was also present on some little endian SoCs, but you can confirm that :).
> Unfortunately I haven’t got any devices with ARM-based DSL SoCs, so the answer is no.
The 6328 LED controller could be utilized on the ARM-based DSL SoCs,
however 6358 will not, so changing the I/O accessors for that driver
sounds like just code churn to me.
--
Florian
prev parent reply other threads:[~2021-02-24 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 10:11 [PATCH v2 0/2] leds: bcm63x8: improve read and write functions Álvaro Fernández Rojas
2021-02-24 10:11 ` [PATCH v2 1/2] leds: bcm6328: improve write and read functions Álvaro Fernández Rojas
2021-02-24 15:43 ` Florian Fainelli
2021-02-24 10:11 ` [PATCH v2 2/2] leds: bcm6358: " Álvaro Fernández Rojas
2021-02-24 15:43 ` Florian Fainelli
2021-02-24 15:45 ` [PATCH v2 0/2] leds: bcm63x8: improve read and write functions Florian Fainelli
2021-02-24 15:54 ` Álvaro Fernández Rojas
2021-02-24 17:43 ` Florian Fainelli [this message]
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=f94b922f-b720-1ea1-e1d1-405e7bb475de@gmail.com \
--to=f.fainelli@gmail.com \
--cc=dmurphy@ti.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=pavel@ucw.cz \
/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