From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Chandrabhanu Mahapatra <cmahapatra@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 2/7] OMAPDSS: DISPC: Move DISPC specific dss_reg_fields to dispc_features
Date: Fri, 30 Nov 2012 10:25:35 +0000 [thread overview]
Message-ID: <50B8899F.3080904@ti.com> (raw)
In-Reply-To: <50B8844E.2010903@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
On 2012-11-30 12:02, Chandrabhanu Mahapatra wrote:
> On Thursday 29 November 2012 05:35 PM, Tomi Valkeinen wrote:
>>> diff --git a/drivers/video/omap2/dss/dss.h b/drivers/video/omap2/dss/dss.h
>>> index 84a7f6a..aa273d8 100644
>>> --- a/drivers/video/omap2/dss/dss.h
>>> +++ b/drivers/video/omap2/dss/dss.h
>>> @@ -143,6 +143,10 @@ struct reg_field {
>>> u8 low;
>>> };
>>>
>>> +struct register_field {
>>> + u8 start, end;
>>> +};
>>> +
>>
>> We already have the dss_reg_field struct. I think it's better to move
>> that to dss.h, and use it, instead of creating an exact duplicate.
>>
>> Tomi
>>
>>
>
> register_field appears to be a more generic a name rather than
> dss_reg_field. Also I was thinking to initialise
Yes, register_field is a more generic name, and that's one reason I
don't suggest using it. There's a possibility of name clash if some
common linux framework would use a similar name. So dss_reg_field refers
to a register field, used by (omap)dss.
It could also be renamed to omapdss_reg_field, but that's a bit longer.
But perhaps naming it omapdss_reg_field would separate it better from
dss_reg_fields.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Chandrabhanu Mahapatra <cmahapatra@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 2/7] OMAPDSS: DISPC: Move DISPC specific dss_reg_fields to dispc_features
Date: Fri, 30 Nov 2012 12:25:35 +0200 [thread overview]
Message-ID: <50B8899F.3080904@ti.com> (raw)
In-Reply-To: <50B8844E.2010903@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
On 2012-11-30 12:02, Chandrabhanu Mahapatra wrote:
> On Thursday 29 November 2012 05:35 PM, Tomi Valkeinen wrote:
>>> diff --git a/drivers/video/omap2/dss/dss.h b/drivers/video/omap2/dss/dss.h
>>> index 84a7f6a..aa273d8 100644
>>> --- a/drivers/video/omap2/dss/dss.h
>>> +++ b/drivers/video/omap2/dss/dss.h
>>> @@ -143,6 +143,10 @@ struct reg_field {
>>> u8 low;
>>> };
>>>
>>> +struct register_field {
>>> + u8 start, end;
>>> +};
>>> +
>>
>> We already have the dss_reg_field struct. I think it's better to move
>> that to dss.h, and use it, instead of creating an exact duplicate.
>>
>> Tomi
>>
>>
>
> register_field appears to be a more generic a name rather than
> dss_reg_field. Also I was thinking to initialise
Yes, register_field is a more generic name, and that's one reason I
don't suggest using it. There's a possibility of name clash if some
common linux framework would use a similar name. So dss_reg_field refers
to a register field, used by (omap)dss.
It could also be renamed to omapdss_reg_field, but that's a bit longer.
But perhaps naming it omapdss_reg_field would separate it better from
dss_reg_fields.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2012-11-30 10:25 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 10:41 [PATCH 0/7] OMAPDSS: Cleanup omap_dss_features Chandrabhanu Mahapatra
2012-11-28 10:53 ` Chandrabhanu Mahapatra
2012-11-28 10:41 ` [PATCH 1/7] OMAPDSS: DISPC: Move burst_size and buffer_size to dispc_features Chandrabhanu Mahapatra
2012-11-28 10:53 ` Chandrabhanu Mahapatra
2012-11-29 12:01 ` Tomi Valkeinen
2012-11-29 12:01 ` Tomi Valkeinen
2012-11-28 10:41 ` [PATCH 2/7] OMAPDSS: DISPC: Move DISPC specific dss_reg_fields " Chandrabhanu Mahapatra
2012-11-28 10:53 ` Chandrabhanu Mahapatra
2012-11-29 12:05 ` Tomi Valkeinen
2012-11-29 12:05 ` Tomi Valkeinen
2012-11-30 10:02 ` Chandrabhanu Mahapatra
2012-11-30 10:14 ` Chandrabhanu Mahapatra
2012-11-30 10:25 ` Tomi Valkeinen [this message]
2012-11-30 10:25 ` Tomi Valkeinen
2012-11-29 12:18 ` Tomi Valkeinen
2012-11-29 12:18 ` Tomi Valkeinen
2012-12-03 6:29 ` Chandrabhanu Mahapatra
2012-12-03 6:41 ` Chandrabhanu Mahapatra
2012-12-04 8:16 ` Tomi Valkeinen
2012-12-04 8:16 ` Tomi Valkeinen
2012-11-28 10:41 ` [PATCH 3/7] OMAPDSS: DISPC: Move DISPC specific dss_params " Chandrabhanu Mahapatra
2012-11-28 10:53 ` Chandrabhanu Mahapatra
2012-11-29 12:08 ` Tomi Valkeinen
2012-11-29 12:08 ` Tomi Valkeinen
2012-11-28 10:41 ` [PATCH 4/7] OMAPDSS: DSI: Move DSI specific reg_fields to dsi_feats Chandrabhanu Mahapatra
2012-11-28 10:53 ` Chandrabhanu Mahapatra
2012-11-28 10:41 ` [PATCH 5/7] OMAPDSS: DSI: Move DSI specific dss_params " Chandrabhanu Mahapatra
2012-11-28 10:53 ` Chandrabhanu Mahapatra
2012-11-28 10:41 ` [PATCH 6/7] OMAPDSS: DSS: Add members fld_dispc_clk_switch and dss_fck_max Chandrabhanu Mahapatra
2012-11-28 10:53 ` Chandrabhanu Mahapatra
2012-11-28 10:41 ` [PATCH 7/7] OMAPDSS: DSI: Add FEAT_PARAM_DSS_FCK Chandrabhanu Mahapatra
2012-11-28 10:53 ` Chandrabhanu Mahapatra
2012-12-05 10:16 ` [PATCH V2 0/6] OMAPDSS: Cleanup omap_dss_features Chandrabhanu Mahapatra
2012-12-05 10:28 ` Chandrabhanu Mahapatra
2012-12-05 10:16 ` [PATCH V2 1/6] OMAPDSS: DISPC: Move burst_size and buffer_size to dispc_features Chandrabhanu Mahapatra
2012-12-05 10:28 ` Chandrabhanu Mahapatra
2012-12-05 10:16 ` [PATCH V2 2/6] OMAPDSS: DISPC: Move DISPC specific dss_reg_fields " Chandrabhanu Mahapatra
2012-12-05 10:28 ` Chandrabhanu Mahapatra
2012-12-17 12:37 ` Tomi Valkeinen
2012-12-17 12:37 ` Tomi Valkeinen
2012-12-19 9:27 ` Chandrabhanu Mahapatra
2012-12-19 9:39 ` Chandrabhanu Mahapatra
2012-12-05 10:16 ` [PATCH V2 3/6] OMAPDSS: DISPC: Move DISPC specific dss_params " Chandrabhanu Mahapatra
2012-12-05 10:28 ` Chandrabhanu Mahapatra
2012-12-05 10:16 ` [PATCH V2 4/6] OMAPDSS: DSI: Move DSI specific reg_fields to dsi_feats Chandrabhanu Mahapatra
2012-12-05 10:28 ` Chandrabhanu Mahapatra
2012-12-17 12:23 ` Tomi Valkeinen
2012-12-17 12:23 ` Tomi Valkeinen
2012-12-19 8:58 ` Chandrabhanu Mahapatra
2012-12-19 9:10 ` Chandrabhanu Mahapatra
2012-12-05 10:16 ` [PATCH V2 5/6] OMAPDSS: DSI: Move DSI specific dss_params " Chandrabhanu Mahapatra
2012-12-05 10:28 ` Chandrabhanu Mahapatra
2012-12-05 10:16 ` [PATCH V2 6/6] OMAPDSS: DSS: Add members fld_dispc_clk_switch and dss_fck_max Chandrabhanu Mahapatra
2012-12-05 10:28 ` Chandrabhanu Mahapatra
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=50B8899F.3080904@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=cmahapatra@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.