From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manikandan.M@microchip.com
Cc: Hari.PrasathGE@microchip.com, andrzej.hajda@intel.com,
neil.armstrong@linaro.org, rfoss@kernel.org,
Laurent.pinchart@ideasonboard.com, jonas@kwiboo.se,
jernej.skrabec@gmail.com, airlied@gmail.com, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux@armlinux.org.uk,
Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
claudiu.beznea@tuxon.dev, arnd@arndb.de, Jason@zx2c4.com,
palmer@rivosinc.com, mpe@ellerman.id.au, rdunlap@infradead.org,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] drm/bridge: add Microchip DSI controller support for sam9x7 SoC series
Date: Thu, 11 Jul 2024 11:05:37 +0200 [thread overview]
Message-ID: <4c1b7af7-e53c-492a-9c41-40cad78f7666@kernel.org> (raw)
In-Reply-To: <aeaeb5d4-5e55-4a7a-bce7-fa207ebf0616@microchip.com>
On 11/07/2024 10:30, Manikandan.M@microchip.com wrote:
> Hi Krzysztof,
>
> On 04/07/24 4:27 pm, Krzysztof Kozlowski wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> On 04/07/2024 10:48, Manikandan Muralidharan wrote:
>>> Add the Microchip's DSI controller wrapper driver that uses
>>> the Synopsys DesignWare MIPI DSI host controller bridge.
>>>
>>> Signed-off-by: Manikandan Muralidharan <manikandan.m@microchip.com>
>>> ---
>>
>>
>> ...
>>
>>> +
>>> +#define HSTT(_maxfreq, _c_lp2hs, _c_hs2lp, _d_lp2hs, _d_hs2lp) \
>>> +{ \
>>> + .maxfreq = _maxfreq, \
>>> + .timing = { \
>>> + .clk_lp2hs = _c_lp2hs, \
>>> + .clk_hs2lp = _c_hs2lp, \
>>> + .data_lp2hs = _d_lp2hs, \
>>> + .data_hs2lp = _d_hs2lp, \
>>> + } \
>>> +}
>>> +
>>> +struct hstt hstt_table[] = {
>>
>> So more globals? No.
>
> In the sam9x7 datasheet, the high speed transition time for data and
> clock lane at different freq for the DSI controller ranges are tabulated
> with constant values.
> I referred other similar platforms for the functionality and found
> similar way of implementation, only a few had equations to derive the
> low power and high speed timings.I am not able to come up with a more
> efficient method. If there is something I am missing, please suggest.
> TIA
Yeah, this should not be a global. Nothing above suggests it.
BTW, no W=1 clang warnings? Are you sure?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-11 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 8:48 [PATCH 0/4] MIPI DSI Controller support for SAM9X75 series Manikandan Muralidharan
2024-07-04 8:48 ` [PATCH 1/4] dt-bindings: display: bridge: add sam9x75-mipi-dsi binding Manikandan Muralidharan
2024-07-04 10:53 ` Krzysztof Kozlowski
2024-07-04 8:48 ` [PATCH 2/4] drm/bridge: add Microchip DSI controller support for sam9x7 SoC series Manikandan Muralidharan
2024-07-04 10:57 ` Krzysztof Kozlowski
2024-07-11 8:30 ` Manikandan.M
2024-07-11 9:05 ` Krzysztof Kozlowski [this message]
2024-07-11 9:58 ` Conor Dooley
2024-07-11 10:08 ` Manikandan.M
2024-07-14 14:15 ` claudiu beznea
2024-07-04 8:48 ` [PATCH 3/4] MAINTAINERS: add SAM9X7 SoC's Microchip's MIPI DSI host wrapper driver Manikandan Muralidharan
2024-07-04 10:48 ` Krzysztof Kozlowski
2024-07-04 8:48 ` [PATCH 4/4] ARM: configs: at91: Enable Microchip's MIPI DSI Host Controller support Manikandan Muralidharan
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=4c1b7af7-e53c-492a-9c41-40cad78f7666@kernel.org \
--to=krzk@kernel.org \
--cc=Hari.PrasathGE@microchip.com \
--cc=Jason@zx2c4.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Manikandan.M@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=airlied@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrzej.hajda@intel.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mpe@ellerman.id.au \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=palmer@rivosinc.com \
--cc=rdunlap@infradead.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®